youtube video
Automate your Amazon orders data with SP API, Google Sheets and Python (new method 2021)Guide: Using Amazon Seller Central with Databox
Currently, there is not a direct Databox + Amazon Seller Central integration available, but there are alternative ways to sync your Amazon Seller Central data with Databox.
These alternatives utilize third-party integrations such as Zapier, or the Databox API.
Pro Tip: If you don't have the time or resources to set this up yourself, check out amazon seller central api documentation services where we can build the custom integration for you. For additional information, feel free to connect with our team via chat or email us at [email protected]
HOW TO
Zapier is a trigger-based app, meaning you can have certain events (such as a new card being added) trigger certain actions (updating the relevant data and syncing with Databox) using Zaps. Because triggers initiate data syncs, historical data will not be available for metrics that are synced using Zapier.
Learn more about the Zapier + Databox third-party integration here.
Whenever possible, it’s recommended that you use a Zap Template. This will save you time and will streamline the process of syncing Amazon Seller Central data with Databox using Zapier.
You can also create Zaps from scratch if a Zap Template isn’t available.
IN THIS SECTION
Zap Templates available for Amazon Seller Central Metrics
View the full list of prepared Zaps here.
Creating Zaps from scratch for Amazon Seller Central Metrics
The following Amazon Seller Central Metrics can also be synced with Databox by creating a Zap from scratch:
- New Order
(triggered when a new order is received)
Learn how to create Zaps from scratch here.
If you’re comfortable using scripting languages or you have developer resources available, you can build your own custom integration and push Amazon Seller Central data via the Databox API.
For more information, check out the Databox developer portal or Amazon Seller Central’s API documentation.
This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether expressed or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.
The software included with this paper is licensed under the Apache License, version (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at ukimmigrationattorneynewjersey.us or in the accompanying "license" file. This code is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either expressed or implied. See the License for specific language governing permissions and limitations.
Amazon MWS component
An integration component which helps Amazon sellers to programmatically exchange data on listing, orders and more using the Amazon MWS API.
Description
Data integration with Amazon enables high levels of selling automation, which can help sellers grow their business. Please visit Amazon Marketplace Web Service (Amazon MWS) Documentation for more information.
How works
This Amazon MWS component can be used to connect your Amazon Seller account with other services.
If you intend to use the Amazon MWS API you must have an Amazon MWS-eligible seller account and you must register to use Amazon MWS. Please visit Registering to use Amazon MWS page to choose your country applicable developer’s page.
Technical Notes
The technical notes page gives some technical details about AWS-S3 component like changelog and completeness matrix.
Credentials
Here are the credentials necessary to authenticate with the Amazon MWS:
Please refer to the document how to provide us access to your Amazon seller account for details.
Requirements
Environment variables
| Name | Mandatory | Description | Values |
|---|---|---|---|
| RESPONSE_CHECK_DELAY | false | Determines delay for requesting submit feed result (in milliseconds) | Default: |
Triggers
Get New And Updated Orders
This trigger polls for the orders in your seller account based on the selected Order Status. All orders which are retrieved according to specified parameters are stored in component memory and will be emited in one message after the last order is retrieved.
User is able to use following input fields to configure the step:
Order Status
Is the only required field, it cibo matto shirt the following available values:
- - all the pending orders
- - all the shipped orders
- - all unshipped orders
- - partially shipped orders
- - canceled orders
- - not fulfillable orders
- - all orders with statusonly available in the Japan store
- - all orders with statusonly specific to Chinese store
Maximum Orders per Page
Number of maximum orders per request page, find more info about in Amazon MWS documentation.
Please Note:
- Sample would be retrieved according to specified value.
- Trigger would retrieve all requested objects during runtime (each request to Amazon MWS would be sent according to specified value).
Start Time
Starting from this time trigger retrieves orders from Amazon MWS ( in Amazon MWS).
Use format for input data, it will be transformed under hood to Amazon MWS date format
End Time
Before this time trigger retrieves orders from Amazon MWS ( in Amazon MWS).
Use format for input data, it will be transformed under hood to Amazon MWS date format
Please Note:
- Trigger debug task (sample retrieve) makes ONLY one API request for throttling safe purposes. Component will throw an exception, if Amazon MWS returns a response with code caused by throttling. In any other cases trigger will poll Amazon MWS API till correct response any 30 seconds (by default).
- Next flow steps after trigger may require additional memory in case when big number of orders emited by the trigger, or they could fail with error .
- We recommend to use real-time flow in cases when more than ~ orders are expected to be emitted by the trigger.
Limitations
- Trigger throws an error in case when no more orders found for specified time range in case when has been specified :
Actions
Get Order
Takes an array of Amazon Order IDs as an input and returns an array of orders for each order.
Input sample:
List Order Items
This action would fetch and give the Order Items on output. This action only needs the Amazon on input:
The output object contains an array of values listing the of the given the Amazon. The output has the following structure:
Submit Product
This action can be configured using two parameters: and .
Operation defines the action type you wish to do:
- - upsert the records
- - delete the records
- - update only one part of the records
Category defines the specific category of the product and it can have the following types:
Auto Accessories, Amazon seller central api documentation, Books, Camera & Photo, Cell Phones & Accessories (Wireless), Clothing Accessories & Luggage, Computers, Consumer Electronics, Entertainment Collectibles, Grocery & Gourmet Food, Health, Home Improvement, Industrial & Scientific: Lab & Scientific Supplies, Industrial & Scientific: Power Transmission, Industrial & Scientific: Raw Materials, Jewelry, Lighting, Miscellaneous, Musical Instruments, Music, Office, Outdoors, Pet Supplies, Shoes Handbags and Sunglasses, Software and Video Games, Sports, Sports Collectibles, Tires & Wheels, Tools, Toys & Games
Submit Product (Category from payload)
This action can be configured to submit the product information based on dynamically selectable products from the payload.
Action perform the following operations:
- - upsert the records
- - delete the records
- - update only one part of the records
Update Order
This action is for updating ‘Order’ entities using submitting feed mechanism. The action includes mechanism for polling submit feed result.
Input metadata
Action requires an array with items description as input data
Update Item
This action is for updating ‘Item’ entities en using submitting feed mechanism. The action includes mechanism for polling submit feed result.
Input metadata
Action requires an array with items description as input data
Submit Inventory
This action can be configured to submit the inventory based on the dynamically selectable values of the Inventory catalogue:
Change Product Image
This action can be configured to change the product image based on the dynamically selectable values of the Inventory catalogue:
Change Product Price
This action can be configured to change the product price based on the dynamically selectable values of the Inventory catalogue:
Establish Product Relationships
This action can be configured to establish the product relationships based on the dynamically selectable values of the Inventory catalogue:
Get Feed Submission Status
This action is for submitting the status to the feed. It accepts the and the as a value on input and outputs the values of the same parameters:
Get Feed Submission Result
This action is for submitting the result to the feed. It accepts the and the as a value on input and outputs the values of the same parameters:
Additional Information
Locating your Developer Keys
To locate your developer keys at Amazon MWS follow these steps.
- Login to Amazon Seller Central dedicated to your country. To find which one to use simply visit Amazon Services and navigate your way through your Seller Central page.
- After login navigate to your Settings > User Permissions page.
- When in the User Permissions page scroll-down to find the section called Amazon MWS Developer Permissions and check the Current Authorizations. Copy the from here for later use when you would need to create the necessary credentials to use inside the platform Security Credentials part.
- Click the link called in the column entitled Action Taken. If you have several Developer IDs in your account then make sure to click on the link in the row where the related Developer ID is located. When clicked a window will pop-up with 3 values: AWS Access Key ID, Secret Key and Status. Make sure that the Status = Enabled.
- Copy AWS Access Key ID, this is your from the credentials.
- Click to Show the Secret Key value and copy it. This is the from the credentials.
Connecting the Amazon Seller account
To retrieve your and the values you need to follow the steps below:
- Visit Amazon Marketplace Web Service (Amazon MWS) and click on Sign up for MWS or login if you have done this already previously.
- You will be presented with this screen where you would need to select I want to give a developer access to my Amazon seller account with MWS option.
- Fill in the details for the Developer’s Name and the Developer Account Number. The last one is your. Check the (3) of the Locating your Developer Keys for information. Click Next to go forward.
- Agree to the therms and conditions on the next page presented and click Next to finally create credentials.
- A page will be presented where you can see the details of your credentials. Please copy the and the values before navigating away. This page is shown once.
Join the world's most advanced pre-accounting system.
Overview
This tutorial is how to sync your Amazon Seller Central sales data to Greenback. Greenback supports North America (U.S., Canada, and Mexico marketplaces), Europe (France, Germany, Italy, Spain, Sweden, Poland, Netherlands, and the United Kingdom marketplaces), and Australia. You will need to set up each region that you sell in for Greenback to capture all of your sales and sales-related fees. Make sure that you already have a Greenback account (paid subscription) and an Amazon Seller Central account (Pro Seller monthly subscription). You must be a Super-Admin (store owner) to Authorize a Developer (Greenback) to allow access to your sales data. Then you will create your merchant (seller) ID & auth token and share them with Greenback. Once added, Greenback allows collaboration and multi-user access. After completing steps for each marketplace/region you sell in, we highly recommend checking out Best Accounting Practices for Amazon Seller + QuickBooks or Best Accounting Practices for Amazon Seller + Xero.
Pro-Tip: Instructions are intended for Amazon Seller Central Marketplaces and Amazon Handmade with Pro Seller subscription plans.
Amazon Seller Central (North America)
Amazon leverages their North America platform for both North America (Canada, Mexico, United States) and Brazil regions. Greenback's same "Developer ID" is used for either region to authorize our application. The process is identical to authorize our application in both regions. For the Amazon Seller North America region, you can authorize our application in any one of your Canada, Mexico, or the United States seller accounts and Greenback will be able to sync data from all them. For Brazil, you'll need to authorize our application using the same steps below.
From your Amazon Seller Central dashboard:
- Go to App Store, then click on "Manage Your Apps" from the menu. If you can't locate it, you can use the following links:
North America (any one of the following)
Canada: ukimmigrationattorneynewjersey.us
Mexico: ukimmigrationattorneynewjersey.us
United States: ukimmigrationattorneynewjersey.us
Additional Regions (each requires an authorization)
Brazil: ukimmigrationattorneynewjersey.us
- Next, click on the “Authorize New Developer”
- On the Authorize New Developer screen, copy/paste the developer name Greenback and the developer id into the fields and click Next.
- Find the Amazon Seller ID (at the top) and MWS Auth Token (at the bottom) that you created. Keep the tab open so that you can copy/paste them next.
- Setup your account on Greenback.
For North America (Canada, Mexico, or United States): ukimmigrationattorneynewjersey.us
For Brazil: ukimmigrationattorneynewjersey.us
In the connect box, copy/paste your seller ID and auth token into their respective fields and click Connect.
Amazon Seller Central (Europe)
Amazon leverages their Europe platform for the Europe (United Kingdom, France, German, Spain, Italy, Poland, and Netherlands), India, Turkey, Egypt, and United Arab Emirates regions. Greenback's same "Developer ID" is used for each region to authorize our application. The process is identical to authorize any of the regions. For the Amazon Seller Europe region, you can authorize our application in any one of your United Kingdom, France, German, Spain, Italy, Poland, or Netherlands seller accounts and Greenback will be able to sync data from all them. For the other regions, you'll need to authorize our application in each one following the steps below.
From your Amazon Seller Central dashboard:
- Go to App Store, then click on "Manage Your Apps" from the menu. If you can't locate it, you can use the following links:
Europe (any one of the following)
United Kingdom: ukimmigrationattorneynewjersey.us
Italy: ukimmigrationattorneynewjersey.us
France: ukimmigrationattorneynewjersey.us
Germany: ukimmigrationattorneynewjersey.us
Netherlands: ukimmigrationattorneynewjersey.us
Poland: ukimmigrationattorneynewjersey.us
Spain: ukimmigrationattorneynewjersey.us
Additional Regions (each requires an authorization)
Egypt: ukimmigrationattorneynewjersey.us
India: ukimmigrationattorneynewjersey.us
Saudi Arabia: ukimmigrationattorneynewjersey.us
Turkey: ukimmigrationattorneynewjersey.us
United Arab Emirates: ukimmigrationattorneynewjersey.us
- Next, click on the “Authorize New Developer”
- On the Authorize New Developer screen, copy/paste the developer name Greenback and the developer id into the fields and click Next.
- Find the Amazon Seller ID (at the top) and MWS Auth Token (at the bottom) that you created. Keep the tab open so that you can copy/paste them next.
- Setup your account on Greenback.
For Europe (United Kingdom, France, German, Spain, Italy, Poland, and Netherlands): ukimmigrationattorneynewjersey.us
For Egypt: ukimmigrationattorneynewjersey.us
For India: ukimmigrationattorneynewjersey.us
For Saudi Arabia: ukimmigrationattorneynewjersey.us
For Turkey: ukimmigrationattorneynewjersey.us
For United Arab Emirates: ukimmigrationattorneynewjersey.us
In the connect box, copy/paste your seller ID and auth token into their respective fields and click Connect.
Amazon Seller Central (Australia)
Amazon leverages their Far East/Australia platform for the Australia, Japan, and Singapore regions. Greenback's same "Developer ID" is used for each region to authorize our application. The process is identical to authorize any of the regions. You'll need to authorize our application in each region following the steps below.
From your Amazon Seller Central dashboard:
- Go to App Store, then click on "Manage Your Apps" from the menu. If you can't locate it, you can use the following links:
Australia: ukimmigrationattorneynewjersey.us
Japan: ukimmigrationattorneynewjersey.us
Singapore: ukimmigrationattorneynewjersey.us
- Next, click on the “Authorize New Developer”
- On the Authorize New Developer screen, copy/paste the developer name Greenback and the developer id into the fields and click Next.
- Find the Amazon Seller ID (at the top) and MWS Auth Token (at the bottom) that you created. Keep the tab open so that you can copy/paste them next.
- Setup your account on Greenback.
For Australia: ukimmigrationattorneynewjersey.us
For Japan: ukimmigrationattorneynewjersey.us
For Singapore: ukimmigrationattorneynewjersey.us
In the connect box, copy/paste your seller ID and auth token into their respective fields and click Connect.
How to Unarchive Amazon Statements
If you need Amazon Seller Central amazon seller central api documentation containing transactions older than 90 days, you need to request them from Amazon. By default, Amazon archives statements after 90 days.
Follow these steps to amazon seller central api documentation your Amazon Seller Central statements:
- Login to your Amazon Seller account
- Click Reports > Payments
- Click All Statements
- Locate the desired time frame(s) then click Request Report
Once unarchived, Greenback is able to access the transactional data. Amazon will archive them again in 90 days, but the data will now remain in Greenback.
While they are accessible, you are essentially sharing them with Greenback just like they were new transactions being auto-fetched for you. There's no need to worry about duplicates; Greenback always searches for matching transactions and prevents them.
How to Extract Your Amazon Seller Central Data
If you’re selling on Amazon, you already know that getting all the Amazon Seller Central data you need for a complete picture of your business is challenging (and may seem downright impossible), especially if you’re a large brand with international distribution. We’ve been there.
To make the seemingly impossible possible, we wanted to create a guide that shows how to get your Amazon seller data, as well as the various quirks that you need to be aware of within Amazon in order to develop a reliable data reporting system.
The Big Three Amazon Data Sources:
Data Source One: Your Amazon Seller Central Dashboard
When you use it: The Amazon Seller Central Dashboard and its graphs/charts give you a high-level view of your store’s performance and inventory status. If you’re trying to get a quick idea of high-level figures, this is the place to start.
How you use it: The Amazon Seller Central Dashboard is accessible simply by logging into your Seller Central account; it is the first element of the UI that you see.
Why you use it: This is where the non-data-analytics folks on the team will start their journey to get a snapshot of performance and manage the account. But all the analytics pros out there know you’re barely scratching the surface here.
Data Source Two: Exported Data Reports
When you use them: You can download reports through Amazon Seller Central to get detailed data on Orders, Inventory, Traffic, and Returns.
How you use them: Export your brand’s data reports through Amazon Seller Central (see two data report examples below for navigation information).
Why you use them: When you want a granular view into all elements of your Amazon data, exported data reports are most sellers’ best bet. Not only can you view and analyze the major categories, but you can also get more specific data reports, such as Unshipped Orders, Sales, and Traffic by ASIN.
Data Report Ex. #1: New Orders Report
Navigation: amazon seller central api documentation Central > Sidebar/Top Menu > Orders > Orders Reports
Data Report Ex. #2: All Orders Report:
Navigation: Amazon Seller Central > Sidebar/Top Menu > Reports > Fulfillment > Sales > All Orders
Data Source Three: Amazon API (via Amazon Marketplace Web Services aka MWS)
A quick note: Amazon’s API (also called Amazon Seller Central API, Amazon Seller API, Amazon Merchant API, among other names) will be updated later inand MWS will be replaced with the Selling Partner API (SP-API), but calling the API through MWS will remain crucial until then.
When you use it: You use Amazon’s API through Amazon MWS to get data, such as pending order data, that you cannot get through exported data reports (more on this in later sections) and to schedule Seller Central report requests.
How you use it: You access the API through Amazon MWS. In the API section, you can choose the API section (e.g., Orders) and Operation (e.g., ListOrders), the date range for the data you want to see, as well as other optional parameters, and then call custom reports based on your needs. Once you extract the data in CSV form (see Amazon API Subquirk below), you can send it to Excel, Google Spreadsheets, or your preferred data storage/data warehouse system.
Why you use it: For brands looking to get a complete Amazon data picture, it is necessary to use both Seller Central data reports (whether through manual download, i.e., as in Data Source 2 or by scheduling them through the API) and using the Real-Time API, which we’ll get into next.
Real-Time APIs vs. Reports API
At Daasity, we break down Amazon’s APIs into two categories: Real-Time APIs (boxed in red) and the Amazon Reports API (boxed in green).
The Real-Time APIs (Easy Ship, Orders, and others) allow you to build applications (e.g., paying for shipping costs through API or tracking sales trends by SKU) and query the data categories for specific information such as an individual order. The Real-Time APIs are necessary for brands looking to build data picture because they supply information that the Seller Central data reports do not (see Quirk #1 below).
The Reports API allows you to download the same data reports as you would through the Seller Central Dashboard. However, the Reports API also allows you to schedule downloads of data reports.
Now, let’s head to where working to get your Amazon seller data getsmore interesting.
Demonstrating Amazon’s Data Quirks with Order Data
The key to building a single source of reliable Amazon data requires a deeper understanding of the differences between data reports from Seller Central and data from the API (and the quirks of each).
To illustrate this, let’s focus on Amazon order data.
Quirk #1: API + Report = Complete Order Status Data
To get us started, here’s Daasity CEO, Dan LeBlanc, to explain some differences between Amazon Data Reports and Amazon’s (Real-Time) API (data sources #2 and #3 above):
Here’s Dan’s graphic:
To get a complete picture of Amazon order status data, the API and report must be integrated: pending order details (costs and quantities) can only be retrieved from a downloaded report. The same details around canceled and refunded orders can only be retrieved from the API.
However, this leads us to an…
Amazon API "Subquirk"
Amazon’s Real-Time API does not return data requests in JSON. Instead, it returns data in CSV form. This is important to be aware of, especially for larger brands with much larger data sets. Depending on the resources you have available, you may find it necessary to add a step of data processing and convert the CSV files into JSON.
Quirk #2: Amazon Seller Central Data Reports Are Not Up-to-Date
Although the high-level data in your Amazon Seller Central Dashboard is up-to-date, all data in the reports that you download from Seller Central run on hour delays.
So, if you download a data report from Amazon Seller Central on Wednesday morning, you’re looking at data that is updated through Sunday. This means that Wednesday is amazon seller central api documentation first day that you can analyze last week’s data.
Quirk #3: Amazon API Limitations
Once you get past the hurdles of delayed data reports and normalizing data in Excel, Amazon has another quirk waiting for you if you’re too eager and frequent with your API calls.
Amazon has a rate limit on API calls, which means that you can only hit the API so many times before your access is temporarily removed and you’re put in the penalty box.
The reason this becomes such an issue for merchants trying to get their Amazon data, especially international ones, is because all API calls (Real-Time and Reports in addition to reports on data from different regions) count toward that rate limit.
So, you may need to get every report from every region you sell in every day, but if you have to redo some data analyses a few times, you may hit the limit from too many requests. For even more potential frustration, if you have requested API calls from the Reports API, and they have not loaded yet, those too will get amazon seller central api documentation out. Then, you have to start from scratch in your data requests.
Bonus Section: A Couple Amazon Settlement Report Quirks
In our article about combining Amazon and Shopify data, we mentioned an extra-challenging Amazon data report, the settlement report, which is a big ol’ honkin’ document that contains the full breakdown of fees associated with your Amazon Seller Account, most importantly what you are going to get paid. Like everything else with Amazon’s data reports, there are quirks to be aware of with the settlement report.
Quirk #1: You can’t schedule or request this fella. Amazon decides when you receive it.
Quirk #2: The settlement report is broken down by region. This means that in addition to the fundamental analytical challenges the settlement report poses due to complexity, you don’t have the ability to zoom into individual marketplaces to get the granularity that you might hope for.
Going Quirkless: Let Daasity Handle Your Amazon Data!
Not to put too fine a point on this, butextracting your Amazon Seller Central data and creating a single source of truth around that data is a nightmare. It takes experienced analysts hours, every day, to correctly download and make sense of all the Amazon data reports (this doesn’t even include running daily and then as-needed queries on the reports).
As a result, it probably sounds pretty darn good to have everything we just discussed completely automated and beautifully presented for you to analyze. Don’t do it all by yourself; let Daasity do all the heavy lifting.
Build a single source of truth around your Amazon data today. Check us out here and learn more.
Amazon Vendor API - Content and Access
Vendors at Amazon have not been spoiled when it comes to the technical connection of their own systems to those of Amazon. Until now, Amazon only offered an outdated interface based on the EDI standard. For some time now, Amazon has also been providing a modern REST interface. We explain what this can do and how you can get access to it.
Scope of the Amazon Selling Partner API
Under the English designation Amazon Selling Partner API Amazon now also offers its suppliers (vendors) a RESTful interface. This covers the areas "retail" and "direct supply".
As of June the API was not yet on the same level as the EDI interface. Amazon's own overview shows which processes are currently supported in the Retail area:
| Area | Process | Vendor Central | EDI Schn. | REST API |
|---|---|---|---|---|
| Stock Management | Mark item as temporarily unavailable | ✓ | ✓ | |
| Mark item as permanently unavailable | ✓ | |||
| Share stock | ✓ | |||
| Cost of Goods | EK Update Prices | ✓ | ✓ | |
| View EK prices | ✓ | |||
| Orders | Read out new orders | ✓ | ✓ | ✓ |
| Changes / Read out cancellations | ✓ | June | ||
| Read status | ✓ | June | ||
| Send Order Confirmation | ✓ | ✓ | ✓ | |
| Read order confirmation status | ✓ | ✓ | ||
| Delivery | Create Delivery Announcement (ASN) | ✓ | ✓ | ✓ |
| Update Delivery Bremer online banking login out delivery announcement status | ✓ | ✓ | ||
| Confirm delivery | ✓ | |||
| Invoices and Credits | Create and Update | ✓ | ✓ | ✓ |
| Check Invoice Status | ✓ | |||
| View Invoice | ✓ | |||
| Controlling | Reports on sales data | ✓ | ✓ | |
| Reports Sales Analysis | ✓ | |||
| Payment Advice | Read out Payment Advice | ✓ | ✓ |
Both interfaces can be used simultaneously. The new REST API is therefore to be regarded as a supplement to the EDI interface. In the long run, according to Amazon, the REST API would probably get more features than the EDI interface. Therefore, it can be assumed that the EDI interface will not be further developed in the long run.
Request Vendor API access
Set up AWS User
To access the interface you need an account in Amazon's Cloud - AWS. There you create your own user with programmatic access and assign this user the necessary rights for access to the "Selling Partner API" via a so-called "IAM Policy".
After completion you will receive an AWS Access Key with the corresponding Secret Key. Download this key and save it securely. Also note the so-called "ARN-ID", which identifies the user uniquely.
Request access
To get access to the API, you must create a case of type API Integration in Vendor Central. Enter "Register my application" as the reference and the following information:
- Name of the application
- ARN of the AWS user who should get access
- Dimension "Retail" or "Direct Fulfillment"
Amazon will now check your registration and hopefully activate it.
Get access data
As soon as the activation is done, log back into Vendor Central and go to the following page:
There you will find an overview of the applications you have registered with the corresponding Login with Amazon (LWA) access data.
The authorization at the API works with the so-called OAuth2 procedure, i.e. you need a refresh token to request data from the API. You get this refresh token on the same page by clicking "Edit" next to the application and requesting the code there.
Amazon Vendor API Sandbox
Amazon also provides developers with a sandbox in which they can first test their application. Thus the sandbox is available for European vendors under e.g. 'ukimmigrationattorneynewjersey.us' in the AWS region 'ewest-1'.
Available methods
In version 1 the API provides the following methods:
| Area | Endpoint | Purpose |
|---|---|---|
| Orders API | /vendor/orders/v1/ | Read out and confirm purchase orders |
| Shipments API | /vendor/shipping/v1/ | Create Shipping Pre-Message |
| Payments API | /vendor/payments/v1/ | Send Invoices |
| Transactions API | /vendor/transactions/v1/ | Check API transactions |
Future
Amazon states that it will continue to expand the API. Thus Amazon writes:
Inwe will be offering APIs for Product Listing, Item Cost Updates, PO Changes & Cancelations. The API roadmap for will be published in April
Especially the API for modifying Amazon Product listings should become interesting for vendors.
Vendors can find further information under: ukimmigrationattorneynewjersey.us(opens new window)
Note about links in this article
Please note that the links in this article can only be opened with a Vendor Central Account.
