SP-API Vendor FAQs

To be sure that your vendor group contains all of the vendor codes that you want your application to access, check the vendor codes in your vendor group. If you need to, you can add or remove vendor codes from your vendor group at any time.

To add or remove vendor codes from your vendor group:

1. Go to Vendor Central. See Vendor Central URLs for a list of URLs by country.
2. Sign in using the credentials for the Vendor Central account with the vendor group for which you want to add or remove vendor codes.
3. Select the Support link at the top of the page.
4. On the Support page, select the Contact Us button.
5. On the Contact Amazon support page, select Settings and Account Management, then choose Account Settings.
6. In the Settings and Account Management box, at the bottom, select Still need help?.
7. Follow the instructions to contact Amazon support.

Note: To register as a developer, you will need to create an Amazon Web Service (AWS) account.

• Identity and Access Management (IAM) is a feature offered at no additional charge.
• If you sign up for the free tier and the only AWS service you use is IAM, your account should continue to be free. You might incur charges after 12 months for the use of other AWS services by your users, if you use any other AWS services.
• You can reference the IAM Pricing FAQ and the AWS Free tier info which includes information about which services always have free usage tiers or limits and which ones have 12 month free trials.

No. API integration is based on access to specific roles. You can create one application client and add the required roles to have access to the APIs. So one application can have both the roles, if you need access to both Retail and DF APIs.

You can appeal the decision via a support case with our vetting team, and they will provide insight on the missing details or any relevant changes that the submission needs to have to get the application approved.

Yes. If you use multiple vendor groups to manage your vendor codes, for Selling Partner API integrations we recommend that you either:

• Create a new vendor group containing all of the vendor codes you need, or
• Choose an existing vendor group and add the vendor codes that you need.

You can add or remove vendor codes in a vendor group at any time. However once you have registered as a developer, you cannot change the vendor group associated with that developer.

If you want to maintain separate API integrations for different businesses, you can. Having a developer account as an administrator of the other vendor group allows for the authorization of a single application for multiple vendor groups. For more information, refer to the Vendor Self Authorization documentation.

You can go to the Vendor Direct Fulfillment APIs Use Case Guide, the Vendor Retail Procurement Use Case Guide or you can navigate to the “Integration” > “API Integration” section of your Vendor Central account, and select the “API Documentation” hyperlink to download the documentation.

The “Getting Started” page under the “Integration” menu item also has additional details including FAQs on EDI vs API usage.

• For Direct Fulfillment API access, you must have the Direct-to-Consumer Shipping role added to your application client.
  NOTE: Direct-to-Consumer Shipping is a restricted role. Restricted roles allow access to Personally Identifiable Information (PII) about Amazon Buyers so you will be required to provide additional information about your data use and security controls.
• For Retail Procurement API access, you must have the Amazon Fulfillment role added to your application client.

When registering your application, the IAM ARN that you provide must be for the IAM entity to which you attached the IAM policy from Step 3. Create an IAM policy.

In this workflow, that IAM entity is the IAM role from Step 4. Create an IAM role. If you register your application using your IAM user, be sure that the IAM policy is attached to it. Otherwise your calls to Selling Partner API will fail.

We recommend registering your application using an IAM role to help you better control access to your AWS resources.

These steps are available in the Selling Partner API Developer Guide under Register your application

• NA: (US, CA, MX)
• EU: (ES, UK, FR, DE, IT)
• India: (IN)
• FE: (JP, AU, SG)

Make sure to enable the API integration using the correct vendor code, region, and country since this is not yet available in all marketplaces.

Yes. The Selling Partner API provides a sandbox environment that allows you to test your applications without affecting production data or triggering real-world events. Making sandbox calls to the Selling Partner API is identical to making production calls except you direct the calls to the Selling Partner API sandbox endpoints.

The authorization and authentications models are the same for sandbox calls and production calls. Calling the sandbox endpoints returns static, mocked responses for all Selling Partner APIs. You can refer to these mocked responses in the Swagger model JSON file for the API that you want to call. For more information, see How to make a sandbox call to the Selling Partner API and Selling Partner API sandbox endpoints.

For information on third-party developers and vendor direct fulfillment APIs, see Vendor Central.

No, Vendor API is built on the Selling Partner API (SP-API) and the registration process and integration is described in the Selling Partner Developer Guide.

For more information, see the Connecting to the Selling Partner API within the Selling Partner Developer Guide.

You must open a support case to request postman collections today. We are working to make them available soon in Vendor Central for download.

Testing is not available with vendors' production data right now. Vendors can test in the sandbox environment using mock request and responses. Sandbox testing performs syntax and semantic validation but does not perform business validation.

To learn more about making a sandbox call to SP API, see The Selling Partner API sandbox topic.