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

# Errors & Status

> How the API reports success and failure.

Every response includes a **`status`** field and a human-readable **`message`**. Always branch on `status` rather than HTTP code alone.

## Status values

| `status` | Meaning |
| - | - |
| `success` | The service was delivered and your wallet was debited. |
| `fail` | The transaction did not go through. Read `message` for the reason. No charge, or an automatic refund, applies. |
| `pending` | The transaction is being processed. The final outcome is delivered via [webhook](https://docs.bilalsadasub.com/guides/webhooks.md). |

## Example failure

```json theme={null}
{
  "status": "fail",
  "message": "Insufficient wallet balance.",
  "request-id": "Data_12345678900"
}
```

## Common errors

> [accordion] 401 Unauthorized
>
> Missing or invalid token. Send `Authorization: Token <your_api_key>` — see [Authentication](https://docs.bilalsadasub.com/authentication.md).

> [accordion] Insufficient wallet balance
>
> Top up your wallet from the [dashboard](https://app.bilalsadasub.com) before retrying.

> [accordion] Duplicate request-id
>
> A transaction with that `request-id` already exists — the original result is returned instead of charging again. Use a fresh `request-id` for a new purchase.

> [accordion] Invalid plan or network
>
> Check the plan ID / network ID against your dashboard's Pricing & Plan IDs page.

> [!TIP]
>
> For `pending` transactions, never re-send the purchase — wait for the webhook, or re-query using the same `request-id`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.