SP-API General FAQ
Frequently asked questions for SP-API.
Accounts
Do I need a Professional Selling Account to register as a Selling Partner API developer?
Select to expand the answer.
No, you don't need a Professional Selling Account to develop or integrate with Selling Partner APIs. You can create a developer Account on Solution Provider Portal. For more information, refer to Registering as a developer.
Do I need to have a professional selling account to use Sandbox endpoint?
Select to expand the answer.
No, you don't need a Professional Selling Account to develop or integrate with Sandbox endpoints. You can create a developer Account on Solution Provider Portal. For more information, refer to Registering as a developer.
You can call the SP-API sandbox in the same way you call SP-API, except you direct sandbox calls to the SP-API sandbox endpoints. Calling the sandbox endpoints returns static, mock responses for all Selling Partner APIs. This means that you can test your applications without affecting production data or triggering real-world events.
Does updating my developer profile affect existing applications or roles?
Select to expand the answer.
No. Updates to your developer profile don't impact any of your existing applications or roles.
When you submit changes to update a developer profile, a new case is created. Depending on the feedback you get on the case, you'll need to update or modify your profile by the due date that's specified in the reply. These updates don't affect your roles or apps.
After I update my developer profile, how long does it take to complete review?
Select to expand the answer.
Review usually takes at least two 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 doesn't the Confirm button work 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.
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 does not expire.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.
You can 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.
Follow the steps in List Your App on the Selling Partner Appstore.
Note
It usually takes more than two weeks to complete the whole process and publish the app.
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. After 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 in to 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?
Select to expand the answer.
We recommend to using the latest version. The latest versions account for earlier technical issues and older versions are deprecated accordingly.Need more help?
For additional support, contact Selling Partner API Developer Support. For vendor applications, submit a support case in Vendor Central by navigating to Vendor Central > Support > Contact Us > API Integration.
Updated 15 days ago