Selling Partner API BlogVideos
SP-API DocsDeveloper ConsoleSupport
SP-API DocsDeveloper ConsoleSupport

Use a single SP-API application to authorize multiple Vendor Central accounts

Use the self-authorization page in Vendor Central to authorize multiple vendor groups/Vendor Central accounts to a single application.

by Supriya P., Solutions Architect, Selling Partner Developer Services | May 9, 2023

This post shows you how to use the self-authorization page in Vendor Central to authorize multiple vendor groups to a single application. This approach reduces the need to create identical applications for each individual vendor group for authorization.

About Vendor Central self-authorization

Vendor Central applications are created for a particular vendor group ID that is tied to the developer account. When you create a private application for your own organization, you can self-authorize and generate a refresh token to access SP-API for that account and all Vendor Central accounts that you have access to.

As a developer, you can create authorization grants and generate refresh tokens to a single application for each of your Vendor Central accounts. This reduces the need to create developer profiles and multiple identical applications for each individual vendor group/Vendor Central account for authorization.

You can authenticate with another set of credentials while remaining logged into your Vendor Central account. Once logged in, you can create an authorization grant for any Vendor Central account to which the logged-in user has access.

Tutorial

This tutorial helps you set up authorization grants and generate a refresh token between your applications and any vendor group or the Vendor Central account to which you have administrative access.

Prerequisites

You need these prerequisites to complete this tutorial:

  • Register as a developer on Vendor Central.
  • A private SP-API Vendor Central application in draft status.
  • A Vendor Central account that is an administrator of other Vendor Central accounts.

Self-authorize your application in Vendor Central

The first step in this process is to self-authorize your application.

  1. Sign in to Vendor Central with the credentials you used to register as a developer.

  2. On the Integration menu, choose API Integration.

  3. On the Developer Central page, for the application that you want to authorize, choose the Edit App drop-down menu, and then choose Authorize.

View of Developer central showing to select Edit App and then Authorize

Authorize the SP-API application

  1. On the Manage Authorizations page, in the Action column, choose Authorize app for each Vendor Central account that you want your application to access.
A view of the Manage Authorizations page showing applications and buttons to authorize them.

View accounts on the Manage Authorizations page

A Login with Amazon (LWA) refresh token is generated for each application. A new refresh token generates each time you choose Authorize app. Generating a new refresh token does not invalidate your previously generated refresh tokens.

A view of the manage authorizations page showing refresh tokens after they are generated.

Generate Refresh Tokens from the Manage Authorizations page

For ease of reference, you can store your existing LWA credentials securely in an encrypted location for each Vendor Central account that you authorized your application to access. You can use these refresh tokens to get access tokens for calling Selling Partner APIs. When you call a Selling Partner API to access a selling partner account, include the access token that corresponds to that account. For more information, refer to Connecting to the Selling Partner API.

If you don’t see your desired vendor groups/accounts, follow the steps in the next section to authorize your application to access a different Vendor Centralaccount.

Authorize your application to access a different Vendor Central account

  1. On the Manage Authorizations page, scroll to the bottom and choose sign in to that account.
The Manage Authorizations page highligting the link to sign into that account located at the bottom of the page.

Choose sign in to that account

  1. Sign in to Vendor Central using the credentials for the Vendor Central account that you want your application to access.
  2. On the Manage Authorizations page, choose Authorize app to get a refresh token. You can use these refresh tokens to get access tokens for calling Selling Partner APIs. For more information, refer to Connecting to the Selling Partner API.

Remove authorizations from your application

There is a maximum limit of 10 self-authorizations for generating refresh tokens at the application level. When your application has reached the limit of 10 self-authorizations, you must either remove an existing self-authorization or contact Vendor Central Support to increase your quota.

  1. Sign in to Vendor Central with the credentials you used to register as a developer.
  2. On the Integration menu, choose API Integration.
  3. On the Developer Central page, for the application that you want to remove authorizations, choose the Edit App drop-down menu, and then choose Authorize.
  4. On the Manage Authorizations page, in the Revoke Authorization section, expand Self-Authorizations to view all active self-authorizations.
  5. For any authorization that you want to remove, choose Revoke.
The revoke authorizations button displays to the right of authorized apps.

The Revoke application button

Conclusion

In this post, you learned how to authorize multiple Vendor Central accounts/vendor groups. You also learned how to create an authorization grant for multiple Vendor Central accounts. This process eliminates the need to create multiple developer accounts and applications for each Vendor Central account so you can pull data for multiple Vendor Central accounts/vendor groups from one Vendor Central account.

For more information about this process, refer to Self authorization. For any issues or inquiries, contact Vendor Central Support.

👍

Have feedback on this post?

If you have questions or feedback on this post, we'd like to hear from you! Please vote and leave a comment using the tools at the bottom of this page.

Subscribe to updates via RSS feed.