> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dojah.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get help with Dojah

> Four ways to reach Dojah — Help Centre, Slack community, technical support, and dashboard live chat — plus what to include so an integration issue can be traced quickly.

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.

<Columns cols={2}>
  <Card title="Help Centre" icon={<span className="dj-card-emoji">📚</span>} href="https://support.dojah.io">
    Self-serve answers on pricing, onboarding, accounts and billing.
  </Card>

  <Card title="Slack community" icon={<span className="dj-card-emoji">💬</span>} href="https://join.slack.com/t/dojahinc/shared_invite/zt-ng9ch04k-bT5sVBnTY6Fa1ffQ0SAxpQ">
    Quick questions and integration advice from the community.
  </Card>

  <Card title="Technical support" icon={<span className="dj-card-emoji">🛠️</span>} href="mailto:support@dojah.io">
    Failing calls, unexpected responses and production incidents.
  </Card>

  <Card title="Dashboard live chat" icon={<span className="dj-card-emoji">⚡</span>} href="/dashboard-guide/account/support">
    A live thread with the team, inside your dashboard.
  </Card>
</Columns>

## Which channel do I need?

| If you…                                                        | Use                                                                                                   |
| -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Have a pricing, billing or account question                    | [Help Centre](https://support.dojah.io)                                                               |
| Are evaluating Dojah and want to discuss volumes or a contract | [Help Centre](https://support.dojah.io)                                                               |
| Want to know which endpoint fits your use case                 | [Slack community](https://join.slack.com/t/dojahinc/shared_invite/zt-ng9ch04k-bT5sVBnTY6Fa1ffQ0SAxpQ) |
| Are getting an error you cannot explain from the reference     | [Technical support](mailto:support@dojah.io)                                                          |
| Have calls failing in production                               | [Technical support](mailto:support@dojah.io)                                                          |
| Need a webhook redelivered or a verification re-run            | [Technical support](mailto:support@dojah.io)                                                          |
| Want to talk to an agent now, from inside the dashboard        | [Dashboard live chat](/dashboard-guide/account/support)                                               |
| Need your wallet funded or a payment reconciled                | [Dashboard live chat](/dashboard-guide/account/support)                                               |

## 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:

| Detail                        | Why it helps                                                                   |
| ----------------------------- | ------------------------------------------------------------------------------ |
| The endpoint and method       | `GET /api/v1/kyc/bvn/full` narrows it immediately.                             |
| Environment                   | Whether you called `api.dojah.io` or `sandbox.dojah.io`.                       |
| Your `AppId`                  | Identifies the app whose logs to search.                                       |
| Timestamp, with the time zone | Lets the team find the request in the logs.                                    |
| The full response body        | Including any reference or request id Dojah returned.                          |
| The HTTP status code          | Tells the team whether it is your request, your wallet, or an upstream source. |
| What you expected instead     | Separates a bug from an endpoint doing what it is documented to do.            |

<Warning>
  **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.
</Warning>

<Tip>
  **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.
</Tip>

## Check these first

A large share of the issues that reach support are answered by four pages:

* [Errors & status codes](/api-reference/core-concepts/errors-status-codes) — what each code means, which are worth retrying, and the failures that come up most.
* [Authentication](/api-reference/get-started/authentication) — the cause of nearly every `401`, usually a `Bearer` prefix that should not be there.
* [Environments](/api-reference/get-started/environments) — why a call that works in sandbox can fail in production.
* [Wallet & billing](/api-reference/core-concepts/wallet-billing) — the `402` that stops production calls until the wallet is funded.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="What is the fastest way to reach a human?">
    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](/dashboard-guide/account/support).
  </Accordion>

  <Accordion title="Should I use Slack or technical support?">
    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.
  </Accordion>

  <Accordion title="Can I share a failing request in Slack?">
    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.
  </Accordion>

  <Accordion title="How do I report a suspected outage?">
    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](/api-reference/core-concepts/errors-status-codes).
  </Accordion>
</AccordionGroup>