Migrating from PA-API 5.0 to the Amazon Creators API

Amazon shut down PA-API 5.0 on May 15, 2026. Requests to it now fail with AccessDenied: Product Advertising API is deprecated. The Amazon Creators API offers the same kind of product data, but almost everything around it changed: the credentials, the login, the addresses and the parameter names. Amazon’s own version of this guide is the official migration page.

What changes

	PA-API 5.0	Amazon Creators API
Credentials	AWS Access Key + Secret Key	New Credential ID + Credential Secret + Version (old keys do not work)
Login	Every request signed with AWS Signature Version 4	An access token you fetch once and reuse for an hour (OAuth 2.0)
Address	`webservices.amazon.*/paapi5/…`	`https://creatorsapi.amazon/catalog/v1/…`
Marketplace	In the request body	In the body and in the `x-marketplace` header
Parameter names	PascalCase: `ItemIds`, `PartnerTag`	lowerCamelCase: `itemIds`, `partnerTag`
Offers	`Offers.Listings`, `Offers.Summaries`	Only `offersV2.*`

Step by step

Get new credentials. Register for the Creators API in Associates Central and create a 3.x credential (how).
Replace the signing code. Remove the AWS Signature v4 logic. Fetch an access token instead and cache it until it expires.
Change the address. Use https://creatorsapi.amazon/catalog/v1/… and add the x-marketplace header.
Rename the parameters. All request keys and resource names change to lowerCamelCase, e.g. ItemInfo.Title → itemInfo.title.
Switch to OffersV2. Replace every Offers.* resource with its offersV2.* counterpart.
Update error handling. Errors now come with type, message and reason. The error lexicon explains each code.
Test every operation with your new credentials in the Scratchpad before you deploy.

Coming next

Side-by-side PA-API 5.0 and Creators API examples for every operation
A full mapping table from PA-API 5.0 resources to their new names
Notes for common WordPress plugins and libraries