> For the complete documentation index, see [llms.txt](https://docs.sarafa.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sarafa.live/api-reference/api-and-transaction-limits.md).

# API and Transaction Limits

To ensure fair usage and maintain the stability of the Sarafa API, we implement rate limiting on the number of requests you can make within a specific time window. 

Currently, the API is limited to **2500 query requests every 10 minutes** per API key.If you exceed this limit, the API will return a **429 Too Many Requests** error response.

**Example JSON Response (Too Many Requests - HTTP 429):**

```json
{
  "status": "error",
  "message": "Too many requests. Please wait and try again later."
}
```

When you receive a 429 error, your application should implement a retry mechanism with an appropriate backoff strategy (e.g., waiting for a few seconds before attempting the request again). Avoid aggressive retries to prevent further overloading the API. You can monitor your API usage to stay within the defined limits.

### [​](https://readme.sarafa.ss/api-reference/limits#transactions-limits)Transactions Limits <a href="#transactions-limits" id="transactions-limits"></a>

The following table outlines the default transaction limits for SSP, UGX, and KES stablecoin backed wallets within the Sarafa platform. Please note that these limits may vary based on your business’s KYC/KYB verification level. You can view your specific limits within your account dashboard.

| Currency | Charge          | Transfers       |
| -------- | --------------- | --------------- |
| SSP      | 100-2,000,000   | 100-2,000,000   |
| UGX      | 5,000-3,950,000 | 5,000-3,950,000 |
| KES      | 100-150,000     | 100-150,000     |
| USD      | 1 - 10,000      | 1 - 10,000      |

### [​](https://readme.sarafa.ss/api-reference/limits#important-notes:)Important Notes: <a href="#important-notes" id="important-notes"></a>

These limits are per transaction are as per our integration partners and cannot be increased, changed or modified