Amazon Creators API vs PA-API 5.0: What Affiliates Need to Know in 2026
If you’re an Amazon affiliate, you’ve probably heard about the Amazon Creators API. Maybe you’ve seen it mentioned in forums. Maybe your current plugin stopped working recently. Or maybe you’re just wondering what all the fuss is about.
In 2026, Amazon officially began transitioning affiliates from the Product Advertising API (PA-API 5.0) to the new Creators API. This isn’t just a minor update—it’s a complete overhaul of authentication, endpoints, and how product data is structured.
In this post, I’ll break down everything you need to know about the Creators API, how it differs from PA-API 5.0, and what it means for your WordPress affiliate site.
What Was PA-API 5.0?
For years, the Product Advertising API (PA-API) was the standard way for affiliates to access Amazon product data. Version 5.0 was the last major release, and it worked well for its time.
PA-API 5.0 allowed affiliates to:
- Search for products by keyword or ASIN
- Retrieve product titles, images, prices, and descriptions
- Get availability status for products
- Use AWS Signature Version 4 for authentication
But the internet changed. Content became more visual. Mobile traffic surpassed desktop. And PA-API 5.0 started to show its age. Amazon knew they needed something new—something built for creators, not just developers.
Enter the Amazon Creators API
Announced in 2024 and fully rolled out in 2026, the Creators API is Amazon’s replacement for PA-API 5.0. It’s built specifically for content creators, influencers, and affiliates who produce product-focused content.
The name itself tells you something: this API is for creators. It’s designed to power the kind of content that actually converts.
Key Differences Between Creators API and PA-API 5.0
Let’s break down the major changes based on Amazon’s official migration documentation. This matters because if you’re using an older plugin, it might still be trying to use PA-API 5.0—and soon, that won’t work at all.
1. Authentication Method
PA-API 5.0: Used AWS Signature Version 4. You needed an AWS Access Key and Secret Key, and every request required a complex signature calculation.
Creators API: Uses OAuth 2.0 client credentials flow. You get a Credential ID and Credential Secret, exchange them for an access token (valid for 1 hour), and then use that token for API calls. This is simpler and allows for token caching.
2. Endpoint Structure
PA-API 5.0: Used webservices.amazon.com/paapi5/... endpoints. Each marketplace had separate endpoints.
Creators API: Uses creatorsapi.amazon/catalog/v1/... endpoints with three regional credential versions:
- Version 2.1 / 3.1 – North America (US, Canada, Mexico)
- Version 2.2 / 3.2 – Europe (UK, Germany, France, Italy, Spain, Sweden, Netherlands, Poland, Egypt, Turkey, UAE, India)
- Version 2.3 / 3.3 – Far East (Japan, Australia, Brazil, Singapore)
The version number (2.x vs 3.x) indicates which authentication system is used (Cognito vs LwA). When you generate credentials, the version is automatically assigned based on your region.
3. Parameter Naming Convention
PA-API 5.0: Used PascalCase (e.g., ItemIds, PartnerTag, Keywords).
Creators API: Uses lowerCamelCase (e.g., itemIds, partnerTag, keywords).
4. Offers Support
PA-API 5.0: Used “Offers.Listings” and “Offers.Summaries” for pricing and availability.
Creators API: Introduces OffersV2—a completely redesigned data structure. According to Amazon’s documentation: “Offers Support: Not Available. use OffersV2.” This means the old Offers format is deprecated—you must use OffersV2 with the Creators API.
5. Request Headers
PA-API 5.0: Required AWS signature headers (X-Amz-Date, Authorization).
Creators API: Requires:
Authorization: Bearer YOUR_TOKEN, Version 2.1– The token plus your credential versionx-marketplace: www.amazon.com– Specifies which marketplace to queryContent-Type: application/json
Comparison Table: PA-API 5.0 vs Creators API
| Aspect | PA-API 5.0 | Creators API |
|---|---|---|
| Authentication | AWS Signature Version 4 (Access Key + Secret Key) | OAuth 2.0 (Credential ID + Credential Secret) |
| Endpoints | webservices.amazon.com/paapi5/… | creatorsapi.amazon/catalog/v1/… |
| Token Management | AWS signature required for each request | Bearer token (valid 1 hour, cacheable) |
| Parameter Style | PascalCase (ItemIds, PartnerTag) | lowerCamelCase (itemIds, partnerTag) |
| Offers Support | Offers.Listings, Offers.Summaries | OffersV2 (improved data quality) |
| Marketplace Header | In request body | Required in x-marketplace header |
| Credential Regions | us-east-1, eu-west-1, etc. | 2.1 (NA), 2.2 (EU), 2.3 (FE) |
Migration Steps for Affiliates
According to Amazon’s documentation, here’s how to migrate:
Step 1: Register for Creators API
You must create new credentials. Your old AWS keys won’t work.
- Navigate to Associates Central and look for the “CreatorsAPI” tab
- Click “Create Application” and enter a name
- Click “Create Credential” – copy and store your Credential ID and Credential Secret
- Note your Version (2.1 for NA, 2.2 for EU, 2.3 for FE)
Step 2: Choose Your Migration Path
Amazon offers two options:
Option A: Use the New SDKs (Recommended)
Amazon provides SDKs for Node.js, Python, PHP, and Java that handle OAuth 2.0 authentication automatically. They include token caching, renewal logic, and simplified authentication flows.
Option B: Update Your Direct API Calls
If you’re making direct HTTP requests, you’ll need to:
- Remove AWS Signature Version 4 signing logic
- Implement OAuth 2.0 token retrieval
- Update endpoints from
/paapi5/to/catalog/v1/ - Add the
x-marketplaceheader - Update parameter naming to lowerCamelCase
Step 3: Update Request Parameters
| PA-API 5.0 Parameter | Creators API Parameter | Notes |
|---|---|---|
| Keywords | keywords | Changed to camelCase |
| ItemIds | itemIds | Changed to camelCase |
| PartnerTag | partnerTag | Changed to camelCase |
| Resources | resources | Resource names use dot notation |
| Marketplace | marketplace | Also required in x-marketplace header |
Step 4: Test Your Migration
Amazon recommends starting with a simple GetItems or SearchItems request to verify authentication works correctly. Access tokens are valid for 3600 seconds (1 hour), so implement token caching and renewal.
Common Migration Issues and Solutions
| Issue | Problem | Solution |
|---|---|---|
| Invalid Credentials | Using AWS Access Key/Secret Key instead of new credentials | Generate new credentials from Associates Central CreatorsAPI dashboard |
| Token Expired | Access token expired after 1 hour | Implement token caching and renewal. Check token expiry before each request |
| Wrong Endpoint | Still using webservices.amazon.com/paapi5/* | Update to creatorsapi.amazon/catalog/v1/* |
| Missing Marketplace Header | Request fails with missing marketplace information | Add x-marketplace header (e.g., x-marketplace: www.amazon.com) |
| Incorrect Authorization Header | Authorization header doesn’t include credential version | Use format: Authorization: Bearer <token>, Version <version> |
What This Means for WordPress Affiliates
If you’re running a WordPress affiliate site, the transition to Creators API has real implications.
Your Old Plugin Might Stop Working
If your current plugin is still using PA-API 5.0, it will eventually stop working. Amazon is phasing out the old API. If your product displays recently stopped showing prices or started acting strangely, this is likely why.
You Need a Plugin That Handles OAuth 2.0
The Creators API uses OAuth 2.0 with token caching. Plugins that haven’t updated to handle this authentication flow will fail to connect.
Credential Version Matters
Your plugin needs to know which credential version to use (2.1 for NA, 2.2 for EU, 2.3 for FE). This is region-specific and affects which marketplaces you can access.
OffersV2 Is the New Standard
The old Offers format is deprecated. Your plugin must use OffersV2 to get accurate pricing and availability data.
How AmDisplayPro Handles the Creators API
We built AmDisplayPro with the Creators API in mind. Here’s how we handle the changes:
- OAuth 2.0 authentication – Automatic token retrieval, caching, and renewal
- Credential version support – Choose 2.1 (NA), 2.2 (EU), or 2.3 (FE) in settings
- lowerCamelCase parameters – All requests use the correct format
- OffersV2 support – Uses the latest data format for better pricing and availability
- x-marketplace headers – Automatically handles the required headers
- Smart caching – Respects rate limits while keeping your site fast
- Geolocation built-in – Automatically detects visitor location and uses the correct regional endpoint
Creators API Operations
The Creators API supports the following operations:
| Operation | Description |
|---|---|
| GetBrowseNodes | Lookup information for a Browse Node (Amazon category) |
| GetItems | Provides item attributes, offer listings, images, and other details (up to 10 ASINs per request) |
| SearchItems | Searches for items on Amazon based on keywords |
| GetVariations | Returns variations for an item (different sizes, colors, etc.) |
Resource Types in Creators API
Resources determine what information is returned. Available high-level resources include:
- BrowseNodeInfo – Browse node information associated with an item
- BrowseNodes – Browse node information for GetBrowseNodes requests
- Images – Image URLs in various sizes
- ItemInfo – Title, Brand, Description, and other item details
- ParentASIN – The parent ASIN for an item
- SearchRefinements – Dynamic search refinements for search requests
- VariationSummary – Summary for GetVariations operations
- OffersV2 – Enhanced pricing and availability data
Frequently Asked Questions
How do I get Creators API credentials?
Visit the Register for CreatorsAPI page in Associates Central. You need to be an Amazon Associate first.
How does Creators API authentication work?
It uses OAuth 2.0 client credentials flow. Your application exchanges credentials for an access token (valid for 1 hour), which is then used to authenticate API requests.
Is there batching support?
Yes. You can specify up to 10 item IDs for GetItems and up to 10 BrowseNode IDs for GetBrowseNodes in a single request.
What happened to the old Offers format?
The documentation explicitly states: “Offers Support: Not Available. use OffersV2.” The old Offers.Listings and Offers.Summaries are deprecated.
What’s the difference between version 2.x and 3.x credentials?
Version 2.x uses Cognito authentication, while version 3.x uses Login with Amazon (LwA). Both work, but the version is automatically assigned based on your region when you generate credentials.
Final Thoughts
The Creators API is one of the biggest changes in Amazon affiliate marketing in years. The shift from AWS Signature to OAuth 2.0 simplifies authentication. The move to lowerCamelCase and OffersV2 modernizes the data structure. And the new regional version system makes multi-marketplace targeting easier.
Affiliates who adapt will benefit from better data quality, faster responses, and a more reliable API. Those who stick with outdated plugins that still use PA-API 5.0 will eventually find their product displays broken.
If you’re still using an old plugin that relies on PA-API 5.0, now is the time to switch. The old API is being phased out. Your product displays will stop working. And you’re missing out on the improved data quality that OffersV2 provides.
Have you migrated to the Creators API yet? What’s your experience been? Drop a comment below—I’d love to hear your thoughts.