Rate Limits
Limits are applied on an endpoint basis. When a rate limit is exceeded, an HTTP 429 error will be triggered with a message similar to 'API calls quota exceeded! maximum admitted 5 per 1 second'.
| Area | Endpoints | Limit | Concurrency |
|---|---|---|---|
| Authentication | /api/rest/v1/oauth/token | 300 per minute | |
| User Management | /api/rest/v1/management | 5 per second | |
| Data | /api/rest/v4/data | 5 per second | |
| Schema | /api/rest/v4/schema | 5 per second | |
| RelIntel | /api/rest/v4/ri/import | 5 per second | |
| Publications | /api/v1/rest/publication | 1000 per second | Single |
| eMarketing | /api/v1/eMarketing | 1000 per second |
Rate Limit Response Headers
In the response of API calls, 3 individual headers will be set with details to the current rate limit, the time of expiry and how many calls remain in the period. These are prefixed with 'X-Rate-Limit'.
If the information table above is incorrect, the header from the actual response is the authoritative answer.
X-Rate-Limit
The X-Rate-Limit response header describes the time period for the rate limit.
X-Rate-Limit-Remaining
The X-Rate-Limit-Remaining response header indicates the number of remaining API calls allowed during the current time period.
X-Rate-Limit-Reset
The X-Rate-Limit-Reset response header specifies the exact time when the current limit will be reset, and a new limit period will begin.
Example Header Responses
X-Rate-Limit-Limit: 1s
X-Rate-Limit-Remaining: 4
X-Rate-Limit-Reset: 2025-07-18T20:49:54.0210812Z