Rate limits
Our API has set rate limits which are documented below. The limits below are subject to change, and could change at any time. Please make sure any use of the Ortto API takes into account that you could be rate limited at any time, and retry as appropriate. If your request is rate limited you will receive a 429 status code response and a payload similar to the following:
json
{ "error": { "code": "rate-limit", "message": "rate limit", "try-in-seconds": 10 } }Plan rate limits
Plan
Limit (no. of requests/second)
Professional
10
Business
30
Enterprise
30
NOTE: These are the default limits for the enterprise plan. However, on this plan, Ortto can increase your rate limit upon request. If you can explain your requirements for a higher limit, these rate limits can be made significantly higher than the default values. Please contact your customer service manager or salesperson about this.
Rate limits per IP address
Limit (no. of requests)
Time (seconds)
2000
10
6000
60
Bad request rate limiter
If you send repeated bad requests to the Ortto API, your access will be limited.
The limits are as follows:
Limit
No. of seconds IP is banned for
15 bad requests in 15 seconds
15
15 bad credentials requests in 15 seconds
15
Payload limits
Name
Limit
Number of attributes per activity
15
Number of activities per payload
100
Number of contacts per payload
100
Number of activities per contact
50 activity events per activity per contact per 24 hours. See an example.
Data size per activity
16kB
Limit per payload
2MB
TIP: Use the supported bulk action payload to batch multiple requests into a single API call. This improves efficiency by reducing the total number of requests and helps ensure you stay within rate limits.
For example, when creating a large volume of contacts, you can submit them in batches of 100 per request to process them most efficiently.
Field limits
Name
Limit
String
255 unicode characters
Text
4000 unicode characters