Developer types and roles
Who can build an SP-API application, what registration asks for, which roles an application can hold and how the restricted ones work.
As Amazon publishes it
Every statement on this page restates Amazon's public documentation, linked under Sources.
Private and public applications
Private application
- Who uses it: only the developer's own organization.
- Authorization: self-authorized.
- Listing: not listed.
Public application
- Who uses it: any seller or vendor.
- Authorization: authorized by sellers or vendors through OAuth (see Selling partner).
- Listing: must be listed in the Selling Partner Appstore, under the Solution Provider Portal Agreement.
Registration
- Registration is completed by the primary account user.
- A private seller application needs a professional selling account in Seller Central; individual selling accounts are not eligible.
- Before registering, a developer:
- reviews the Acceptable Use Policy, the Data Protection Policy and the Solution Provider Portal Agreement (see Data protection and retention);
- works out which roles to request;
- as a public developer, meets Amazon's website guidelines.
- The developer profile application has a 500-word limit and must be original content, not copied from Amazon's policies.
- The team responsible for data security answers its security control questions. Amazon's Key Security Control Guidance explains how those controls map to Data Protection Policy requirements.
- Every person using the Solution Provider Portal also completes identity verification.
Roles
A role is a set of operations. An application can call only the operations of the roles granted to it.
- Account Information Service Provider — information about the selling partner account, including information about the seller's business.
- Amazon Fulfillment — Amazon fulfillment operations and shipping services such as Fulfillment by Amazon (FBA).
- Amazon Warehousing and Distribution — AWD shipment and inventory operations.
- Brand Analytics — Amazon store analytics reports, such as seller and vendor performance metrics.
- Buyer Communication — operations that manage messaging to and from Amazon buyers.
- Buyer Solicitation — buyer feedback solicitation operations.
- Direct-to-Consumer Shipping (Restricted) — operations that ship orders directly to customers.
- Finance and Accounting — operations that create accounting and financial statements.
- Inventory and Order Tracking — operations that analyze and manage inventory.
- Notifications in Seller Central — operations that send targeted notifications to sellers within Seller Central.
- Payment Initiation Service Provider — operations that initiate the payout to the seller's deposit method.
- Pricing — operations that determine list prices and automate product pricing.
- Product Listing — operations that create and manage product listings.
- Professional Services (Restricted) — operations that provide add-on services such as assembly and installation.
- Selling Partner Insights — operations that retrieve information about a selling partner's account and performance.
- Tax Invoicing (Restricted) — operations that generate tax invoices to comply with tax regulation.
- Tax Remittance (Restricted) — operations that calculate and remit sales taxes.
Requesting a role
- Roles are requested in the developer profile. Amazon evaluates the request and approves or denies it; a denied request can be corrected and resubmitted.
- A role must be approved in the developer profile before it can be added to an application.
- After a new role is approved and added to the application, the selling partner must authorize the application again so that new access tokens carry the role.
Restricted roles and personal data
Personal data
The four roles marked (Restricted) — Direct-to-Consumer Shipping, Professional Services, Tax Invoicing and Tax Remittance — give access to personally identifiable information (PII) about Amazon customers. Handling PII brings the additional requirements of Section 2 of the Data Protection Policy (see Data protection and retention).
Operations that return restricted data are called with a Restricted Data Token (RDT) from the Tokens API instead of the plain access token. For example:
- the Orders API's
getOrders,getOrder,getOrderItemsandgetOrderBuyerInfo; - the Reports API's
getReportDocumentfor restricted reports; - Merchant Fulfillment shipment operations.
The RDT is issued for the restricted resources named in the request.