Amazon Ads says certain campaign-management API queries will return HTTP 400 errors from November 18, 2026 unless developers change how they request records. The November 10 announcement applies to queries that use a global advertising account ID without setting their marketplace scope to GLOBAL.
For sellers using advertising software or an agency’s own tools, the practical question is whether that integration makes the affected requests. The notice does not say that campaigns will stop serving or that the advertising console is closing.
Send the notice to whoever maintains your advertising integration and ask whether it applies. A failed request could prevent a tool from retrieving campaign objects, but that is a conditional risk, not a confirmed failure in any seller account.
The account header and scope determine applicability
Both conditions matter: the Amazon-Ads-AccountId header must contain a global account ID in the form amzn1.ads-account.g.*, and the request must not set marketplaceScopeFilter to GLOBAL. Amazon expressly excludes queries whose scope is GLOBAL from these requirements.
The change covers queries for campaigns, ad groups, ads, targets and ad associations. Amazon’s campaign-management guide identifies the corresponding filters as campaignIdFilter, adGroupIdFilter, adIdFilter, targetIdFilter and adAssociationIdFilter. Other filters may accompany the required object-ID filter.
What developers need to change
- Supply an ID filter for the type of object being requested.
- Omit
nextToken. These affected queries cannot continue using that pagination token. - If the request sets
maxResults, make it at least as large as the number of IDs in the filter.
Amazon says requests that do not satisfy these rules will receive a 400 error starting November 18. The guide already describes the requirements in the present tense, while the dated release note supplies the enforcement date. Neither source specifies the exact enforcement time or time zone.
Ask for a scoped check, not a blanket assurance
A useful provider response should identify whether its requests use the affected header and scope, which object types it retrieves, and whether it has updated and tested those requests. Sellers with an in-house integration can ask their developer to check the same details.
Do not assume that selling in multiple countries means the change applies, or that a tool is unaffected because it serves only one country. Amazon defines this rule by request configuration and does not provide a country-by-country applicability list.
If a provider confirms that its requests are affected, ask how it will verify successful retrieval after the deadline and distinguish request errors from missing campaign data. This notice alone is not a reason to change bids, budgets or campaign status.
Sources and scope
Checked November 15, 2026 at 8:09 a.m. EST against the live Amazon Ads release note dated November 10 and campaign-management guide. The guide displays no publication date. Both documents come from Amazon and constitute one source organization.
Seller Squash has not tested these API requests, verified a software provider’s implementation or established actual seller impact. The notice concerns the specified campaign-object queries, not a verified platform-wide outage. The featured image is an editorial illustration of identifier matching, not an Amazon interface or evidence of API performance.

