How to register for Amazon SP-API

Updated November 1, 2026. Every step below was re-checked that day against Amazon's SP-API developer documentation, which is linked at each step.

Short answer: you register in two stages. First you create a developer profile, in Solution Provider Portal or in Seller Central (Apps and Services, then Develop Apps) or Vendor Central (Integration, then API Integration), and wait for Amazon to approve it. Then you add an app client, authorize it and call the API with a Login with Amazon token. You no longer need an AWS IAM user, policy or role.

What is Amazon SP-API?

The Selling Partner API (SP-API) is Amazon's REST API for sellers and vendors. Applications use it to read and change orders, listings, inventory, FBA shipments, reports, finances and more for the accounts that authorize them. To call it you need an approved developer profile and a registered application.

Which kind of developer are you?

Amazon's registration overview sorts applications into three kinds, and the registration steps differ slightly for each:

You are buildingDeveloper typeWhere you registerWho authorizes the appWhat to have ready
A tool only your own company uses on your seller accountPrivate developer (private seller application)Seller Central: Apps and Services, then Develop Apps (or Solution Provider Portal: Settings, then Developer Profile)You, by self-authorizationA Professional selling account (Amazon says Individual accounts are not eligible), use cases, security control answers
A tool only your own company uses on your Vendor Central accountPrivate developer (private vendor application)Vendor Central: Integration, then API Integration (or Solution Provider Portal)You, by self-authorization, for the vendor group you signed in withA Vendor Central user with permission to manage SP-API apps; Direct Fulfillment needs extra restricted roles
An app other sellers or vendors will usePublic developerSolution Provider Portal or Seller Central: Apps and Services, then Develop AppsEach seller or vendor, through OAuthA public website (not login-only, not under construction), use cases, security answers, an Appstore listing

An app built for you by an agency or freelancer is still a private app if only your company uses it. Amazon's private vendor guide gives "a third-party IT company or agency creating an app for you" as an example. Keep the developer profile and the app in your own company's account.

How do you register as an SP-API developer?

The developer profile is the part Amazon reviews. Amazon's steps for a private developer, a public developer and a private vendor follow the same pattern:

  1. Sign in. Sellers use Seller Central for their Amazon store and open Apps and Services, then Develop Apps. Vendors use Vendor Central and open Integration, then API Integration. If your company already uses Solution Provider Portal, sign in there and open Settings, then Developer Profile.
  2. Choose Proceed to Developer Profile (or View profile if you started one before).
  3. Enter your Contact Information.
  4. Under Data Access, pick the private developer option ("I build application(s) that integrate my own company with Amazon Services APIs") or the public developer option.
  5. Select the Roles you need (next section).
  6. Describe your Use Cases and answer the Security Controls questions. Amazon asks for original answers, not text copied from its policies, and says the tech team responsible for data security should answer the security questions.
  7. Accept the Solution Provider Portal Agreement, Acceptable Use Policy and Data Protection Policy, then choose Register.
  8. Watch the admin email on file. If Amazon asks for more information, Amazon says to respond within five days or the case is closed.

New companies registering through Solution Provider Portal also verify their identity first. Amazon's account set-up steps ask for a company registration number, a registered business address, a government ID or passport, a recent bank or credit card statement, and a video call with an Amazon associate, so have those ready.

Which SP-API roles should you request?

Roles decide which operations your app may call. Request only what your features need; you can add roles later through your developer profile. Amazon's roles page lists these:

RoleWhat it gives access to
Product ListingCreating and managing listings; catalog reports and feeds
PricingList prices and automated pricing; pricing reports and feeds
Inventory and Order TrackingInventory, order tracking and FBA sales reports, vendor orders, sales metrics
Amazon FulfillmentFBA and Amazon Fulfillment Network operations and reports
Amazon Warehousing and DistributionAWD shipments and inventory
Finance and AccountingAccounting and financial statements
Brand AnalyticsStore analytics: performance and how customers find and buy products
Selling Partner InsightsAccount and performance information
Buyer Communication / Buyer SolicitationMessaging buyers / asking buyers for feedback
Notifications in Seller CentralTargeted notifications to sellers inside Seller Central
Account Information / Payment Initiation Service ProviderAccount and store details / initiating payouts and refunds
Direct-to-Consumer Shipping, Tax Invoicing, Tax Remittance, Professional Services, Selling Partner Support (all Restricted)Operations that use customer personal data (PII) or support cases; extra review

Restricted roles mean more scrutiny. For a public app, Amazon's public developer page describes an architecture review with its SP-API Solutions Architecture team and a two-phase review of business verification and data security.

How do you check whether Amazon approved your developer profile?

Sign in where you registered (Solution Provider Portal, Seller Central's Develop Apps or Vendor Central's API Integration) and read the banner. Amazon's status page says that if your request is denied, you see which questions and controls were missed, fix them and resubmit the profile. You can register an application only after approval.

How do you register your SP-API application?

Amazon's production app steps:

  1. Open Develop Apps (Solution Provider Portal or Seller Central) or API Integration (Vendor Central) and choose Add new app client.
  2. Enter an app name, choose SP-API as the API type and Production as the application type. If Sellers and Vendors check boxes appear, tick the ones your app serves.
  3. Choose roles. You can only pick roles approved on your developer profile.
  4. For a public app, enter the OAuth log-in URI and redirect URI (Amazon does not accept localhost redirect URIs).
  5. Choose Save and exit. The app is created as a draft.

A private app does not need to be published. Amazon's self-authorization page says you can self-authorize it in draft: choose Authorize app for each account it should reach, and a refresh token appears. Apps are subject to authorization limits, so check those before you add accounts.

Do you still need an AWS IAM user, role or Signature Version 4?

No. Older guides, including the first version of this one, walked you through an AWS account, an IAM user, an IAM policy, an IAM role and an STS policy. Amazon's current production call guide lists only three credentials: the app's client ID, its client secret and the Login with Amazon refresh token. You trade the refresh token for an access token at https://api.amazon.com/auth/o2/token and send it in the x-amz-access-token header. Amazon's connection guide adds that access tokens expire one hour after they are issued, that every request needs a user-agent header, and that operations returning customer personal data use a Restricted Data Token instead.

Step in older SP-API guidesWhat to do now
Seller Central, Partner Network, Develop AppsSeller Central, Apps and Services, Develop Apps, or Solution Provider Portal
Create an AWS account and IAM user, save the access keyNot needed for SP-API calls
Create an IAM policy with execute-api:InvokeNot needed
Create an IAM role and paste its ARN into the app formNot needed; the app form asks for name, API type, application type, roles and (public apps) OAuth URIs
Add an STS AssumeRole policy and sign requests with AWS Signature Version 4Send a Login with Amazon access token in x-amz-access-token
Pick every role "just in case"Pick only the roles your features need; restricted roles add review

If an older tool or SDK in your stack still asks for AWS keys, it is worth checking whether it is maintained; Amazon's official samples are a good reference for current code.

What usually slows a registration down?

  • Thin use cases. Amazon decides on what your profile says. Name each feature, the data it reads and why.
  • Security answers written by someone else. Amazon wants the team that runs data security to answer them, and the answers are reviewed against its Data Protection Policy.
  • Restricted roles you do not need. Each one adds questions. Leave PII roles out unless a feature truly ships, labels or invoices orders.
  • Missing the five-day reply window. Amazon closes the case if you do not answer its questions in time.
  • The wrong account owning the app. Register in your company's own account, not a contractor's, so you keep the app if the contractor leaves.

Once your app is live, Amazon's Agent Policy applies to any automated tool that acts on your account, and our SP-API glossary entry explains the main APIs in plain words.

Who can register and build an SP-API app for you?

Ecomsellertool, a Cord4 Technologies company, has built on Amazon's seller APIs since 2017. We prepare the developer profile and security answers with you, keep the app in your company's account, and build the integration: order sync, inventory, reports, FBA shipments or AI agents. Tell us the job in a project brief, or see our SP-API development work.

One example is an advanced analytics and reporting system for large sellers, with WMS and inventory forecasting:

Analytics and reporting dashboard built on Amazon SP-API

More of our builds are in the portfolio. Rather talk it through? Schedule a call or contact us.

Questions people ask about SP-API registration

Can I register for SP-API with an Individual selling account?
Not for a private seller application. Amazon's registration overview says you need a Professional selling account; Individual accounts are not eligible, and you can upgrade.

Do I need my own developer registration if an agency builds the app?
If the app is only for your company, register as a private developer in your own account and let the agency build it. If the agency's app serves many sellers, it is the agency's public app and you authorize it.

What do I need before I start the developer profile?
Amazon's preparation checklist asks for your business details, ID and a recent bank or card statement, written use cases, and, for restricted roles, your security, data handling and data retention documentation.

How long does approval take?
Amazon does not publish a fixed time. It reviews each profile and may open a case with questions; answer within five days to keep the case open.

Can I add roles after the app is live?
Yes. Request the role on your developer profile, apply it to the app once approved, and re-authorize to get a refresh token that includes the new role, as Amazon's roles page describes.