Rate Limits
Rate limits are policies that restrict how much a user can access the API within a given period of time. They help prevent misuse and abuse of the API and ensure fair access to the service for all users.
If you exceed your rate limit, the API will return a 429(Too Many Requests) error. You can check your remaining usage through Rate limit Headers included in each response.
Rate Limit Headers
Rate limit information is available in the HTTP headers of each API response as described below.
| Rate limit HTTP Headers | Description |
|---|---|
| x-{window}-rate-limit | The maximum number of requests allowed per {window}
{window} is one of second, minute, or day. |
| x-{window}-rate-limit-remaining | The number of requests remaining in the current {window}
{window} is one of second, minute, or day. |
| retry-after | The number of seconds to wait before retrying the request |
| retry-after-ms | The number of milliseconds to wait before retrying the request |
※ The retry-after and retry-after-ms headers may not be included in every response.
Examples
HTTP/1.1 429 Too Many Requests
...
retry-after: 1
retry-after-ms: 630
x-request-id: 01a1b489-0e13-76bd-85e1-f571524de67c
x-second-rate-limit: 1
x-second-rate-limit-remaining: 0
x-minute-rate-limit: 60
x-minute-rate-limit-remaining: 59
x-day-rate-limit: 86400
x-day-rate-limit-remaining: 86300The x-request-id is a unique identifier assigned to each request. It is automatically generated by the API service.