Amazon integration connects MeTEY to Amazon Seller Central using the Selling Partner API (SP-API), so orders flow in automatically and inventory flows back out.

⏱️ Set aside about two hours

Amazon's credential setup is the most involved of any platform we support. It spans Seller Central, Amazon's developer console, and AWS. Amazon's own verification can take 1-2 business days, so start well before you need to go live.

Prerequisites

Step 1: Upgrade to a Professional Seller Account

  1. Log into Amazon Seller Central
  2. Go to Settings → Account Info
  3. If you are on an Individual account, click Upgrade to Professional
  4. Complete payment setup and wait for approval (usually instant, sometimes 24 hours)

Step 2: Register as an SP-API Developer

SP-API (Selling Partner API) is how MeTEY talks to your Amazon account.

  1. In Seller Central go to Apps & Services → Develop Apps
  2. Click Add New App Client
  3. Enter these values:
    • App Name: MeTEY Integration
    • OAuth: Login with Amazon
    • Redirect URL: http://localhost
  4. Save the two credentials it gives you:
    • LWA Client ID - begins amzn1.application-oa2-client.
    • LWA Client Secret - a long alphanumeric string

💡 Store these in a password manager

You will need the Client ID and Secret again in the next step, and the Secret cannot always be retrieved later.

Step 3: Generate a Refresh Token

The refresh token lets MeTEY reach your account without you logging in each time. It does not expire unless you revoke access.

  1. Open this URL in a browser, replacing {CLIENT_ID} with your LWA Client ID:

    https://sellercentral.amazon.com/apps/authorize/consent?application_id={CLIENT_ID}&version=beta

  2. Log in if prompted and click Authorize
  3. You will be redirected to http://localhost?spapi_oauth_code=XXXXX. The page will not load - that is expected. Copy the spapi_oauth_code value from the address bar.
  4. Exchange that code for a refresh token. From a terminal:

    curl -X POST https://api.amazon.com/auth/o2/token -d "grant_type=authorization_code" -d "code=XXXXX" -d "client_id={CLIENT_ID}" -d "client_secret={CLIENT_SECRET}"

  5. From the JSON response, save the refresh_token value (it begins Atzr|)

💡 Not comfortable with the command line?

The same request can be made with a tool like Postman, or your IT provider can run it for you. Contact support@met-software.com if you would like help with this step.

Step 4: Create an AWS IAM User

Amazon requires every API request to be cryptographically signed using AWS credentials.

  1. Sign into the AWS Console using the account linked to Seller Central
  2. Go to IAM → Users → Add Users
  3. User name: metey-spapi, access type: Programmatic access (not Console access)
  4. Create a policy with this JSON, named MeTEY-SPAPI-Access:
    {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Effect": "Allow",
          "Action": "execute-api:Invoke",
          "Resource": "arn:aws:execute-api:*:*:*"
        }
      ]
    }
  5. Attach the policy to the user and finish creating it
  6. Save the Access Key ID (begins AKIA) and Secret Access Key

⚠️ The AWS secret key is shown only once

Download the CSV or copy the Secret Access Key before closing that screen. AWS will not show it again - you would have to generate a new key pair.

Step 5: Find Your Marketplace ID

This identifies which Amazon region you sell in. Find your primary marketplace under Settings → Account Info in Seller Central.

Country Marketplace ID Region
United StatesATVPDKIKX0DERna
CanadaA2EUQ1WTGCTBG2na
MexicoA1AM78C64UM0Y8na
United KingdomA1F83G8C2ARO7Peu
GermanyA1PA6795UKMFR9eu
FranceA13V1IB3VIYZZHeu
JapanA1VC38T7YXB528fe
AustraliaA39IBJ37TRP1C6fe

Step 6: Enter Credentials in MeTEY

  1. Open E-Commerce → ⚙️ Channel Configuration
  2. Add a new channel and select Amazon
  3. Fill in everything you collected:
    • Seller ID - Seller Central → Settings → Account Info
    • Marketplace ID and Region - from Step 5
    • LWA Client ID and Client Secret - from Step 2
    • LWA Refresh Token - from Step 3
    • AWS Access Key ID and Secret Access Key - from Step 4
  4. Click Validate Configuration - you should see a success message
  5. Click Save. Credentials are encrypted before being stored.

Troubleshooting

Problem What to do
Validation fails with an authentication errorMost often the refresh token was copied incompletely. It is long and begins Atzr|. Re-run Step 3 if unsure.
"Access denied" or signature errorsThe AWS IAM policy is missing or wrong. Confirm the execute-api:Invoke policy from Step 4 is attached to the user.
Orders are not importingCheck the E-Commerce Dashboard for sync errors, and confirm products are mapped to Amazon SKUs.
Listings rejected by AmazonUsually a missing or invalid UPC/EAN, or a category requiring approval. Amazon's feed processing report gives the specific reason.

Related Topics