Amazon Product Advertising API Alternatives in 2026

PA-API 5 is deprecated—what should developers use now?

If you are searching for an Amazon Product Advertising API alternative because an existing integration stopped working, the first question is not “Which API has the most fields?” It is “Which API matches my relationship with Amazon?”

Amazon's current PA-API 5 deprecation notice says Product Advertising API 5.0 has been deprecated and replaced by Creators API. It also says calls to the old endpoint receive 403 Forbidden with an AccessDeniedException. New and existing affiliate integrations should therefore evaluate Creators API first, not build new PA-API 5 code.

There is no single replacement for every use case. The practical choices in 2026 are:

• Amazon Creators API for publishers, influencers, and affiliate product experiences.
• Amazon Selling Partner API (SP-API) for seller and vendor software.
• Amazon Business Product Search API for business purchasing and procurement integrations.
• Glade API for developers who need a normalized interface to public Amazon product data without seller OAuth.

Glade is an independent API and is not operated or endorsed by Amazon. The official APIs are the right choice whenever you need private account data, seller actions, affiliate attribution, or Amazon Business purchasing consent.

Option 1: Amazon Creators API

Creators API is the supported successor to PA-API 5. Amazon describes it as a REST API that gives publishers, influencers, and affiliate partners access to catalog data for shopping experiences. Its documented operations include:

• SearchItems for keyword, filter, and browse-node searches.
• GetItems for product details by ASIN or another identifier.
• GetVariations for a product's variations.
• GetBrowseNodes for category information and hierarchy.

The access requirements are important. According to the Creators API introduction, an applicant must be enrolled in Amazon Associates for the target marketplace, have at least 10 qualifying sales in the previous 30 days, register for API access, and generate credentials. The registration guide further says the Associates account must have final acceptance and that only its primary owner can register an application.

Creators API is the best starting point when:

• Your application recommends or advertises Amazon products to an audience.
• You participate in Amazon Associates and meet its access requirements.
• You need official affiliate-compatible product links and content.
• You can follow the applicable Associates operating agreement, license, and display policies.

It is less suitable when you are not operating an affiliate experience or cannot yet meet the program's qualifying-sales requirement.

Option 2: Amazon Selling Partner API

SP-API is often called an Amazon product API, but its center of gravity is seller and vendor operations. Amazon's onboarding overview lists workflows such as catalog management, pricing, orders, shipments, and inventory.

For product lookup, the Catalog Items API provides two relevant operations:

• searchCatalogItems searches the catalog by identifiers or keywords.
• getCatalogItem retrieves details for a specific ASIN and marketplace.

The default usage plan shown in the Catalog Items reference is five requests per second with a burst of five, although Amazon notes that an account's actual plan can differ and may be returned in x-amzn-RateLimit-Limit.

SP-API also has a more involved authorization model than an API-key product-data service. Public applications must use Login with Amazon OAuth so selling partners can authorize access. Private applications are self-authorized. Developers must register, request appropriate roles, and meet the requirements for their application type. Amazon's registration overview notes that a private seller application requires a Professional selling account, while public seller and vendor apps must be listed in the Selling Partner Appstore.

SP-API is the best starting point when:

• You are building for Amazon sellers or vendors.
• A selling partner can authorize your application.
• You need listings, inventory, pricing, orders, fulfillment, or other account-scoped operations.
• You are prepared for Amazon's developer registration, role, security, and authorization requirements.

It is usually the wrong abstraction for a consumer-facing product explorer that has no seller relationship.

Option 3: Amazon Business Product Search API

Amazon Business exposes a separate Product Search API for product data available to Amazon Business customers. Its operations cover keyword search, product and offer retrieval, and lookup of multiple ASINs. Amazon's guide requires API onboarding and access to the Business Product Catalog role.

This API is designed for procurement applications where an Amazon Business user or group is part of the transaction. Results can reflect business purchasing context, guided-buying policies, and regional availability.

Amazon Business Product Search API is the best starting point when:

• You are integrating Amazon Business purchasing into a procurement workflow.
• Your users or organization have the required Amazon Business relationship and consent.
• You need business offers and buying-policy context, not a general public catalog feed.

Option 4: Glade API

Glade provides a normalized interface for public Amazon product data. A Glade API key works across REST, GraphQL, and MCP without requiring each of your users to connect an Amazon seller account.

The current API covers 17 operations across 13 marketplaces, including product details, search, autocomplete, variants, offers, reviews, seller profiles, categories, deals, bestsellers, identifier conversion, and clearly labeled stock and sales estimates. All interfaces share the same validation, marketplace semantics, quota accounting, cache metadata, and error model.

Here is a product lookup using an ASIN:

export GLADE_API_KEY="glade_test_lookup_your_secret"

curl --request GET \
  "https://gladeapi.com/api/amazon/product?asin=B0D1XD1ZV3&domain=US" \
  --header "Accept: application/json" \
  --header "API-KEY: $GLADE_API_KEY"

And a keyword search:

curl --get "https://gladeapi.com/api/amazon/search" \
  --header "API-KEY: $GLADE_API_KEY" \
  --data-urlencode "searchTerm=mechanical keyboard" \
  --data-urlencode "domain=US" \
  --data-urlencode "page=1"

Glade is a practical choice when:

• You want to prototype or ship an Amazon product-data feature behind a conventional API key.
• Your users should not have to authorize a seller account.
• You need one normalized contract across several public catalog surfaces.
• You want the same operations available to application code and AI tools through REST, GraphQL, or MCP.
• You need explicit request, cache, data-freshness, rate-limit, and usage metadata.

Glade is not the right choice when:

• You need to create listings, change prices, manage inventory, process orders, or access private seller data. Use SP-API.
• You need official Associates attribution or Amazon-provided affiliate content under the Creators API license. Use Creators API.
• You need Amazon Business purchasing consent and guided-buying context. Use Amazon Business APIs.
• Your planned use of product content is not permitted by applicable policies or third-party rights. An API response does not grant additional display or redistribution rights.

Feature comparison by decision, not field count

Marketing comparisons often reduce APIs to a checklist of fields. That misses the expensive part of an integration: eligibility, authorization, policy fit, and operating model.

Choose Creators API if affiliate attribution is central

Creators API is official, aligned with Amazon Associates, and designed for publishers and creators. Its tradeoff is program eligibility and an affiliate-specific contract. If you already used PA-API 5 for an Associates site, migration to Creators API should be your default plan.

Choose SP-API if a seller or vendor is the customer

SP-API gives you official, account-authorized workflows that a public catalog API cannot replace. The tradeoff is a substantial onboarding and OAuth surface. That complexity is justified when your product manages a selling business.

Choose Amazon Business APIs for purchasing workflows

The Product Search API can expose business-specific catalog and offer context inside a procurement integration. Its scope and onboarding are tied to Amazon Business rather than general product discovery.

Choose Glade when developer access and normalized public data matter

Glade minimizes setup for public product-data features and exposes more discovery surfaces behind one contract. Its tradeoff is that it is an independent service: it cannot grant Amazon account permissions, replace Amazon program membership, or override Amazon's policies.

A migration plan for an existing PA-API application

Do not start by translating request fields one for one. First identify what your product actually does.

1. Inventory the user promise. Separate affiliate links, product discovery, seller operations, business purchasing, analytics, and internal research.
2. Map each promise to the correct authorization model. Associates experiences map to Creators API; seller/vendor actions map to SP-API; procurement maps to Amazon Business; unauthenticated public-data features may fit Glade.
3. Define a provider-neutral internal model. Keep your UI dependent on fields such as asin, marketplace, title, price, and fetchedAt, rather than one provider's entire response.
4. Treat fields as optional. Product pages differ, offers disappear, and not every marketplace exposes the same observation.
5. Attach marketplace and freshness to stored data. A price without its store, currency, and observation time is not safe to compare.
6. Build an error translation layer. Distinguish invalid input, unauthorized access, missing resources, throttling, upstream failure, and timeout.
7. Run both paths during migration. Compare normalized results for a representative set of products, marketplaces, variants, books, unavailable items, and products without a visible price.
8. Review policy and attribution requirements before cutover. Technical parity does not imply equivalent rights to store or display content.

This structure also keeps your application replaceable if eligibility, pricing, or product requirements change again.

Production concerns shared by every Amazon product API

Regardless of provider, a durable integration should handle these concerns explicitly:

Marketplace context

Never cache solely by ASIN. Include the marketplace and any location or language inputs that can affect the result.

Freshness

Separate slow-changing catalog facts from fast-changing offers. Record when the data was fetched and decide how old it may be for each user experience.

Throttling and concurrency

Read rate-limit headers, limit background concurrency, back off with jitter, and avoid retry storms. A documented request-per-second value is not permission to launch an unbounded batch.

Optional and changing fields

Use runtime validation at the provider boundary. Missing price, image, seller, or rating data should degrade a feature—not crash the page or silently become zero.

Secret management

Keep credentials in a server-side secret store. Never ship Creators API credentials, SP-API refresh tokens, Amazon Business tokens, or Glade API keys to the browser.

Compliance

Review the governing API license, Amazon program policies, and third-party rights. Apply the required attribution and caching rules for the API you choose. For Glade, review the data-sources policy and acceptable-use policy before production use.

Try the Glade path

If your use case fits Glade's boundaries, start with the Amazon ASIN API guide, inspect the complete API documentation, and use the free tier to test real request and error handling. The free tier requires no subscription or payment method.

The best Amazon Product Advertising API alternative is not the service with the longest feature list. It is the one whose authorization model, policies, data scope, and operational behavior match the product you are building.

References

• Amazon PA-API 5 deprecation notice
• Amazon Creators API introduction
• Amazon Creators API registration
• Amazon SP-API developer onboarding
• Amazon SP-API registration overview
• Amazon SP-API Catalog Items reference
• Amazon Business Product Search API reference
• Glade API documentation