To provide the best experience for all our customer we enforce a rate limit on our REST API. The default limit is 250 requests per minute. This is calculated with a sliding window of length 1 minute, so your request will be rejected, if from 1 minute ago until now you have made more than 250 requests. When the request is rejected, the API will return a response with status code 429 (Too Many Requests) and the following response body as an example:

{
    "RetryAfterSeconds": 14,
    "Message": "The request was throttled. The limit of 250 requests per minute is reached",
    "Type": "TooManyRequestsException"
}

It includes an appropriate error message as well as amount of time (in seconds) to wait until the client will be allowed to make the next request. This delay is also included in Retry-After header, specified in seconds.

The limit is applied per Application token or system/user pair if CRM-login is used. This means, if you create multiple tokens at Configurations/Integration/API - each of them will get a separate quota of 250 requests per minute.

The limit should be enough for regular usage. For example: continuously making 4 requests every second will never reach the limit. It also allows for short bursts of requests, so you can use all your 250 calls in the first second (still limited by the api throughput), but in this case you will have to wait 59 seconds to be able to call the api again.

Rate limiting takes effect on the 1^st of October 2021.

To access the new log from the API, you can use our History API located here:

It provides some basic functionality to work with comments and other log records.
Use the same authentication as you would for this REST API. Set an Authorization header with the value of "Bearer {token}". The same access token can be used with both APIs.