Creators API vs PA-API v5: 2026 Guide for WordPress Affiliates

Creators API vs PA-API v5: 2026 Guide for WordPress Affiliates | PaapiPlugin

Last updated: 2026-04-30

Quick answer: after May 15, 2026, the Creators API is the only Amazon product API that still works. If you applied for PA-API v5 access years ago and have not yet hit Amazon's 10 qualifying sales threshold for the Creators API, your WordPress plugin needs to support both so you can keep working through the transition. PaapiPlugin supports both right now, so the choice is really "which credential do I enter today?" not "which API do I bet my site on?"

Why this comparison matters today

Amazon deprecated PA-API v5 today, April 30, 2026, and the endpoint fully retires on May 15, 2026. Every WordPress affiliate running a plugin that talks to Amazon is either already migrated, in the middle of migrating, or about to find out the hard way that their product grids stopped responding. For the full timeline, retirement specifics, and the AWS Signature V4 to OAuth 2.0 mechanics, read our full deprecation timeline.

This post is the decision-frame partner to that one. You already know the deadline. The question now is which API to enter into your plugin's settings panel, who can use which, and how to keep your site running while Amazon's old auth method goes quiet. The short version is below as a side-by-side, then we walk through the picks and a 5-step setup for the Creators API.

The two APIs side-by-side

Dimension	PA-API v5 (legacy)	Creators API (current)
Authentication	AWS Signature V4 with Access Key ID and Secret Access Key	OAuth 2.0 with Client ID and Client Secret
Lifecycle status	Deprecated April 30, 2026; endpoint retires May 15, 2026	Active, recommended by Amazon for all new integrations
Parameter naming	PascalCase (`Keywords`, `SearchIndex`, `ItemCount`, `ItemIds`, `Resources`)	lowerCamelCase (`keywords`, `searchIndex`, `itemCount`, `itemIds`, `resources`)
Eligibility	Open to any approved Amazon Associate with a valid account	10 qualifying referred sales in the last 30 days; only the primary Associates account owner can register the application
Marketplaces	All Amazon Associates marketplaces	All Amazon Associates marketplaces (BR, CA, FR, DE, IN, IT, JP, MX, NL, ES, UK, AE, US, and others)
Recommended for	Existing integrations running the clock down to May 15	Every new affiliate site, plus migrations off PA-API v5

Resource cap to know about: both authentication paths are subject to Amazon's 15-resource cap per request (search and getItems alike). If you are porting code, you do not gain or lose resource headroom by switching auth methods. The cap is a property of the API itself, not of the credentials you use to talk to it.

When to pick which

Pick Creators API if...

You are setting up a new affiliate site and you already have 10 qualifying referred sales in the last 30 days

You are the primary owner on your Amazon Associates account (a co-owner cannot register the application)

You want a single set of credentials that will keep working past May 15, 2026 with no further migration work

You are comfortable with the OAuth 2.0 token flow (most modern plugins, including PaapiPlugin, handle this for you)

Pick PA-API v5 if...

You already have working PA-API v5 keys and your site is live, today, with affiliate revenue flowing

You have not yet hit the 10-qualifying-sales bar Amazon requires for Creators API access

You understand that the endpoint retires May 15, 2026 and you have a calendar reminder to switch credentials before then

You want to avoid scrambling on May 15 by applying for Creators API access now and keeping it in your back pocket

Pick a plugin that supports both if...

You are mid-migration and want to verify Creators API works on your site before fully retiring your PA-API v5 keys

You are still under the 10-sales threshold and want to fall back to PA-API v5 for the next two weeks while you cross it

You manage multiple sites or client sites where some accounts qualify for Creators API and others do not

You want the migration to be a settings change, not a migration project, with no shortcode rewrites or page edits

The third bucket is where most working affiliates land in 2026. PaapiPlugin supports both authentication methods today (AWS Signature V4 for PA-API v5, OAuth 2.0 for the Creators API), so you can pick whichever credential set is ready first and switch later from the same settings panel. See the full feature list for everything that carries across both.

How to set up the Creators API in 5 steps

If you are migrating off PA-API v5, or starting fresh, this is the path. Each step is short. Total real time depends on Amazon's approval queue, which is the slowest part. The full step-by-step credential walkthrough also lives in our setup documentation if you want to bookmark it for later.

Get set up with the Creators API

Step 1: Apply for Creators API credentials

Sign in to Amazon Associates Central and open Tools > Creators API to start the application. The form takes a few minutes; Amazon reviews on its own schedule.

Step 2: Confirm eligibility before you submit

Amazon requires 10 qualifying referred sales in the last 30 days, and only the primary Associates account owner can apply. If your account is shared, the original owner needs to initiate the request.

Step 3: Receive your Client ID and Client Secret

Once approved, Amazon issues an OAuth 2.0 Client ID and Client Secret. Treat them like a password: store them in a password manager, do not paste them into public Slack channels or screenshots.

Step 4: Enter credentials in PaapiPlugin Settings

Open Settings, paste your Client ID and Client Secret, and pick the marketplace your Associates account is registered against. Save. The shortcodes you already have on your pages stay exactly as they are.

Step 5: Click Test Connection and verify

Test Connection runs a real request against Amazon and reports back. If it returns OK, your [psfa_search] shortcodes are now pulling product data through OAuth 2.0. Visit a page that uses one and confirm products render.

That is it. A settings change, not a migration project. Your existing layouts, filters, deal badges, and cached product data all carry over with no rework.

Frequently asked questions

Will the Creators API replace PA-API v5 entirely?

Yes. April 30, 2026 is Amazon's deprecation date and May 15, 2026 is the date the PA-API v5 endpoint actually shuts off. After May 15, the only way to pull live Amazon product data through the official channels is the Creators API with OAuth 2.0. Plugins that have not added Creators API support by then will stop returning product data; the AWS Signature V4 endpoint will reject every request.

What if I have not hit 10 qualifying sales yet?

You are in the awkward middle. Amazon requires 10 qualifying referred sales in the last 30 days before they will issue Creators API credentials, so brand-new affiliates are gated. Your move is to keep PA-API v5 working through May 15 while you grow the sales count, then apply the moment you cross the threshold. A plugin that supports both APIs lets you stay on PA-API v5 today and flip to Creators API the day your application is approved, with no rework on the page side.

Do I need to rewrite my shortcodes when I switch?

Not in PaapiPlugin. The authentication change is a settings panel concern; your [psfa_search] shortcodes, layouts, filters, and deal badges all keep working untouched. If you are using a different plugin, the answer depends on how that plugin was built. The migration trap to look out for is parameter naming: PA-API v5 used PascalCase like Keywords and SearchIndex, while the Creators API uses lowerCamelCase like keywords and searchIndex. A plugin that handles this for you should not require any shortcode edits.

Are the rate limits or marketplaces different?

Both APIs run against the same Amazon Associates marketplaces (BR, CA, FR, DE, IN, IT, JP, MX, NL, ES, UK, AE, US, and others), and both are subject to Amazon's 15-resource cap per request on search and getItems endpoints. Practical throttling is governed by your Associates account standing rather than the auth method you choose, so picking Creators API does not buy you more headroom or cost you any. The shape of the response data is the same; only the credentials and parameter casing differ.

Can I use both APIs at once for safety?

You can keep both credential sets configured in PaapiPlugin and switch between them from the Settings panel. That gives you a safety net during the transition: enter your Creators API Client ID and Client Secret, run Test Connection, browse a couple of pages to verify products are loading, and only then retire the PA-API v5 keys. If anything looks off, switching back is one click. After May 15, 2026 the PA-API v5 path stops returning data regardless, so think of dual configuration as a transition tool rather than a permanent setup.

What happens to my cached product data when I switch?

Cached product data carries over because PaapiPlugin's cache is keyed on the request, not on the auth method. You will see existing search results and product details continue to render from cache while new requests start hitting Amazon through OAuth 2.0. If you want to force fresh data after switching, clear the plugin cache from the Settings panel; otherwise it expires naturally on the standard cache TTLs and refills with Creators API responses going forward.

Pick the API that fits, keep the plugin that does both

PaapiPlugin supports PA-API v5 and the Creators API today, so the migration is a settings change, not a migration project. Start free with 5 categories and 50 products, then upgrade when you are ready.

View Premium Plans Get PaapiPlugin Free

See the full feature list →