Self Authorization

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.

📘

Note

To learn how a selling partner can authorize a public application, refer to Authorizing Selling Partner API Applications.

To self-authorize your application

1. Sign in to Solution Provider Portal with your developer credentials.

   📘

   Note

   For Seller Central users, sign in to Seller Central for your marketplace and navigate to Apps and Services, then Develop Apps.

   For Vendor Central users, sign in to Vendor Central for your marketplace and navigate to Integration, then API Integration.

2. For the application that you want to authorize, select the arrow next to Edit App, and then select Authorize.

   ❗

   Important

   For Solution Provider Portal only: If you want to authorize a Seller Central account, sign in to that account using the link on the Manage Authorizations page.

   If your selling partner account is merged with accounts in other regions, an Authorize app button appears for each of your merged accounts.

   If your vendor account is an administrator of other vendor groups, you can authorize apps for each of your vendor groups.

3. On the Authorize application page, choose Authorize app for each selling partner account that you want your application to access. The Marketplaces column shows the marketplaces in which an account is active.

   🚧

   Warning

   You can't 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.

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

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.