Apideck CLI: Query 200+ SaaS APIs from your terminal. No SDK needed. Read more

Apideck Documentation Page

Amazon Seller Central – Configuration Guide

Service ID: amazon-seller-central

Amazon Seller Central enables both individuals and businesses to sell their products and inventory on Amazon.com.

How to register an OAuth app for Amazon Seller Central

Amazon Seller Central provides access to the Selling Partner API (SP-API), a REST-based API that helps Amazon selling partners programmatically access their data on orders, shipments, payments, and much more.

Important — before you start

Your Amazon SP-API app must be in Published / Production status before it can be used with Apideck. Apps in Draft / Sandbox status only support Amazon's self-authorization flow (a refresh token generated directly in Developer Central), which Apideck does not consume. If you attempt to connect with a Draft app, Amazon's consent screen will reject the request with error MD9100.

Apideck does not provide a default OAuth app for Amazon Seller Central — you must register and publish your own SP-API app to use this connector.

Register as a developer with Amazon

1. Create a developer account and register your application

  1. Go to the Amazon Selling Partner page
  2. Click the Develop Apps button from the top left corner menu under "Apps and Services" Develop Apps
  3. Fill out the registration form with your details
  4. Accept the terms and conditions
  5. Navigate to Developer Central section
  6. Click + Add new app client Add new app client
  7. Fill in the application details:
    • Application name: Enter a meaningful name (typically your company name)
    • Application type: Select the appropriate type (SP API)
    • Business entities supported: Select the appropriate type (Sellers)
    • Roles: Select the appropriate roles. We suggest to select all roles for uninterrupted access.
    • OAuth Login URI: Enter https://unify.apideck.com/vault/callback as the OAuth Login URI
    • Redirect URIs: Enter https://unify.apideck.com/vault/callback as the redirect URI
    • Click on Save and exit button. Register App

2. Get your credentials

After your application is registered, on Developer Central you'll receive: App Credentials

  1. Client ID: A unique identifier for your application
  2. Client Secret: A secret key used to authenticate your application Client ID and Client Secret
  3. Application ID: A unique ID for your SP-API application (format: amzn1.sellerapps.app.*) Application ID

Make note of these credentials as you'll need them for the Apideck configuration.

Configure in Apideck

Head over to the Apideck dashboard for Amazon Seller Central and:

  1. Enter the following credentials from your Published SP-API app:
    • Client ID: The Client ID from your SP-API application
    • Client Secret: The Client Secret from your SP-API application
    • Application ID: The Application ID from your SP-API application
  2. Flip the enable toggle in the top-right corner of the connector card to ON
  3. Click Save settings

Testing the connection

On the same configuration page, click the Test Vault button in the top-right. This opens a Vault session pre-scoped to Amazon Seller Central where you can:

  1. Click Connect on the Amazon Seller Central tile
  2. Log in with your real Seller Central account and complete the OAuth consent flow
  3. Verify that the connection is established and make a test API call

If the OAuth consent screen returns an error, see the Troubleshooting section below.

Troubleshooting

Error: MD9100 — "The application provided is not set up for third-party authorization using OAuth"

This error is returned by Amazon's consent screen when your SP-API app is in Draft / Sandbox status. Amazon only allows third-party OAuth authorization for apps that have been Published (approved for Production).

To resolve:

  1. In Amazon Developer Central, submit your app for Production listing approval. See Amazon's documentation on registering your application for the review process.
  2. Wait for Amazon to review and Publish your app. Approval times vary depending on the roles requested.
  3. Once your app is Published, retry the connection in Apideck.

Note: Amazon's self-authorization option (the one-click flow inside Developer Central that generates a refresh token directly) is available for Draft apps but is not supported by Apideck — Apideck's flow requires the OAuth authorization-code redirect, which only Published apps can use.

Error: Invalid Client ID or Client Secret

If you receive an error about invalid credentials:

  • Double-check that you've copied the correct Client ID and Client Secret
  • Ensure there are no extra spaces or characters in the credentials
  • Verify that your application has been approved by Amazon

Error: Invalid Redirect URI

If you encounter redirect URI errors:

  • Verify that you've added https://unify.apideck.com/vault/callback to your application's redirect URIs
  • Check for any typos in the redirect URI configuration

Error: Insufficient Permissions

If you receive permission errors:

  • Review the data access permissions you've configured for your application
  • Make sure you've selected all the necessary API sections your application needs

Resolve 400 Errors

There are many possible reasons for a 400 response when making API calls. Here are the most common causes and solutions:

For more detailed information, see the Amazon SP-API documentation on resolving 400 errors.

Permissions and Credentials

Ensure the following:

  • Required roles are approved for your profile and application
  • The seller account is active

If a seller account isn't active and you're receiving 400 errors:

  1. Contact the seller and request that they navigate to Seller Central > Settings > Account Info > Charge Information
  2. If the Charge Information page displays a banner requesting a credit card update, ask the seller to update their credit card information
  3. Allow 48 hours for the updates to propagate through all Amazon systems

Note: If a seller account has not been used for 90 or more days, the account will be marked dormant, and the seller will be advised to update their credit card. Allow for a 48-hour waiting period to ensure a successful update. Afterwards, API calls can be made by that account.

Rate Limits

Rate limits apply per account-application pair. The following rate limits apply to order-related operations:

For more information, see the Amazon SP-API Orders API rate limits documentation.

Orders List (getOrders)

  • Rate limit: 0.0167 requests per second
  • Burst: 20 requests
  • Scope: Per account-application pair

Single Order (getOrder)

  • Rate limit: 0.5 requests per second
  • Burst: 30 requests
  • Scope: Per account-application pair

Order Line Items on Single Order (getOrderItems)

  • Rate limit: 0.5 requests per second
  • Burst: 30 requests
  • Scope: Per account-application pair

Additional resources

For more information about using the Amazon Seller Central connector with Apideck, visit our documentation.