SP-API General Frequently Asked Questions

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.

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 appstore
  • All developer IDs of MWS are added to the hybrid application and the seller had authorized this application in MWS as well.

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. No, you cannot change the IAM ARN after saving the SP API application. Please ensure the IAM ARN is for the IAM entity to which the IAM policy is attached. Incorrect ARN associations can lead to Access Denied errors when making SP API requests.

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.

How do I use multiple redirect URIs?

Select to expand the answer.

When a selling partner signs into your website (Step 3 in the Marketplace 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. If you do not include the redirect_uri parameter, the default is the first OAuth Redirect URI you specified when you registered your application.

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 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 Confirm button not working.

When will the refresh token expire?

Select to expand the answer.

The refresh token expires after one year. This is identical to MWS token expiration.

📘

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.