Rate limits

How many requests your keys may make, how you see it, and what to do when you reach it.

Each API app has a request budget per minute, and heavy requests (exports, large lists) cost more than light reads. Every answer carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset (seconds until the budget refills). Too many requests at once answer 429 RATE_LIMITED with Retry-After.

The SDKs wait for Retry-After and try again (twice by default); a write is retried with the same Idempotency-Key, so it is never applied twice. Spread bulk work out, page with limit rather than many small requests, and use webhooks instead of polling. Ask support if your integration needs a higher budget.

curl -i https://api.watenga.africa/v1/transactions?limit=1 -H "Authorization: Bearer $WATENGA_SECRET_KEY"
# RateLimit-Limit: …
# RateLimit-Remaining: …
# RateLimit-Reset: …

Related: Errors · Idempotency