Add support for MWSAuthToken

[csaunders]

Amazon MWS will require the Auth Token to be used by all client apps on 15 March, 2015

---

Details:

We are always looking for ways to ensure that our Amazon Marketplace Web Service is safe and secure. As part of our ongoing efforts, Amazon MWS authorizations now include an additional parameter – the “MWSAuthToken”. The MWSAuthToken is an authorization token that we have started issuing to represent the authorization of a specific developer by a specific Amazon seller.

If you are a developer for whom multiple sellers have authorized your developer account number, including the MWSAuthToken in Amazon MWS requests is currently optional, but starting March 31, 2015 you will be required to include the MWSAuthToken in all Amazon MWS requests.

To get MWSAuthTokens for sellers already using your solutions you can call the GetAuthToken operation as more fully described here. More information about the new MWSAuthToken feature can be found here. If you have questions that have not been resolved by reading the links above, please use the Amazon MWS contact form, making sure to choose the “Solution Provider” dropdown option, here (NA) or here (EU).

If you are using an integrated registration pipeline that returns signed credentials as part of your authorization process, on September 16, 2014 the MWSAuthToken will start being sent as part of the signed credentials in the post-back URL.

If you are using an integrated registration pipeline that is returning unsigned credentials, the MWSAuthToken will not be returned until you upgrade to a new pipeline. Please contact us here (NA) or here (EU), make sure to choose the “Solution Provider” dropdown option, and we will help you begin the process to upgrade to a new pipeline.

[jamesmacaulay]

MWS AuthToken now available in MWS Client Libraries

As previously announced, Amazon Marketplace Web Service (Amazon MWS) authorizations now include an additional parameter – the “MWSAuthToken”. The MWSAuthToken represents the authorization of a specific developer by a specific Amazon seller. While including the MWSAuthToken in Amazon MWS requests is currently optional, starting March 31, 2015 you will be required to include the MWSAuthToken in all Amazon MWS requests.

The Amazon MWS client libraries have now been updated to accept the MWSAuthToken request parameter. To get authorization tokens for sellers already using your solutions you can call the GetAuthToken operation as described here. If you are not using the Amazon MWS client libraries, you can also use the Amazon MWS Scratchpad to obtain authorization tokens that you require. From the Amazon MWS Scratchpad, first select Sellers from the API Section dropdown list. Then, select GetAuthToken from the Operation dropdown list.

More information about the new MWSAuthToken feature can be found in the authorization sections of the Developer Guide here. If you have questions that have not been resolved by reading the previous links, please use the Amazon MWS contact form, making sure to choose the “Solution Provider” dropdown option, here.

Thank you for continuing to use Amazon MWS to help our sellers succeed.

Sincerely,

The Amazon MWS Team

• CA: AuthToken Guide
• UK: AuthToken Guide
• US: AuthToken Guide

[MarkHaroldson]

I have question. My company has an in house application that we use to access MWS. When we signed up for MWS we close the "I want to access my own Amazon seller account with MWS" option. When I choose this option I do not see an MWSAuthToken. Does this mean that we are excempt from this change or do I get the value from a different location.?

[Rrishibhati]

I have question, My company has a seller account on amazon mws and we want to use Integrated Registration Pipeline (IRP) or get the client's MWSAuthToken through API. is this seller getMWSAuthToken API still exist ?, i didn't see any documentation on amazon mws developer guide related to this.
It is highly appreciated if anyone have any clue on this subject.