Amazon Vendor Central is a supplier platform for first-party vendors selling products in bulk to Amazon. It is used primarily by manufacturers and distributors.
- A. Set up an OAuth 2.0 HTTP connection to Amazon Vendor Central
- B. Edit HTTP application details
- C. Save, test, and authorize
Start establishing an OAuth 2.0 HTTP connection to Amazon Vendor Central in either of the following ways:
- From the Resources menu, select Connections. Then, click + Create connection at the top right.
– or –
- While working in a new or existing integration, you can add an application to a flow simply by clicking Add source or Add destination/lookup.
In the resulting Application list, select HTTP.
The Create connection pane opens with required and advanced settings.
At this point, you’re presented with a series of options for providing an Outh 2.0 HTTP authentication.
Important: This connection requires that you’ve set up an AWS account, registered as a developer, registered an Amazon Vendor Central account, and registered your application for the Selling Partner API. You’ll also need to set up an OAuth 2.0 login using Login with Amazon.
Base URI (required): Provide the base URI for the Amazon Selling Partner API. URIs are divided by region:
|North America (Canada, US, Mexico, and Brazil marketplaces)
|Europe (Spain, UK, France, Germany, Italy, Turkey, U.A.E, and India marketplaces)
|Far East (Singapore, Australia, and Japan marketplaces)
Media type (required): Specify the data format used in the HTTP request and HTTP response bodies. These data formats determine how the information is sent to the API and include JSON, XML, multipart/form-data, and URL encoded.
Authentication type (required): Select OAuth 2.0 from the list.
OAuth 2.0 client (required): Select the client pair that stores the client ID and client secret provided to you by your app. To add an iClient and configure your credentials, click the plus (+) button. Click the edit ( ) button to modify a selected client. Be sure to give the client a recognizable name for use in any other connections.
Client ID (required): Enter the client ID as found in your Amazon account.
Client secret (required): Enter the client secret as found in your Amazon account. Multiple layers of protection are in place, including AES 256 encryption, to keep your connection’s secret safe. When editing this form later, you must generate this value again; it is stored only when the connection is saved and never displayed as text.
Grant type (required): You can use the Authorization code to get an access token for web and native apps after you authorize the app, or Client credentials for apps to request an access token on their own behalf.
- Authorization code – the provided code is obtained by using an authorization server as an intermediary between the client, integrator.io, and resource owner. Selecting Authorization code enables additional required and informational settings.
- Client credentials – limits the authorization scope to the protected resources under the control of the client, or to protected resources previously arranged with the authorization server. Selecting Client credentials exposes one additional required setting.
Authorization URL: Enter the authorization code retrieval endpoint on the API provider’s authorization server.
– or –
Access token URL: In this instance, you’ll use https://www.amazon.com/ap/oa.
Set up your OAuth 2.0 overrides, configure your token authentication, and learn more about the remaining options for an HTTP OAuth 2.0 connection.
Once you have configured the OAuth 2.0 HTTP connection, you have a few options for continuing:
- Save & authorize – click this button to test the connection, and commit the new connection so that it will be available to all integrations for your account (and applied to the current source or destination app, if you created it within a flow)
- Close – click this link to exit connection creation without saving
- Test connection – click this button to verify that your new connection is free of errors
When you Save & authorize, a new browser window opens to ask you to grant access to integrator.io for the specified scopes. The refresh token is stored within this connection if you allow the request.