{"id":50288,"date":"2026-11-16T12:08:49","date_gmt":"2026-11-16T06:38:49","guid":{"rendered":"https:\/\/www.getastra.com\/blog\/?p=50288"},"modified":"2026-11-17T12:47:25","modified_gmt":"2026-11-17T07:17:25","slug":"amazon-sp-api-updates","status":"publish","type":"post","link":"https:\/\/www.getastra.com\/blog\/compliance\/amazon-sp-api-updates\/","title":{"rendered":"Amazon SP-API Updates 2026: Security &amp; Compliance Changes Tracker"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Amazon has shipped three material SP-API updates in 2026 that every Solution Provider needs on the compliance radar. The 25 August 2026 Data Protection Policy revision expanded the pentest and vulnerability scanning scope to include APIs, added web application firewall and device storage encryption requirements, and mandated a 15-minute screen lock.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Amazon also reversed the SP-API developer fees in May 2026 and tightened ShipperTrackingNumber validation for the Brazil store in August.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This page tracks every Amazon SP-API update from 2026, newest first, with source citations and the compliance action each one requires.<\/p>\n\n\n<div class=\"gb-container gb-container-e43a8917\">\n\n<h3 class=\"wp-block-heading\"><strong>TLDR;<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The 25 August 2026 DPP update is the biggest 2026 compliance shift.&nbsp;<\/li>\n\n\n\n<li>APIs are now explicitly in pentest and scanning scope, a WAF is required on internet-facing endpoints, and a 15-minute screen lock plus 10-attempt lockout policy are mandatory.<\/li>\n\n\n\n<li>Amazon reversed the planned SP-API developer fees in May 2026. The $1,400 annual subscription and monthly usage fees that would have started in January and April 2026 are off the table.<\/li>\n\n\n\n<li>The Brazil Amazon store now enforces strict ShipperTrackingNumber validation. URLs and special characters are silently rejected.<\/li>\n\n\n\n<li>If your last pentest predates 25 August 2026 and does not cover APIs as a distinct scope category, assume your next review will flag it.<\/li>\n\n\n\n<li>Continued SP-API use after 25 August 2026 counts as acceptance of the updated DPP, Solution Provider Portal Agreement, and Acceptable Use Policy.<\/li>\n<\/ul>\n\n<\/div>\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"25_August_2026_Data_Protection_Policy_Solution_Provider_Portal_Agreement_and_Acceptable_Use_Policy_update\"><\/span>25 August 2026: Data Protection Policy, Solution Provider Portal Agreement, and Acceptable Use Policy update<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The most consequential Amazon SP-API update of 2026. Amazon updated three policies simultaneously, and the changes apply to every Solution Provider with SP-API access.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Announced:<\/strong> 12 August 2026 via the SP-API changelog. <strong>Effective:<\/strong> 25 August 2026.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Sources:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/developer-docs.amazon.com\/sp-api\/changelog\/sp-api-updates-solution-provider-portal-agreement-and-policy-updates-br-store-shippertrackingnumber-validation-and-listings-attribute-and-enumeration-values-changes\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">SP-API changelog entry (12 August 2026)<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/developer.amazonservices.com\/policy-update-for-sp-api\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Policy update landing page<\/a><\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What changed<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A web application firewall is required in front of every internet-facing endpoint that receives or returns Amazon data.<\/li>\n\n\n\n<li>Storage encryption is mandatory on all devices used to access the Solution Provider Portal or SP-API.<\/li>\n\n\n\n<li>A 15-minute screen lock policy is required on all endpoint devices.<\/li>\n\n\n\n<li>A 30-minute account lockout is required after 10 failed login attempts.<\/li>\n\n\n\n<li>An Incident Management Point of Contact (IMPOC) must be designated and documented.<\/li>\n\n\n\n<li>Vulnerability scanning and penetration testing requirements have been expanded to explicitly include APIs as a distinct scope category.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Who it affects<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Every Solution Provider with access to the Amazon SP-API or Solution Provider Portal. Private developers testing only against their own seller account are not exempt.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What to do before your next assessment<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Audit your current pentest scope and confirm APIs are tested and documented as a separate category. If your most recent SP-API pentest report scoped only the web application, assume it will be flagged at review. Deploy a WAF in front of every internet-facing endpoint handling Amazon data. Push the 15-minute screen lock, device storage encryption, and 10-attempt lockout policies through your MDM. Name an IMPOC and add their contact details to your incident response plan.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"August_2026_SP-API_fees_formally_removed\"><\/span>August 2026:&nbsp; SP-API fees formally removed<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Amazon\u2019s reversal of the planned SP-API developer fees was formalised through SP-API portal updates across August 2026. Originally announced on 3 November 2025, the fees would have introduced a $1,400 annual subscription from 31 January 2026 and monthly usage fees from 30 April 2026.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Effective:<\/strong> May 2026 (publicly confirmed through SP-API portal updates across May and formally referenced in August 2026 developer notices).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Sources:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/developer.amazonservices.com\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Amazon SP-API portal announcement<\/a><\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What changed<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Both the annual subscription fee of $1,400 and the monthly usage-based fees for GET API calls are cancelled. The February 2026 removal of applications without payment methods from the Selling Partner Appstore is also reversed. SP-API access remains free for all developer categories.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Who it affects<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Every third-party developer using the Amazon SP-API. Sellers and vendors using SP-API only for their own businesses were never in scope for the fees.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What to do before your next assessment<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">No compliance action required. If your 2026 Amazon SP-API budget still carries fee line items, remove them. Projects that were deprioritised because of the fee announcement no longer have a commercial blocker.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"12_August_2026_ShipperTrackingNumber_field_validation_enforcement_for_the_Brazil_store\"><\/span>12 August 2026: ShipperTrackingNumber field validation enforcement for the Brazil store<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A smaller but enforcement-significant SP-API update that quietly rejects malformed tracking submissions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Announced:<\/strong> 12 August 2026. <strong>Effective:<\/strong> 11 August 2026.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Source:<\/strong> <a href=\"https:\/\/developer-docs.amazon.com\/sp-api\/changelog\/sp-api-updates-solution-provider-portal-agreement-and-policy-updates-br-store-shippertrackingnumber-validation-and-listings-attribute-and-enumeration-values-changes\" target=\"_blank\" rel=\"noreferrer noopener\">SP-API changelog entry (12 August 2026)<\/a><\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What changed<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">For seller-fulfilled (MFN) orders in the Brazil Amazon store, the ShipperTrackingNumber field must contain only the actual carrier tracking number. URLs are silently rejected. Special characters including :\/\/, \/, ., and ? are silently rejected. When the field contains a URL, Amazon discards the tracking information and the buyer receives no tracking update.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Who it affects<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Solution Providers with applications that submit shipping confirmations for MFN orders in the Brazil Amazon store.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What to do before your next assessment<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Audit every ShipperTrackingNumber value your application has submitted to the Brazil store in 2026. Replace URLs or special-character values with raw tracking numbers. Add the CarrierCode field from the Amazon XSD catalog (case-sensitive and space-sensitive). Use Other when the carrier is not in the XSD. Include the CarrierName field, which is mandatory when CarrierCode is Other and recommended in all other cases.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"5_August_2026_LISTINGS_ITEM_ISSUES_CHANGE_v10_deprecation\"><\/span>5 August 2026: LISTINGS_ITEM_ISSUES_CHANGE v1.0 deprecation<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A deprecation notice SP-API developers using notifications need to take action before late August.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Announced:<\/strong> 5 August 2026. <strong>New subscription deadline:<\/strong> 14 August 2026. <strong>Event delivery stop date:<\/strong> 26 August 2026.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Source:<\/strong> <a href=\"https:\/\/developer-docs.amazon.com\/sp-api\/changelog\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Amazon SP-API changelog, August 2026 release notes<\/a><\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What changed<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Starting 14 August 2026, version 1.0 of the LISTINGS_ITEM_ISSUES_CHANGE notification is no longer available for new subscriptions. Requests to subscribe using v1.0 now return an error. From 26 August 2026, Amazon stopped delivering events for existing v1.0 subscriptions entirely.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Who it affects<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Solution Providers subscribed to the LISTINGS_ITEM_ISSUES_CHANGE notification v1.0.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What to do before your next assessment<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Migrate existing subscriptions to the current version of the LISTINGS_ITEM_ISSUES_CHANGE notification. Verify in staging that your event handlers accept the current version\u2019s payload shape.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"5_August_2026_Tracking_API_v2026-01-30\"><\/span>5 August 2026: Tracking API v2026-01-30<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Announced:<\/strong> 5 August 2026. <strong>Availability:<\/strong> US store.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Source:<\/strong> <a href=\"https:\/\/developer-docs.amazon.com\/sp-api\/changelog\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">SP-API changelog, August 2026 release<\/a><\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What changed<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Amazon released the Tracking API v2026-01-30 for the US store. The API returns shipment tracking details as a shipment moves through Amazon\u2019s supply chain.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Who it affects<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Solution Providers with applications in the US store that need programmatic access to in-transit shipment tracking details.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>What to do before your next assessment<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">No compliance action. If tracking visibility was a feature gap in your US-store application, evaluate the new API against your roadmap.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Standing_SP-API_compliance_requirements_worth_remembering\"><\/span>Standing SP-API compliance requirements worth remembering<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>LWA client secret rotation every 180 days.<\/strong> Applications that do not rotate lose SP-API access. Amazon sends a 90-day notice. <a href=\"https:\/\/developer-docs.amazon.com\/sp-api\/docs\/rotating-your-apps-lwa-credentials\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Source<\/a>.<\/li>\n\n\n\n<li><strong>Inactive authorization deactivation at 365 days.<\/strong> Amazon periodically deactivates SP-API application authorizations with zero API calls in 365+ days. <a href=\"https:\/\/developer-docs.amazon.com\/sp-api\/docs\/seller-authorizations-faq\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Source<\/a>.<\/li>\n\n\n\n<li><strong>The November 2025 DPP revision<\/strong> (effective 25 November 2025) is still the baseline the August 2026 update builds on. If your last compliance review predates November 2025, you are working from an outdated policy. <a href=\"https:\/\/developer-docs.amazon.com\/sp-api\/changelog\/updates-to-the-data-protection-policy-and-acceptable-use-policy\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Source<\/a>.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_to_watch_for_the_rest_of_2026\"><\/span>What to watch for the rest of 2026<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The pattern across the 2026 Amazon SP-API updates is that Amazon is tightening evidence requirements and expanding scope faster than most Solution Providers are refreshing their pentest and scanning posture. Expect further revisions to the DPP to be reactive rather than announced. The live DPP page carries no version number and no effective date, so audit-time disputes about which version applied to which engagement are harder than they should be. Save dated copies of the DPP every quarter.<\/p>\n\n\n<div class=\"gb-container gb-container-b63b9678\">\n\n<h3 class=\"wp-block-heading\">Disclaimer<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Last updated: November 16, 2026<\/strong><br><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This article is updated monthly to reflect the latest Amazon SP-API policy changes, security requirements, API updates, and compliance announcements. The information is for general guidance only and is not official Amazon advice. Always refer to the latest Amazon SP-API documentation and Data Protection Policy for authoritative requirements.<\/p>\n\n<\/div>\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_Astra_Helps_with_Amazon_SP-API_Security_and_Compliance\"><\/span>How Astra Helps with Amazon SP-API Security and Compliance<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Keeping up with Amazon SP-API policy changes requires continuous security validation, not just periodic compliance reviews. Astra helps Solution Providers address the technical security requirements introduced by the 2026 DPP updates through three complementary solutions.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.getastra.com\/services\/penetration-testing\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>Manual PTaaS:<\/strong> <\/a>Conducts comprehensive penetration testing across network infrastructure, cloud environments, APIs, applications, databases, and storage. Testing follows recognized methodologies such as OWASP WSTG, PTES, or NIST SP 800-115, with remediation validation and retesting.<\/li>\n\n\n\n<li><a href=\"https:\/\/www.getastra.com\/dast\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>Continuous DAST:<\/strong> <\/a>Continuously identifies vulnerabilities across web applications and API endpoints. It supports recurring vulnerability assessments, change-triggered testing, and security validation throughout the CI\/CD pipeline.<\/li>\n\n\n\n<li><a href=\"https:\/\/www.getastra.com\/cloud-vulnerability-scanner\" target=\"_blank\" data-type=\"link\" data-id=\"https:\/\/www.getastra.com\/cloud-vulnerability-scanner\" rel=\"noreferrer noopener\"><strong>Cloud Scanne<\/strong>r:<\/a> Identifies cloud misconfigurations and validates security controls, including encryption at rest, TLS configurations, IAM permissions, MFA enforcement, and WAF implementation.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">By combining manual penetration testing, continuous application security testing, and cloud security assessments, Astra helps organizations identify vulnerabilities, validate security controls, and maintain technical evidence for Amazon SP-API compliance reviews.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Final_Thoughts\"><\/span>Final Thoughts<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Amazon&#8217;s 2026 SP-API updates highlight a clear shift towards stricter security controls, expanded API testing requirements, and continuous compliance validation. Solution Providers must track policy changes, assess their impact on existing integrations, and update security controls before the next compliance review.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rather than treating compliance as a one-time activity, organizations should establish continuous vulnerability management, periodic penetration testing, API security validation, and documented remediation processes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With Astra&#8217;s Manual PTaaS, Continuous DAST, and Cloud Scanner, organizations can strengthen their security posture and maintain readiness for evolving Amazon SP-API requirements<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Amazon has shipped three material SP-API updates in 2026 that every Solution Provider needs on the compliance radar. The 25 August 2026 Data Protection Policy revision expanded the pentest and vulnerability scanning scope to include APIs, added web application firewall and device storage encryption requirements, and mandated a 15-minute screen lock.&nbsp; Amazon also reversed the &#8230; <a title=\"Amazon SP-API Updates 2026: Security &amp; Compliance Changes Tracker\" class=\"read-more\" href=\"https:\/\/www.getastra.com\/blog\/compliance\/amazon-sp-api-updates\/\" aria-label=\"Read more about Amazon SP-API Updates 2026: Security &amp; Compliance Changes Tracker\">Read more<\/a><\/p>\n","protected":false},"author":138,"featured_media":50313,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[696],"tags":[],"class_list":["post-50288","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-compliance"],"_links":{"self":[{"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/posts\/50288","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/users\/138"}],"replies":[{"embeddable":true,"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/comments?post=50288"}],"version-history":[{"count":1,"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/posts\/50288\/revisions"}],"predecessor-version":[{"id":50290,"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/posts\/50288\/revisions\/50290"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/media\/50313"}],"wp:attachment":[{"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/media?parent=50288"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/categories?post=50288"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.getastra.com\/blog\/wp-json\/wp\/v2\/tags?post=50288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}