Skip to main content
Skip table of contents

(ASC) SP-API Customer Setup

Steps for Customers to Permit Access

The Following Steps may require login by the Amazon Account Owner/Admin.

Steps to Submit Developer Profile

  1. In the Seller Central account, navigate to ‘Apps & Services > Develop Apps’.

  2. You will be directed to the New “Solution Provider Portal” for Profile and Apps

    image-20251018-011227.png
  3. When On Enroll Page, Choose the Current Account

    image-20251018-012228.png
  4. Proceed to Start Setup & Complete Validation and confirmation in Setup

    image-20251018-011418.png
  5. Once Validated you can choose Go to Home Page

    image-20251018-011515.png
  6. Click “Proceed to Developer Profile”

  7. Fill out the Top section of the Profile with Business & Contact Information

  8. Answer the questions using the screenshots below.

    Also these new ones in above Roles

    image-20250211-175202.png
  9. After submission, you will receive a message saying the application is under review. Click to view the status. Once the application is approved, Move to the create app steps below to complete your request for Credentials.

Create an App

  1. In the Seller Central account, navigate to ‘Apps & Services > Develop Apps’. (If you’re asked to Submit Developer Profile, please see section below “Steps to Submit Developer Profile”, then return to Step 1)

    1. Click ‘+ Add new app client'.

    2. Enter App name: “In8Sync Amazon DirectConnect

    3. Select API Type “SP API”.

    4. Select APP Type “Production”

    5. Select Business entities Supported “Sellers”

    6. Select all the roles available.

    7. Under the RDT section, select “NO” and do not select the Restricted

      image-20251018-002741.png
      image-20251018-002806.png

    8. Click “Save and Exit.

  2. The apps will now be listed.

    1. On the “In8Sync Amazon DirectConnect” app, click on the “View” link in the “LWA Credentials” column.

      image-20251018-011908.png
    2. Copy the client identifier and client secret, and provide these to In8Sync.

  3. Close the LWA credentials popup, then Edit App and ensure the App Permissions are as follows:

  4. On the “In8Sync Amazon DirectConnect” app, select “Edit App” & “Authorize” from the dropdox menu.

    1. Copy the “Application ID” to provide to In8Sync.

  5. For each marketplace to be configured, click “Authorize app”.

    1. A refresh token will be visible. Copy this to provide to In8Sync (along with an indication of which marketplace it relates to).

  6. Log in to https://in8sync.com

    1. Supply the following data needed under the Credentials section using notes to supply additional information or open a support case to update us with the Credentials or to let us know the Credentials are updated

      1. Client Identifier, from Step 3

      2. Client Secret, from Step 3

      3. Application ID, from Step 4

      4. Refresh Token for each Marketplace, from Step 5

These will be used to configure access for Amazon DirectConnect.

Updating Credentials and Enabling SPI-API

**IF TODAY’S DATE IS BEFORE JULY 27th, 2022 & Version Not Confirmed 2.1.0 or Later, DO NOT PROCEED ANY FURTHER. PLEASE SEND CREDENTIALS TO IN8SYSNC.**

Come July 31st 2022, SP-API Credentials should be uploaded and SP-API Enabled in the Credentials Page. First, confirm that the Amazon DirectConnect Bundle Version is 2.1.x. To do this, navigate to Customization > SuiteBundler > Search & Install > List
Check the Version is 2.1.0 or greater.

Once you have the APP Client ID, App Client Secret, Application ID, and Refresh Token, they can be entered into the Amazon Credentials Page here:

Setup Tab > Amazon Seller Central > Access/Credentials

Edit the Correct Credentials and enter the Following

Please Check the Enable SP-API Credentials Checkbox on July 31st, if Amazon DirectConnect Bundle Version is 2.1.x, from Customization Tab > SuiteBundler > Search & Install > List
Check the Version is 2.1.0 or greater. And the APP Client ID, App Client Secret and Refresh Token are listed.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.