Skip to main content

Autotask API Rate Limit

Updated

Autotask API Rate Limit Rules Analysis

To ensure response times for all REST API users and to prevent system crashes due to coding errors, Autotask has established the following API rate limiting rules:

Rate Limiting Threshold

  • Hourly Request Limit

The number of external requests between each database and the API is limited to 10,000 per hour. This limit applies to all integrations and is checked every 60 minutes.

Usage Notifications

  • Usage-Related Delays

As the number of requests approaches the rate limit threshold, the API will introduce usage-based delays. This means that during high-load conditions, the speed of request responses may decrease.

Normal Usage Impact

  • Reasonableness of Threshold Settings

This threshold is designed to be relatively lenient, and under normal circumstances, users should not be affected. However, if multiple high-usage integrations run simultaneously, or if a single integration makes frequent API calls through multiple threads, it may reach this limit.

Consequences of Exceeding Limits

  • Error Messages and Service Suspension

Once the request volume exceeds the limit, users will receive error messages and experience a temporary suspension of API services. This means that subsequent API requests will be denied until the request volume decreases after reaching the rate limit threshold.

References

For more details, please refer to the official documentation: Autotask API Rate Limit Guidelines.

 

MSPbots Autotask API Rate Limit Policy

After integrating with Autotask, apply the following throttling strategies. If you want to connect to Autotask integration, see Autotask Integration Setup.

  • When the API request volume triggers the MSPbots alert threshold, synchronization for the related interfaces will be automatically halted.
  • At the start of the next synchronization cycle, the system will automatically check if the alert threshold has been triggered. If not, the system will automatically resume API data synchronization to ensure service stability and efficiency.

Rate Limit Rules

  • When API request volume exceeds 5000, synchronization for the TICKETS-HISTORY-SYNC API will stop.
  • When API request volume exceeds 6000, synchronization for the SERVICE-LEVEL-AGREEMENT-RESULTS-SYNC API will stop.
  • When API request volume exceeds 8000, synchronization for the TICKET-NOTES-SYNC API will stop.

API Interface Descriptions

  1. TICKETS-HISTORY-SYNC
    • This API interface requests historical data for each TICKET by ID.
  2. SERVICE-LEVEL-AGREEMENT-RESULTS-SYNC
    • This API interface requests service level agreement data for each TICKET by ID.
  3. TICKET-NOTES-SYNC
    • This API interface is used for full data synchronization.

If you have any questions, please feel free to contact us.

 

Related articles