Authorization Limits
The applications that you create have authorization limits and application restrictions based on the data access selection of your developer profile, and the type of Selling Partner (seller or vendor) that your application supports.
There are three types of application restrictions and authorization limits:
Private developer applications: Private developer applications are available only to your organization. Private applications are restricted to self-authorization and have a limit of 10 self-authorizations. After your application has reached the limit of 10 self-authorizations, you must either update your data selection to public developer or remove an existing self-authorization.
Public developer applications for sellers: Public developer applications for sellers are publicly available to other organizations and are authorized by sellers. Sellers must use OAuth via the Amazon Seller Central Partner Network (Amazon SCPN) authorization workflow or the website authorization workflow to authorize your application. Your seller application has a default limit of 25 OAuths while the application is unlisted (not available on the Amazon Seller Central Partner Network). After your application is listed on Amazon SCPN, your application is able to add unlimited authorizations.
Public developer applications for vendors: Public developer applications for vendors are publicly available to other organizations and are authorized by vendors. Vendors must use Oauth via the website authorization workflow to authorize your application. There is no limit on the number of vendor OAuths that you can have on your public application. Your public application (seller or vendor) has a default limit of 10 self-authorizations that may be used for internal testing of your application with different test accounts. Your Selling Partner customers must use OAuth to authorize your application.
::: daner
You can not add authorizations to an application after it reaches the maximum authorization limit. We recommend that you review all current authorizations and remove one or more authorizations from the applications in order to add a new authorization. Limits may vary depending on the Selling Partner type. Refer to the Authorization limit summary table below for more information.
:::
# Authorization limit summary table
| Application Type | Self-authorization | OAuth |
|---|---|---|
| Private | 10 | N/A |
| Public (unlisted) | 10 | Seller: 25 Vendor: Unlimited |
| Public (listed) | 10 | Seller: Unlimited Vendor: Not applicable |
# View authorization limits and usage
You can track authorization usage and limits for your application from the Developer Central page in Seller Central (opens new window) and Vendor Central (opens new window).
# From Seller Central (for public applications and private seller applications):
Sign into Seller Central using the credentials that you used to register as a developer (opens new window).
From the Partner Network menu, select Develop Apps.
From the Authorizations remaining table column, choose View. The authorization limits are enforced at the selling partner type level.
# In Vendor Central (for private vendor applications):
Sign into Vendor Central with the credentials that you used to register as a developer (opens new window).
From the Integration menu, select API Integration.
From the Authorizations remaining menu, choose View. The authorization limits are enforced at the selling partner type level.
Note: If your application’s authorization usage is nearing the limit, a warning is displayed.
# Removing an authorization from your application
To remove an authorization from your application, contact the SP-API Developer Support team (opens new window) with the Application ID and the authorization (Merchant Customer ID for sellers or Vendor Group ID for vendors).