Rate Limits

The Revnator API applies limits to keep the service fast and fair for everyone. This page explains the limits that exist and how to handle them.

AI endpoint limits

AI endpoints are the most tightly limited because each call is a paid model round-trip. POST /api/v1/ai/trigger is capped at 10 requests per minute per API key. Exceeding it returns HTTP 429 with the error "Too many requests. Try again in a minute."

Pagination limits

List endpoints never return more than 50 records in one response. Use the limit and offset query parameters to page through larger result sets — limit defaults to 20 and is capped at 50.

1curl "https://app.revnator.com/api/v1/contacts?limit=50&offset=100" \
2  -H "X-Revnator-API-Key: rvn_live_your_key_here"
Copy

Handling 429 responses

When you receive a 429, pause and retry after a short delay. For AI endpoints, wait at least a minute. Build exponential backoff into any client that calls the API in a loop.

Fair use

Endpoints that are not explicitly rate-limited are still expected to be used reasonably. Page through data rather than polling tight loops, request only the records you need, and cache responses where you can. Sustained abusive traffic may have a key throttled or revoked.