Skip to main content
Four ways to reach us, depending on what you need. Start with the Help Centre for account and product questions — come to technical support when an endpoint is not behaving the way the reference says it should.

Help Centre

Self-serve answers on pricing, onboarding, accounts and billing.

Slack community

Quick questions and integration advice from the community.

Technical support

Failing calls, unexpected responses and production incidents.

Dashboard live chat

A live thread with the team, inside your dashboard.

​
Which channel do I need?

​
Before you report a technical issue

The team can resolve an integration issue far faster with the details that identify the exact call. Include as much of this as you have:
Never share your secret key. Not in Slack, not in an email, not in a screenshot. Dojah will never ask for it. Send your AppId instead — it identifies your app without granting access to it. If a secret key has been exposed, rotate it from the dashboard straight away.
Redact customer data. BVNs, NINs, phone numbers and document images belong in the dashboard chat or an email to technical support — never in the public Slack community.

​
Check these first

A large share of the issues that reach support are answered by four pages:
  • Errors & status codes — what each code means, which are worth retrying, and the failures that come up most.
  • Authentication — the cause of nearly every 401, usually a Bearer prefix that should not be there.
  • Environments — why a call that works in sandbox can fail in production.
  • Wallet & billing — the 402 that stops production calls until the wallet is funded.

​
Frequently asked questions

The live chat on the Support page of your dashboard — it opens a thread with the Dojah team, with no ticket number to track. See Support in the dashboard.
Use Slack for questions about how Dojah works — which endpoint to call, how a flow is meant to behave. Use technical support when a specific call is failing, because the team needs your AppId and timestamps to trace it, and those do not belong in a public channel.
Share the endpoint, the status code and the shape of the error. Do not share secret keys, AppId values, or customer identifiers such as BVNs and NINs — the community channel is public. Send those to technical support instead.
Contact technical support with the endpoint, the time the failures started, and the status codes you are seeing. A run of 424 responses usually means an upstream identity source is unavailable rather than a fault in your integration — see Errors & status codes.