SP-API General FAQs

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.

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.

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.

• 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.

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.

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.

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.

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

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.

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.

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.

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.

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