Amazon SP-API 6 min read

How to Get Amazon SP-API Access (Seller Central) — Step-by-Step

SP-API setup is way simpler than Ads API. This guide shows you where to create the app client, pick roles, grab Client ID/Secret, and generate the refresh token.

By Shahzeb
Updated Jan 2026
How to Get Amazon SP-API Access (Seller Central) — Step-by-Step

What You Need Before You Start #

Before you begin, make sure you have:

  • Access to Amazon Seller Central
  • Admin-level permissions (to create/manage apps)
  • A basic idea of what you want: Orders, Inventory, Reports, Finances, etc.

Good news: for most seller-account use cases, you don’t need a long “apply & wait” flow like Ads API.

Where SP-API Credentials Come From #

SP-API uses OAuth. In practice, you’ll end up with:

  • Client ID
  • Client Secret
  • Refresh Token (the important one)

The refresh token is what you store securely. Your code uses it to generate short-lived access tokens.

Step 1: Open “Develop Apps” in Seller Central #

Log in to Seller Central, then open:

  1. Menu
  2. Apps & Services
  3. Develop Apps
Seller Central: Apps & Services → Develop Apps

Step 2: Create a New App Client #

On the Develop Apps page, create a new app client. You’ll usually see an option like “Add new client” or “Create new app”.

Solution portal: add new client / create new app client

Then proceed to create the new app:

Create new app screen

Step 3: Fill the SP-API App Form + Select Roles #

When creating the client, you’ll provide:

  • App name (anything is fine)
  • API type → choose SP-API
  • Roles (permissions)

Tip: If you’re not sure which roles you’ll need, pick the ones you expect (Orders, Reports, Inventory, Catalog, Finances). Missing roles later usually means “access denied”.

App form:

SP-API app creation form

Roles selection:

SP-API roles selection / permissions

Step 4: Copy Client ID + Client Secret #

Once the app client is created, open it and copy:

  • Client ID
  • Client Secret

Tip: Store these securely. You can rotate secrets later if needed.

Client ID and Client Secret screen

Step 5: Authorize the App and Generate Refresh Token (EU vs NA) #

This is the step people miss: even if you have client ID/secret, you still need to authorize the app to generate a refresh token.

When authorizing, choose the right region:

  • EU for Europe marketplaces
  • NA for North America marketplaces

Important: If you authorize the wrong region, you’ll waste hours later thinking your credentials are “broken”.

Authorization screen showing refresh token

What You Should Have Now #

At this point, you should have:

  • Client ID
  • Client Secret
  • Refresh Token

That’s the full credential set needed to start calling SP-API.

Common Issues (Quick Fixes) #

  • No refresh token: you likely didn’t authorize the app
  • Access denied: missing roles — edit the app and add permissions
  • Wrong region: authorized EU but calling NA (or vice versa)

What You Can Build With SP-API #

Once you’re in, SP-API becomes your backbone for seller automation:

  • Daily order pulls → Sheets/DB
  • Inventory alerts
  • Sales dashboards per SKU / per marketplace
  • Reports automation
  • Refunds / returns monitoring

Need help implementing this?

Tell me your stack and what you want automated. I'll reply with a simple plan tailored to your needs.

Found this helpful? Share it:

WhatsApp