Amazon API Documentation
This is the complete API documentation for connecting to the Amazon API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.
MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.
Meet Amazon: Global leader in e-commerce. Keep reading to get started.
Quickstart
Before you run your first Amazon request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one Amazon connection — create or choose one in Connections. Note its
connectionId.
Every Amazon action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/amazonUS/latest/actions/{actionSlug}You need a MindCloud API Key and a Amazon connection. Then call an action such as exampleNewAction:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/amazonUS/latest/actions/example-new-action" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"Every response comes back in the same envelope, with your rows in a data array:
{
"success": true,
"data": [
{ "id": "1042", "name": "Ava" }
],
"meta": {}
}After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.
Authentication
Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Amazon account that should run the action. MindCloud stores and refreshes the Amazon credentials behind that connection, so you never send provider tokens with your requests.
Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.
Amazon actions
All 59 published actions for this Amazon version. Each page documents the endpoint, arguments, and response controls.
- PUTCancel Inbound
- PUTCancel Inbound Plan
- PUTCheck Inbound Eligibility
- POSTConfirm Delivery Window Options
- PUTConfirm Inbound
- PUTConfirm Packing Option
- PUTConfirm Placement Option
- POSTCreate Feed
- POSTCreate Feed Document
- POSTCreate Inbound
- POSTCreate Inbound Plan
- POSTCreate Report
- GETexampleNewAction
- POSTGenerate Packing Options
- POSTGenerate Placement Options
- POSTGenerate Transportation Options
- GETGet Catalog Item by ASIN
- GETGet Feed
- GETGet Feed Document
- GETGet Inbound
- GETGet Inbound Operation Status
- GETGet Inbound Plan
- PUTGet Inbound Shipment
- GETGet Listing Restrictions
- GETGet Listings Items
- GETGet Order
- GETGet Order Address
- GETGet Order Items
- GETGet Orders
- GETGet Product Type Definition
- GETGet Purchase Order Status
- GETGet Purchase Order Status (Internal)
- GETGet Purchase Orders
- GETGet Report By ID
- GETGet Report By ID With Stream
- GETGet Report Document
- GETGet Reports
- GETGet Seller Account
- GETGet Shipment
- GETGet Shipment Items
- GETGet Shipment Items by Shipment ID
- GETGet Shipments
- GETList Inbound Plan Boxes
- GETList Inbound Plan Items
- GETList Inbound Plans
- GETList Inbound Shipments
- GETList Inventory (internal)
- GETList Packing Group Boxes
- GETList Packing Group Items
- GETList Packing Options
- GETList Placement Options
- GETList Transactions
- GETSearch Catalog Items
- GETSearch Listings Items
- GETSearch Product Types
- PUTSet Packing Information
- PUTUpdate Inbound Plan Name
- POSTUpdate Listings Item (Internal)
- POSTUpload Feed
Related apps
More Commerce apps on the Universal API, behind the same REST shape. Or browse all apps.