# About this migration guide
This guide explains what the Selling Partner API is, how it differs from Amazon Marketplace Web Service (Amazon MWS), and shows you how to convert your Amazon MWS application to a hybrid Selling Partner API application.
# Advantages of Selling Partner API
The Selling Partner API is a REST-based API that helps Amazon selling partners programmatically access their data on listings, orders, payments, reports, and more. Applications using the Selling Partner API can increase selling efficiency, reduce labor requirements, and improve response time to customers, helping selling partners grow their businesses. The Selling Partner API is a modernization of Amazon MWS and includes all functionality previously available from Amazon MWS. All future development will only be available for the Selling Partner API.
The following table lists and describes some of these advantages.
| Feature | Description |
|---|---|
| Roles for Selling Partner API | A role is the mechanism used by the Selling Partner API to determine whether a developer or application has access to an operation or resource. As a developer, you must request and qualify for a particular role, or you will not be able to access the operations and resources grouped under that role. The roles in the Selling Partner API are more fine grained than the roles in Amazon MWS. Whereas Amazon MWS had three roles, the Selling Partner API has 11. See Roles in the Selling Partner API for a detailed explanation of roles in the Selling Partner API, as well as a list of roles and their definitions. |
| Restricted Data Token (RDT) requirement | The Selling Partner API protects customers' Personally Identifiable Information (PII) by requiring a Restricted Data Token (RDT) with calls to restricted operations (operations that return restricted data). For information about getting and using RDTs to call restricted operations, see the Tokens API Use Case Guide. |
| Sandbox for Selling Partner API | Selling Partner API provides a sandbox environment that allows you to test your applications without affecting production data or triggering real-world events. For more information, see Selling Partner API Sandbox in the Selling Partner API Developer Guide. |
# Features of Selling Partner API
For every Selling Partner API there is a Swagger model, an API reference, and in some cases a use case guide. Client libraries are also included to help with authenticating calls to Selling Partner APIs.
New features of the Selling Partner API include:
- REST-based APIs with JSON-formatted input and output.
- New endpoints that are supported in all regions.
- Step-by-step instructions for automated SDK generation (see the Selling Partner API Developer Guide).
- A sandbox feature with separate sandbox endpoints for testing with mock data.
- A dynamic usage plan that automatically adjusts rate limits for each selling partner based on a variety of measures.
- Support for Selling Partner API applications across all regions.
- Support for Restricted Data Tokens (RDTs), which help protect customers' Personally Identifiable Information (PII).
| New and updated Selling Partner APIs | Description |
|---|---|
| A+ Content API | Enables selling partners to create and edit A+ content. |
| Authorization API | Exchanges an existing MWS Auth Token with a Selling Partner API authorization code. |
| Catalog Items API | Provides detailed information about the Amazon catalog. |
| FBA Inbound Eligibility API | Checks ASIN eligibility for participation in Fulfillment by Amazon (FBA) to avoid creating inbound shipments for ineligible ASINs. |
| FBA Inventory API | New and improved FBA inventory API with new features for FBA sellers. |
| FBA Small and Light API | Supports the FBA Small and Light program. |
| Messaging API | Enables selling partners to send supported message types to customers. |
| Notifications API | Includes new notifications for branded item content changes, product type name changes, MFN order status changes, and B2B offer changes. |
| Pricing API | Gets product pricing and offer information. |
| Product Fees API | Gets estimated fees for a product. |
| Sales API | Generate sales history reports. |
| Services API | Enables service providers to get and modify their service orders. |
| Shipping API | Provides programmatic access to Amazon's shipping services. |
| Solicitations API | Enables selling partners to send non-critical solicitations to customers. |
| Tokens API | Provides a secure way to access a customer's Personally Identifiable Information (PII). |
For a full list of Selling Partner APIs, refer to SP-API models.
# Migration tutorials
The steps to move from Amazon MWS to SP-API vary depending on whether you have a private application or public application:
- For private applications (self-authorized), follow the steps in Tutorial: Create a private Selling Partner API application
- For public applications (authorized by Selling Partner), follow the steps in Tutorial: Convert a public Amazon MWS application into a Selling Partner API application