verapli
Sign inJoin free
Menu

Guides · commerce · Verification-gated

Amazon Selling Partner API (SP-API) developer registration

Create a Solution Provider Portal account with identity verification (documents plus a video call), submit a developer profile (private or public, roles, use cases, security controls) for Amazon's review, then register an app client to get Login with Amazon (LWA) credentials and self-authorize to get a refresh token.

Researched · not yet run liveLast researched 25 October 2026 · Amazon · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

A Solution Provider Portal account (linked to an Amazon login and verified business) holds one developer profile that sets private or public data access and approved roles. App clients registered under it get LWA credentials; each selling partner account that authorizes an app yields a refresh token.

  • Amazon login (primary user) personal owned by the personApp registration and self-authorization need the primary account user.
  • Solution Provider Portal account organisation owned by the business · under Amazon login (primary user)Identity verification is done by the administrator for themselves and the company.
  • Developer profile developer · under Solution Provider Portal accountPrivate (own business only) or public (Appstore apps serving other sellers); roles decide which APIs and data you can use.
  • App client project · under Developer profileHas an LWA client ID and client secret; secret must be rotated every 180 days.
  • Seller Central or Vendor Central account otheroptionalThe selling account whose data the app reads; it authorizes the app and yields a refresh token.

A professional selling account is not needed to develop against SP-API from the Solution Provider Portal.

Restricted roles (PII, e.g. buyer names and addresses) add a three-stage review including a call with an Amazon solution architect.

Have ready

  • Government-issued photo ID or passport of the primary contact, scanned, plus the original for the video call [1]Needed for: Verify your identity (documents and video call)
  • Recent bank or credit card statement as proof of address [1]Needed for: Verify your identity (documents and video call)
  • Business licence (if applicable), company registration number and registered business address [1]Needed for: Verify your identity (documents and video call)
  • Phone to receive a PIN by SMS or call during verification [1]Needed for: Verify your identity (documents and video call)
  • A device with a video camera for the identity verification video call [1]Needed for: Verify your identity (documents and video call)
  • Public HTTPS website describing your services to Amazon sellers, with privacy policy, terms of service and contact details (public developers) · Inaccessible, under-construction, login-only or insecure sites are not accepted. [4]Needed for: Submit the developer profile (private or public)
  • Written use cases and security-control answers (free text under 500 characters) matching how you meet the AUP and Data Protection Policy [4]Needed for: Submit the developer profile (private or public)

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Register for the Solution Provider Portal

    Sign in with your Amazon login, choose Register, acknowledge the setup terms, enrol your Amazon account and pick "Build applications that use SP APIs". You press each button yourself.

    • Guided by hand
    • Human step: You accept the terms

    Where: https://solutionproviderportal.amazon.com/

  2. Verify your identity (documents and video call)

    Enter business details, verify your phone with a PIN, upload proof of identity and address, then join a video call with an Amazon employee and show your photo ID. verapli never uploads documents.

    • Guided by hand
    • Human step: You prove your identity
    • After: Register for the Solution Provider Portal

    Where: https://solutionproviderportal.amazon.com/

  3. Submit the developer profile (private or public)

    Under Develop Apps, complete contact information, data access (private or public), roles, use cases and security controls, accept the Solution Provider Portal Agreement, Acceptable Use Policy and Data Protection Policy, and register. Amazon opens a case with next steps.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Verify your identity (documents and video call)
    The provider says
    Review for standard (non-restricted) roles typically takes one to two weeks; restricted PII roles go through a longer three-stage review (no time given). [2]
    If something goes wrong (3)
    • Amazon asks for more information on the case.: Reply within five days; unanswered cases are closed and your SP-API access stays unchanged, so you would have to resubmit. [3]
    • Public developer profile rejected for the website.: Make the site public over HTTPS with no security warnings, describe your services to Amazon sellers, and add privacy policy, terms and contact details. [4]
    • Restricted (PII) role requested.: Prepare a data-flow architecture, storage and incident response description for the security and technical reviews, or drop the role if you do not need PII. [2]

    Where: https://solutionproviderportal.amazon.com/

  4. Register an app client

    As primary user, open Develop Apps, choose "Add new app client", select the API type and seller and/or vendor, and save.

    • Guided by hand
    • Human step: You press submit
    • After: Submit the developer profile (private or public)

    Where: https://solutionproviderportal.amazon.com/

  5. Copy the LWA client ID and client secret

    View the app's LWA credentials in the Solution Provider Portal (or Seller/Vendor Central). verapli captures the secret by selector.

    • verapli co-pilot
    • After: Register an app client

    verapli captures SP_API_LWA_CLIENT_SECRET here by plain code: encrypted in your browser, never shown to AI.

    Where: https://solutionproviderportal.amazon.com/

  6. Self-authorize the app to get a refresh token

    As Primary User of the selling account, choose "Authorize app" to generate a refresh token. Public apps instead get tokens through the OAuth authorization flow with each seller.

    • verapli co-pilot
    • Human step: You press submit
    • After: Register an app client

    verapli captures SP_API_REFRESH_TOKEN here by plain code: encrypted in your browser, never shown to AI.

    If something goes wrong (1)
    • Cannot add another authorization.: The app has hit its authorization limit; review the authorization limits for private and public apps. [6]

    Where: https://solutionproviderportal.amazon.com/

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can get you bannedThe rules say

Policy breaches end API access

Not complying with the Acceptable Use Policy may lead to suspension or termination of Amazon Services API access. [9]

Can get you bannedThe rules say

No multiple accounts to dodge limits

Creating several Solution Provider accounts or applications to get around throttling quotas is prohibited. [9]

Can get you bannedThe rules say

Never ask sellers for passwords or keys

Do not request or accept sellers' Amazon passwords or access keys, and never share your own keys. [9]

Can cost moneyThe rules say

Strict PII rules

Customer PII may only be used for merchant-fulfilled shipping and must be deleted within 30 days of order delivery unless law requires otherwise; non-PII data is limited to 18 months. [10]

Can cost moneyThe rules say

Secrets expire every 180 days

LWA client secrets must be rotated every 180 days; after the deadline SP-API calls fail. Old secrets stop working seven days after you generate new ones. [7]

Worth knowingThe rules say

Access keys that do not make a successful call in 90 days are deleted. [9]

Worth knowingPeople report

Developer fees were announced then dropped

Amazon announced a $1,400 annual fee and GET-call fees for third-party developers in 2026, then reportedly cancelled them. [to verify current status on an Amazon page] [12]

What you end up with

Env varSecretFormatWhat it is
SP_API_LWA_CLIENT_IDnot secretamzn1.application-oa2-client.…Login with Amazon client ID of the app client
SP_API_LWA_CLIENT_SECRETsecretLogin with Amazon client secret (rotate every 180 days)
SP_API_REFRESH_TOKENsecretAtzr|…Long-lived refresh token for one authorized selling account

Renewals

  • Rotate the LWA client secret for every app: every 180 days [7]

Pricing

  • Free tier: Sellers and vendors using SP-API for their own business were not charged even under the announced 2026 fee plan.
  • Third-party developer fees announced for 2026 were reportedly cancelled. [to verify]

Source [12]

For agents

The same entry as JSON: /api/v1/entries/amazon/selling-partner-api · requirements /api/v1/requirements/amazon/selling-partner-api · terms /api/v1/terms/amazon/selling-partner-api.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Amazon Selling Partner API (SP-API) developer registration, and how long will it take?"
  → tools/call requirements { "provider_id": "amazon/selling-partner-api" }

Sources

  1. SP-API onboarding Step 2: Create a Solution Provider Portal account Sign in at solutionproviderportal.amazon.com, Register, enrol the Amazon account, choose "Build applications that use SP APIs", then verify identity - business location/type/name, company registration number and registered address, phone PIN, primary contact details, upload proof of identity and proof of address, then a video call with an Amazon employee showing photo ID; needs a device with a camera. · accessed 25 October 2026 · official
  2. SP-API onboarding Step 3: Create a developer profile Standard-role profile review typically takes one to two weeks; restricted (PII) roles go through a three-stage review - business, security, and a technical review meeting with an Amazon solution architect. · accessed 25 October 2026 · official
  3. Register as a private developer (SP-API) Private developer registration via Develop Apps (contact info, data access, roles, use cases, security controls, accept the Solution Provider Portal Agreement, AUP and DPP); Amazon opens a case with next steps; respond within five days or the case closes and access stays unchanged; evaluation criteria are not disclosed. · accessed 25 October 2026 · official
  4. Register as a public developer (SP-API) Public developers need a publicly accessible website describing services to Amazon sellers (not under construction, login-only or with security warnings); restricted roles need PII use-case answers and an architecture review (possibly a screen-share demo); restricted review phase 1 checks HTTPS, privacy policy, terms of service and contact details; security free-text answers under 500 characters; case updates go to the administrator email. · accessed 25 October 2026 · official
  5. Register your application (SP-API) Primary account user signs in to the Solution Provider Portal, Develop Apps, Developer Central, "Add new app client", choose API type and seller/vendor; authorization limits apply to public and private apps. · accessed 25 October 2026 · official
  6. Self-authorize your application (SP-API) "Authorize app" generates a long-lived refresh token per account; generating a new one does not invalidate earlier ones; you must be the Primary User of the Seller Central account; LWA client ID and secret are shown in Seller Central, Vendor Central or the Solution Provider Portal. · accessed 25 October 2026 · official
  7. Rotate your application's LWA credentials (SP-API) Rotate LWA client secrets every 180 days; notice 90 days before; old credentials expire seven days after new ones are generated; missing the deadline makes SP-API calls fail. · accessed 25 October 2026 · official
  8. SP-API general FAQ A professional selling account is not needed to develop or integrate with the SP-API when registering in the Solution Provider Portal. · accessed 25 October 2026 · official
  9. Amazon Services API Acceptable Use Policy Never share or request access keys or Portal passwords; do not circumvent throttling with multiple accounts or applications; customer PII only for merchant-fulfilled shipping; no targeting customers for marketing or reviews; no pooling data across sellers to sell to third parties; non-compliance may result in suspension or termination; access keys with no successful call in 90 days are deleted. · accessed 25 October 2026 · official
  10. Protect Amazon API applications - data retention and recovery Data Protection Policy - retain PII no longer than 30 days after order delivery unless law requires. · accessed 25 October 2026 · official
  11. Updates to the Data Protection Policy and Acceptable Use Policy (effective 25 November 2025) DPP adds account lockout after ten failed logins, TLS 1.2+, a key management system, an incident point of contact, 18-month limit on non-PII data, 12-month log retention, critical vulnerabilities fixed within seven days. · accessed 25 October 2026 · official
  12. Amazon drops SP-API fees after developer pushback (PPC Land) Reports that Amazon cancelled the announced $1,400 annual fee and GET-call usage fees for third-party developers, saying it "will not move forward with the SP-API usage and annual fees at this time". [to verify against an Amazon page] · accessed 25 October 2026 · community

Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Amazon is not affiliated with verapli.