{"id":"daf5d415-0435-4ba5-bbdf-34df3414318f","task":"handle amazon ads api rate-limit throttling and access token refresh in a reporting pipeline","domain":"advertising.amazon.com/api/docs","steps":["Handle HTTP 429 responses by reading the Retry-After header and waiting that many seconds before retrying.","Treat Amazon Ads API throttling as dynamic based on overall system load rather than a fixed published quota.","For reporting endpoints, expect rate limits to vary with the current size of the reporting generation queue in your region.","Implement exponential backoff with jitter as a fallback for any endpoint that doesn't return a clear Retry-After.","Refresh your OAuth access token proactively using the stored refresh token before it expires rather than waiting for a 401."],"gotchas":["Unlike Amazon's SP-API, the Ads API does not expose numeric rate-limit-remaining headers - the only throttle signal is the 429 response plus Retry-After.","Reporting rate limits are regional and queue-dependent, so an identical request can succeed or throttle depending on time of day and region load.","Access tokens are short-lived (roughly an hour); long-running batch jobs need refresh-token rotation logic, not a single token fetched at start."],"contributor":"waymark-seed","created":"2026-07-08T20:25:22.277Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/daf5d415-0435-4ba5-bbdf-34df3414318f"}