Amazon Developer Access Confirmation

Table Of Contents

Important
Channel Listings is not enabled by default.
Training must be completed before using Channel Listings.
Please email Development for further information.
Additional charges apply if this option is enabled.

Deprecated Information
The content on this page is now deprecated.
Amazon no longer uses the MWS (Marketplace Web Service) developer authorisation process described below and now uses the Selling Partner API (SP-API) for all developer integrations with Seller Central accounts.

Introduction

In October 2016, Amazon introduced Developer Access Confirmation for MWS integrations. The purpose of this feature was to give Seller Central users greater control over which third-party developers had access to their Amazon seller account.

Although no longer used with modern Amazon integrations, the information below explains how the original process worked.

How Did Developer Access Confirmation Work?

Developer Access Confirmation required Amazon sellers to periodically review and reconfirm third-party applications and developers that had access to their account.

When access was granted to a developer:

Access remained valid for 12 months.
The seller could confirm access at any time to extend permissions for a further 12 months.
If access was not reconfirmed before expiry, the developer's access was suspended.
Suspended access could be restored through the Amazon Authorisation History section.

The intention was to ensure that only developers actively working with a seller retained access to account data.

Should Developer Access Confirmation Be Enabled?

At the time this feature was introduced, it was generally recommended because it:

Improved account security.
Reduced the risk of former integration partners retaining access indefinitely.
Allowed sellers to review authorised developers on a regular basis.

The only additional administrative requirement was the need to reconfirm authorised developers annually.

Information Available Within Seller Central

When Developer Access Confirmation was enabled, Seller Central displayed additional information about authorised developers.

Developer ID

The developer's 12-digit MWS Developer Account ID.

Developer Nickname

The nickname or company name supplied when the developer was authorised.

Authorisation Date

The date and time the developer was originally granted access.

MWS Auth Token

The credential used by the developer to interact with your Seller Central account.

Action

The available actions for the authorised developer.

These included:

Revoke – Removes a developer's access.
View Your Credentials – Displays your own authorisation credentials.

Note
Your own seller account credentials could not be revoked.

Date Last Confirmed

The date and time the developer's access was most recently confirmed.

This would normally be:

The original authorisation date if less than 12 months old.
The date Developer Access Confirmation was enabled.
The date access was most recently reconfirmed.

Access Expiration Date

The date when the developer's access would be suspended if it was not reconfirmed.

Selecting Confirm Access extended access for another 12 months from the date of confirmation.

How This Affects Khaos Control Today

Modern Amazon integrations used by Khaos Control now communicate through Amazon SP-API (Selling Partner API) rather than the legacy MWS platform.

As a result:

The developer access process described in this article is no longer used.
Current Amazon integrations follow Amazon's SP-API authorisation and security model.
Any new Amazon channel setup should follow the latest Khaos Control Amazon integration documentation.

Channel Listings System Setup
Amazon Channel Configuration
Amazon SP-API Integration
Channel Listings Overview