Self Authorization
Self-authorize an SP-API app.
When you create a private application for your own organization you can self authorize it to access your account information. Before doing this you must register as a developer and register your application. You can self authorize your application in draft status; there is no reason to publish a private application.
Creating a public application to be authorized by selling partners
If you are creating a public application to be authorized by selling partners, go to Authorizing Selling Partner API applications.
The self authorization procedure varies depending on if you have a seller application or a vendor application.
To self-authorize your application (seller application)
-
Sign in to Seller Central with your developer credentials and navigate to Develop Apps.
-
On the Developer Central page, for the application that you want to authorize, select the arrow next to Edit App, and then select Authorize.
Accounts merged from other regions
If your selling partner account is merged with accounts in other regions, there is an Authorize app button for each of your merged accounts.
-
On the Authorize application page, choose Authorize app for each selling partner account that you want your application to access. The Marketplaces column indicates the marketplaces in which an account is active.
Authorization limits
You can not add authorizations to an application after it reaches the maximum authorization limit. Refer to Authorization Limits for more information.
A Login with Amazon (LWA) refresh token appears each time you choose Authorize app. If you choose Authorize app multiple times, a new refresh token is generated each time. Generating a new refresh token does not invalidate previous refresh tokens.
-
Save a refresh token for each selling partner account that you authorized your application to access. Later you can exchange these refresh tokens for access tokens. When you call a Selling Partner API to access a selling partner account, include the access token that corresponds to that account.
-
To authorize your application to access a different selling partner account, at the bottom of the page, choose sign in next to that account.
-
On the Seller Central sign-in page, sign in using the credentials for the selling partner account that you want your application to access.
-
On the Authorize application page, choose Authorize app to get a refresh token.
To self-authorize your application (vendor application)
-
Sign in to Vendor Central using the credentials that you used to register as a developer.
-
On the Integration menu, choose API Integration.
-
On the Developer Central page, choose the arrow next to the Edit App button, and then choose Authorize.
Administrating other vendor groups
If your vendor account is an administrator of other vendor groups, you can authorize apps for each of your vendor groups. Refer to Authorize vendor groups for application access for more information.
-
Choose Authorize app for each vendor group that you want your application to access. The Marketplaces column indicates the marketplaces in which an account is active.
A Login with Amazon (LWA) refresh token appears each time you choose Authorize app.
Authorizing app multiple times
If you choose Authorize app multiple times, a new refresh token is generated each time. Generating a new refresh token does not invalidate previous refresh tokens.
-
Save a refresh token for each vendor group that you authorized your application to access. Later you can exchange these refresh tokens for access tokens. When you call a Selling Partner API to access a selling partner account, include the access token that corresponds to that account.
-
To authorize your application to access a different vendor central account, select sign in to that account at the bottom of the page.
-
On the Vendor Central sign-in page, sign in using the credentials for the vendor central account that you want your application to access.
-
On the Authorize application page, choose Authorize app to get a refresh token.
An LWA refresh token is a long-lived token that you exchange for an LWA access token. An access token obtained through this token exchange must be included with calls to all Selling Partner API operations except restricted operations and grantless operations, which use somewhat different authorization models. After an access token is issued it is valid for one hour. The same access token can be used for multiple API calls, until it expires.
To exchange a refresh token for an access token using a generated SDK, refer to Connecting to the Selling Partner API using a generated Java SDK. To manually exchange a refresh token for an access token, refer to Connecting to the Selling Partner API.
Updated 1 day ago