Rate Limit Exceeded (Too Many Requests)
This error occurs when the API client exceeds the configured rate limits (number of requests permitted per minute or hour).
Error Response Example (RFC 9457)
Section titled “Error Response Example (RFC 9457)”{ "type": "https://docs.apinow.app/errors/too-many-requests", "title": "Rate Limit Exceeded", "status": 429, "code": "RATE_LIMIT_EXCEEDED", "detail": "Too many requests. Please try again in 45 seconds.", "instance": "/api/v1/posts"}Troubleshooting Guide
Section titled “Troubleshooting Guide”For API Consumers (What it means & how to fix)
Section titled “For API Consumers (What it means & how to fix)”- Rate Limiting: Back off and wait before making more requests. Check if your client is executing requests in an infinite loop or firing too many parallel requests.
- Implement Backoff: Use an exponential backoff retry strategy in your client application.
For API Authors (Domain & API Modeler notes)
Section titled “For API Authors (Domain & API Modeler notes)”- Rate Limit Policies: Rate limits are configured per API within the API Modeler. They can be applied granularly at three different levels:
- API Level: Applies a global default rate limit across all endpoints in the API.
- Exposed Entity Level: Overrides the global default for a specific entity’s collections (e.g., setting tighter limits on
/invoicesthan/posts). - Action Level: Overrides at the specific CRUD operation level (e.g., allowing high rates of
Readoperations, but strictly limitingCreateorDeleteactions to prevent abuse).
- If your users are hitting this limit unexpectedly, review the rate limits configured on the target action, exposed entity, or parent API model.