Error - Too many Requests When Using Adobe Analytics API | Community
Skip to main content
H
HaithamTa
June 16, 2025
Solved

Error - Too many Requests When Using Adobe Analytics API

  • June 16, 2025
  • 2 replies
  • 916 views

Hello,
I am automating the pulldown of various Adobe Analytics elements through "https://analytics.adobe.io/api/" API calls. I noticed a few weeks ago that I started to get "Too Many Requests" errors when running the pulldown script.
I saw a previous post here: "https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform/api-error-429-too-many-requests/m-p/668236#M4443" that states that the issue may be related to a certain threshold on calls allowed to be made within a certain period of time. I can guarantee that I am not making many calls per minute in this script. The script is making an API call to Adobe Analytics about every 10 seconds.


Has there been an update to the amount of calls allowed to the API within a window of time? Is there a way to modify the amount of allowed API calls?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Vinay_Chauhan

The 429 "Too Many Requests" error usually means your org is hitting Adobe's API rate limits and it might not just be from your script alone.

Even if your script is only making calls every few seconds, it’s worth checking:

  • If any retry logic or hidden loops are unintentionally sending more requests than expected.

  • Whether others in your organization might also be running scripts or tools that use the same API credentials or company ID all those requests add up against the same limit.

  • Adding backoff handling in your script (e.g. wait and retry when a 429 is returned) to avoid compounding the issue.

Since Adobe doesn't publicly list exact thresholds, it’s a good idea to reach out to Client Care (as @jennifer_dungan also mentioned). They can confirm what limits apply to your contract and help if those limits need to be adjusted.

Hope that helps!

2 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
June 16, 2025

This might be worth checking with Adobe Client Care... they will know if you have any limitations on your contract.. or they might determine that you are making more API calls than you think (maybe there is a phantom script creating additional requests that you are unaware of), or maybe someone else in your organization is making API calls that are using up your bandwidth?

    Vinay_Chauhan
    Community Advisor and Adobe Champion
    Vinay_ChauhanCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    June 18, 2025

    The 429 "Too Many Requests" error usually means your org is hitting Adobe's API rate limits and it might not just be from your script alone.

    Even if your script is only making calls every few seconds, it’s worth checking:

    • If any retry logic or hidden loops are unintentionally sending more requests than expected.

    • Whether others in your organization might also be running scripts or tools that use the same API credentials or company ID all those requests add up against the same limit.

    • Adding backoff handling in your script (e.g. wait and retry when a 429 is returned) to avoid compounding the issue.

    Since Adobe doesn't publicly list exact thresholds, it’s a good idea to reach out to Client Care (as @jennifer_dungan also mentioned). They can confirm what limits apply to your contract and help if those limits need to be adjusted.

    Hope that helps!

      Terms & ConditionsAccessibility statement

      Loading footer...