Support
People who know the APIs, in English. What to send so we can help in one go.
Ask us
Email hello@nways.ng, in English. A person who knows the APIs answers, not a bot. To get an answer in one go, include:
- your project’s name and the first 8 characters of the key (never the whole key);
- the request: method, address and body, with the key removed;
- the answer: HTTP status, the
reasonin the error, and theX-Request-Idheader if there is one; - when it happened (with the time zone) and how often.
Never send a whole API key by email or chat. If a key has been shared or published, ask us to regenerate it: the old one stops working at once, or after a grace period you choose. API keys
How fast we answer
| Plan | Critical (the API is down for you) | Everything else |
|---|---|---|
| Starter | Best effort | Best effort |
| Growth | Next working day | Next working day |
| Business | 4 hours, every day | Next working day |
| Enterprise | 1 hour, every day | 4 working hours |
The times come with each plan. Working days are Monday to Friday in Lagos (West Africa Time, UTC+1), except public holidays.
Before you write
- A 401, 403 or 429? The
reasonsays what’s wrong and the Errors page says what to do. - Is it us? Check the service status.
- A wrong address, road or place? That’s map data: tell us the place and what’s wrong, or correct it in the N-Ways app, where drivers confirm fixes within days.
- Something changed? The changelog lists every change and deprecation.
Design partners
Partners can have a shared channel with the team that builds the platform, for questions, problems and the APIs you need next. Ask for it when you start.
Security issues
Found a way to misuse a key, see another partner’s data or get around a limit? Email hello@nways.ng with “Security” in the subject, and give us time to fix it before telling anyone else. We answer within one working day.