API Limits and Optimization

API Limits:

GET The server applies an 8 kB limit to GET requests. If a request exceeds this size, it will return a 414 Request-URI Too Large error.

POST POST requests send data in the Body, so URL length is not relevant. However, the system has internal limits on the length of task names, team names, task descriptions, etc.

For descriptions, the limit is 65 kB (65 536 characters). If the limit is exceeded, the extra content will simply be trimmed - and the system will not return an error.

Request frequency. The limit is 1 request per second. If exceeded, the API returns a “too many requests” error.

Record count per request. The system allows a maximum of 10 000 records in a single response. For example, if an account contains more than 10 000 tasks, a request attempting to retrieve all tasks at once will return:

“Too many tasks (10000 max)”.

Recommendations:

• Use webhooks instead of frequent polling whenever possible — this greatly reduces the number of requests.
• To avoid hitting API limits and to reduce system load, avoid sending many single-item requests. Instead, use bulk data retrieval with filters. This significantly reduces the number of requests, speeds up data processing, and improves integration stability.
• If your integration requires many requests due to business logic, please contact us via the support form.
  
  We will review your case and try to help - for example, by adding new parameters to the API to reduce the number of requests.

​