Skip to content

/problems/too-many-requests⚓︎

Problem

This is a description of a specific error response that you can receive when using the INVERS OneAPI via REST.1

Check out our API Basics to learn more about the basic structure of all error responses and to find out how you should handle them.

{
    "type": "/problems/too-many-requests",
    "type_documentation": "https://developers.invers.com/problems/too-many-requests",
    "title": "Too many requests.",
    "status": 429,
    "detail": "…",
    "flow_id": "84ec18c6-2c31-4d4d-96bf-7bd5c0d8bee4"
}

Meaning⚓︎

This problem type occurs when requests are sent at too high a rate.

Details⚓︎

  • Use the error response’s type property to handle specific errors and exception handling within your application. It’s comparable to an error code.
  • The detail property contains additional, more human-readable information about the problem or error. This is explanatory text and you should not have any exception handling and error handling code depend on it, as it may change.

Detail examples⚓︎

The following examples are typical texts which you might receive in the error response’s detail property. Note that it is not a complete list of all possible cases. Therefore expect to receive error responses with a detail property value not listed below.

Example problem details⚓︎

This client has sent too many requests and is temporarily blocked. See ‘X-Rate-Limit’ headers for details.

You have sent too many requests within a certain time frame.

Possible solutions:

- Inspect the `X-Rate-Limit-Limit`, `X-Rate-Limit-Remaining` and `X-Rate-Limit-Reset` response headers
- Wait for the time specified in `X-Rate-Limit-Reset` in UTC epoch seconds and attempt the request again
- To prevent further errors, make sure you make requests only so often that `X-Rate-Limit-Remaining` never drops to zero
This client has sent too many requests and is temporarily blocked. See ‘Retry-After’ header for details.

You have sent too many requests within a certain time frame.

Possible solutions:

- Inspect the 'Retry-After' response header
- If the value consists of a single integer, wait for that many seconds and attempt the request again
- If the value consists of an HTML date, wait until then and attempt the request again

  1. The flow_id is specific to each API call, so it will be different in your case. However, type, title and status will match your actual error response if you receive the error described on this page. ↩