SP-API General Frequently Asked Questions

Accounts

Do I need a Professional Selling Account to register as a Selling Partner API developer?

Select to expand the answer.

Yes, only Professional Selling Accounts can register to develop or integrate with Selling Partner API. Individual accounts are not eligible. You can upgrade your account to a professional plan at any time. You can view your selling plan type and the marketplace information under “Your Services” in Account info.

Do I need to have a professional selling account to use Sandbox endpoint?

Select to expand the answer. Yes, Making sandbox calls to the SP-API is identical to making production calls except you direct the calls to the SP-API sandbox endpoints. Calling the sandbox endpoints returns static, mocked responses for all Selling Partner APIs. Sandbox endpoint allows you to test your applications without affecting production data or triggering real-world events.

Will updating my developer profile affect existing applications or roles?

Select to expand the answer.

No. When you submit changes to update a developer profile, a new case will be created. Depending on the feedback you get on the case, you will need to update/modify your profile by the due date provided in the reply.

After I update my developer profile, how long does it take to complete review?

Select to expand the answer.

Review usually takes at least 2 weeks. If you don’t have restricted (PII) roles and are applying to them for the first time, review will take longer. Amazon needs to review the restricted (PII) roles with the latest ADP, which is frequently updated.

Authorization

Why am I not able to make successful call to Authorizations API or why getAuthorizationCode returns No MWS authorization found?

Select to expand the answer. This error is returned if you are making a request to Authorizations API using either a SP-API application or a hybrid application that has not been published yet. Please note these prerequisites for making a valid request for Authorizations API:
  • Published MWS application
  • The published MWS application was converted to hybrid application
  • The hybrid application is also published to the Amazon Selling Partner Appstore
  • All developer IDs of MWS are added to the hybrid application and the seller had authorized this application in MWS as well.

Why do I need to use the Authorization API during migration?

Select to expand the answer.

You can implement error handling with the Authorization API to fall back to MWS code when any errors occur in SP-API code during migration.

Why is the Confirm button not working when I test the Authorization Workflow?

Select to expand the answer.

For the Authorization workflow to work correctly (in both the Amazon Selling Partner Appstore and Website workflows), the SP-API application must include both the OAuth Login URI and Redirect URI details. Failure to add information for either of these fields results in the Confirm button not working.

Why is the MWS auth token not returned with spapi_oauth_code during oauth workflow process for a hybrid application?

Select to expand the answer. For a self-authorization use case (i.e. authorizing your own seller account using OAuth workflow process), no MWS Auth Token is returned.

What are the Login and Redirect URI values to be added in OAuth information when I am registering my app?

Select to expand the answer. The **OAuth Login URI** defines the login page of your website during authorization. This URI is shown after a seller consents to authorize your application.

The OAuth Redirect URI is used to redirect the browser to your application after authorization. You can specify more than one redirect by including the redirect_uri parameter in the OAuth URL. If the redirect_uri parameter is not specified, it will default to the first OAuth Redirect URI you’ve defined.

Note: OAuth Redirect URI does not support localhost: URIs. You must specify both the OAuth Login URI and the OAuth Redirect URI to successfully save them to your App registration.

When will the refresh token expire?

Private developers select to expand the answer. The refresh token is long lived.
Public developers select to expand the answer. The refresh token expires after one year.

Can we get the expiration date of refresh tokens through SP-APIs?

Select to expand the answer.

No. However, sellers will receive an email with a reminder to re-authorize their SP-API app 30 days before the expiration.

How is a publication application for sellers authorized?

Select to expand the answer.

Through December 31, 2022, users can convert authorization tokens from MWS to SP-API by using the Authorization API.

After December 31, you will need to implement OAuth authorization, with either the Selling Partner Appstore authorization workflow or the Website authorization workflow.

Publishing and editing applications

How do I publish my application? How long will the process take?

Select to expand the answer.

The process to publish your application:

  1. Access Developer Central.
  2. For the existing app to be updated, select Create listing from the pull down list Edit App for the app you want to list.
  3. Enter the app info.
  4. Submit your app.

Note: It usually takes more than two weeks to complete the whole process and publish the app.

Can I change the IAM ARN once the SP-API app has been created or when I have converted MWS to Hybrid app?

Select to expand the answer. Yes. When you edit your application information on the Developer Central page (in Seller Central or Vendor Central), you can replace your IAM ARN with a new value. Both the old and the new IAM ARN are active for 14 days, giving you time to update your authorization workflow for the new IAM ARN. After 14 days the old IAM ARN expires.

I want to update an application that is already published. If I submit the application with updated information, does it affect the existing one?

Select to expand the answer.

No. The existing application will not be affected during the publishing process. Once the changes are approved and published, the new version will display to customers.

General questions

How do I use multiple redirect URIs?

Select to expand the answer.

When a selling partner signs into your website (Step 3 in the Selling Partner Appstore authorization workflow), your application loads the Amazon callback URI into the browser and adds the redirect URI, the amazon_state parameter, and the state parameter.

To use multiple redirect URIs for your app, you must add the OAuth Redirect URIs when you register your app. Note that both the OAuth Login URI and the OAuth Redirect URI(s) values must be specified to successfully save them to your app registration. OAuth Redirect URI does not accept localhost: URIs.

When your app is configured with multiple redirect URIs, pass the redirect URI that you want to use as a query parameter in Step 3 in the Selling Partner Appstore authorization workflow. If you do not include the redirect_uri parameter, the default is the first OAuth Redirect URI you specified when you registered your application.

Does Amazon provide a client library for Ruby/PHP?

Select to expand the answer.

No. Amazon does not support a client library for Ruby/PHP.

Which version should I use when there are multiple versions of the same API?

We recommend to using the latest version. The latest versions account for earlier bugs and older versions are deprecated accordingly.

📘

Didn't help?

If you didn't see your question or the answer didn't resolve the issue you're encountering, open a Support Case and we'll help you troubleshoot.