-
Notifications
You must be signed in to change notification settings - Fork 44
Description
Our integration has been experiencing persistent throttling errors when querying the change_history endpoint for a specific seller account.
Marketplace ID: A1F83G8C2ARO7P
Endpoint: change_history
First noticed: mid-September 2025
Behavior: Every request returns an immediate 429 response, even after 24+ hours without any calls.
Other sellers: No throttling issues observed on other accounts using the same application setup.
Sample response (notice a few fields were redacted) :
AdvertisingApiException: <class 'ad_api.base.exceptions.AdvertisingApiTooManyRequestsException'> (429, {'message': 'Too Many Requests'}, {'Server': 'Server', 'Date': 'Thu, 04 Dec 2025 00:09:51 GMT', 'Content-Type': 'application/json', 'Content-Length': '37', 'Connection': 'keep-alive', 'x-amz-rid': '---', 'x-amzn-RequestId': '---', 'x-amzn-ErrorType': 'AccessDeniedException', 'x-amz-apigw-id': '----', 'amazon-advertising-api-throttled': 'true', 'X-Amzn-Trace-Id': 'Root=---', 'Vary': 'Content-Type,Accept-Encoding,User-Agent', 'Strict-Transport-Security': 'max-age=47474747; includeSubDomains; preload'})
Expected behavior:
- After a reasonable cooldown period, requests should resume successfully within the documented rate limits.
- Even if throttled, a "Retry-After" field should have been received.
Questions / Help needed:
Are there account-specific rate limits or quota restrictions applied to this seller?
What is the expected cooldown or reset period for the change_history endpoint?
Could any quota reset or approval for limit increase be applied to resolve this?
Environment:
Amazon Ads API (python-amazon-ad-api release 0.6.7 released October 20th, 2025)
Same credentials and OAuth flow successfully used for other sellers