Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates

Qlik Stitch: Understanding API Rate Limits

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Mohammed_Messaoudi

Qlik Stitch: Understanding API Rate Limits

Last Update:

Nov 13, 2025 9:27:06 PM

Updated By:

Shicong_Hong

Created date:

Nov 13, 2025 9:33:58 PM

When Stitch replicates data from SaaS sources, it must operate within the API rate limits defined by each vendor. These limits determine how many API requests can be made within a specific time period to prevent server overload. Exceeding them typically results in rate limit errors (most often HTTP 429 responses), which can temporarily interrupt data replication.

This article outlines common API rate limit errors observed in Stitch integrations and provides best practices to help you minimize and handle these limits for reliable data replication.

 

Known API Rate Limit Errors

The exact error message for exceeding API rate limits varies across platforms, but all indicate the same underlying cause — too many API requests made within a defined time window.

Refer to the table below for examples of rate limit errors observed in popular Stitch SaaS integrations | Stitch Documentation:

Integration Rate Limit Error Message
Chargebee HTTP-error-code: 429, Error: Sorry, access has been blocked temporarily due to request count exceeding acceptable limits. Please try after some time.
Facebook Ads SingerSyncError GET: 400 Message: User request limit reached
GA4 (Google Analytics) 503 429:Too Many Requests
Google Ads 429 Resource has been exhausted (e.g. check quota)…
Help Scout Too Many Requests. You reached the rate limit, Please retry after sometime.
Jira HTTP-error-code: 429, Error: The API rate limit for your organisation/application pairing has been exceeded.
Klaviyo HTTP-error-code: 429, Error: The API rate limit for your organization/application pairing has been exceeded.
Linkedin Ads HTTP-error-code: 429, Error: API rate limit exceeded, please retry after some time.
Marketo Marketo API returned error(s): [{'code': '606', 'message': "Max rate limit '100' exceeded with in '20' secs"}]. This is due to a short term rate limiting mechanism. Backing off and retrying the request.
Mixpanel HTTP-error-code: 429, Error: The API rate limit for your organization/application pairing has been exceeded.
Pardot Pardot returned error code 122 while retrieving endpoint. Message: Daily API rate limit met
Pipedrive 429 Client Error: Too Many Requests for url: https://api.pipedrive.com/v1…
Pipedrive HTTP-error-code: 429, Error: Daily Rate limit has been exceeded.
Shopify 429 Too Many Requests
Trello 429 Client Error: Too Many Requests for url: https://api.trello.com/1…
Stripe Request rate limit exceeded. You can learn more about rate limits here https://stripe.com/docs/rate-limits.
Xero HTTP-error-code: 429, Error: The API rate limit for your organisation/application pairing has been exceeded. Please retry…
Yotpo The API limit exceeded
Zendesk HTTP-error-code: 429, Error: The API rate limit for your organisation/application pairing has been exceeded.
Zoom {"code":429,"message":"You have reached the maximum daily rate limit for this API. Refer to the response header for details on when you can make another request."}

 

Stitch recommendations & solutions for rate limit errors

  • Reduce replication frequency of an integration if extractions frequently exceed the API’s rate limit.

  • Stagger replication frequency schedules for multiple integrations that connect to the same source account to reduce the number of concurrent calls.

  • Use the key-based incremental replication method | Stitch Documentation where available:

    Full Table Replication:
     Extracts all data from the Start Date indicated in the integration settings during every extraction. This usually requires many API calls as most integrations use pagination to retrieve data.
    Incremental Replication:
     Only fetches new or changed records since the last successful sync, based on a bookmark value. 
    Incremental replication can reduce API call volume by extracting less data, thereby reducing the number of API calls that would need to be made.

  • Monitor extraction logs in Stitch for frequent 429 errors.

  • Contact the API provider to request increased rate limits where applicable.

  • Contact Qlik Support if needed.

 

Environment

Labels (2)
Version history
Last update:
‎2025-11-13 09:27 PM
Updated by: