Connect Amazon Seller Central to Rig

    Rig connects to Amazon's Selling Partner API (SP-API) to sync your orders, financials, FBA inventory, returns, reimbursements and Subscribe & Save data into your warehouse. You can either authorise Rig directly, or register your own Login with Amazon (LWA) app and give Rig its credentials.

    You need a Professional Seller plan
    SP-API is only available on Amazon's Professional selling plan. Individual plans cannot grant API access, so the connection will fail at authorisation regardless of which option below you choose.

    Two ways to connect

    The Amazon connector accepts either method. Pick one — you do not need both.

    • Option A — Connect with Amazon. The standard OAuth flow. You click a button, sign in to Seller Central and approve read access. Fastest, and right for most sellers.
    • Option B — Your own LWA app. You register a developer app in Seller Central and paste its credentials into Rig. Choose this if your security team wants the app owned by your own Amazon developer account, or if you already have a registered SP-API app.

    In Option B, Rig performs the LWA token refresh itself and pulls EU and North America together, discovering your marketplaces automatically.

    Before you start

    • You are on the Professional selling plan.
    • You sign in as the Seller Central account owner, or a user with Developer / App permissions. Standard staff users cannot authorise API access.
    • You know which regions you sell in. Amazon issues credentials per region, not per marketplace — one token covers all of Europe, another covers all of the Americas.
    • For Option B only, you will end up pasting four values into Rig: client ID, client secret, and a refresh token for each region you sell in.

    Option A: Connect with Amazon

    1. In Rig, open Connections and choose Amazon Seller Central (SP-API).
    2. Click Connect with Amazon.
    3. Sign in to Seller Central and approve the read-only access request.
    4. Optionally set Marketplace IDs to limit the sync, as a comma-separated list — for example ATVPDKIKX0DER,A2EUQ1WTGCTBG2 for US and Canada. Leave it blank to sync everything the authorisation covers.
    5. Optionally set Days of history to pull. It defaults to 90.

    That is the whole flow. If it completes without error, skip to What Rig pulls in.

    Option B: Create your own LWA app

    1. In Seller Central, open Settings → User Permissions, then Third-party developer and apps. If you have never done this, register as a developer first under Develop Apps.
    2. Open Develop Apps and click Add new app client.
    3. Name it Rig data sync, set the API type to SP-API, and choose the read-only roles that match the data you want. Selling Partner Insights, Inventory and Order Management, and Finance and Accounting cover the standard set.
    4. Save the app. Amazon shows a client ID beginning amzn1.application-oa2-client. and a client secret beginning amzn1.oa2-cs.v1.. Copy both now.

    Restricted roles need extra approval
    Roles that expose buyer personal data (names, addresses) require Amazon to approve your use case separately. You can connect and sync without them — you will simply not receive the PII-bearing fields until Amazon approves.

    Authorise the app per region

    A refresh token is scoped to one region. If you sell in both Europe and North America you must run this twice, once signed in to each regional Seller Central account, and you will end up with two different tokens.

    1. In Develop Apps, find your app and open Authorise from its actions menu.
    2. Click Authorise app and approve the request.
    3. Amazon returns a refresh token beginning Atzr|. Copy it immediately — Amazon shows it once.
    4. Repeat for your other region if you sell in one, signing in to that region's Seller Central first.

    Connect it in Rig

    1. Open Connections and choose Amazon Seller Central (SP-API).
    2. Paste the client ID into LWA client ID (direct mode).
    3. Paste the client secret into LWA client secret (direct mode).
    4. Paste each refresh token into the field for its region: EU refresh token (direct mode) for European marketplaces, US refresh token (direct mode) for the Americas.
    5. Click Continue.

    Fill in a complete set
    Direct mode needs the client ID, the client secret, and at least one region refresh token. A partial set is rejected, and the error names which combination is missing. Leave Marketplace IDs blank in this mode — Rig discovers your marketplaces from the authorisation itself.

    What Rig pulls in

    Amazon lands in its own amazon_sp_api schema in your warehouse. The first sync is slow by design — Amazon meters SP-API tightly, and a deep backfill is hours of report requests. Rig checkpoints as it goes, so an interrupted first load resumes rather than restarting.

    • Orders and order items — order headers and per-item detail
    • Transactions — financial events: sales, refunds, fees and adjustments
    • FBA inventory and aged inventory by ASIN and marketplace
    • Listings by seller SKU, and the marketplaces you sell in
    • Returns — FBA customer returns per unit with reason and disposition, plus seller-fulfilled return requests
    • Reimbursements — itemised FBA reimbursements with ASIN, quantity, reason and case ID
    • Storage fees — monthly per-ASIN storage charges, and long-term storage surcharges
    • Subscribe & Save — account and per-offer metrics, plus current offer configuration
    • Search Query Performance — the weekly search-term funnel per ASIN

    Two streams are not on by default. Sales & Traffic (daily sessions, page views and buy-box percentage per child ASIN) is opt-in because it costs one report per day and consumes a lot of report quota on a long backfill — ask Rig to enable it if you want it. Amazon-fulfilled shipments is available on the OAuth path only, because it carries buyer data and needs a restricted-data token.

    Amazon Ads is separate

    Advertising spend and performance do not come through SP-API. They are a second connector, Amazon Ads, with its own authorisation — connecting Seller Central does not bring ad data with it, and vice versa.

    Amazon Ads covers Sponsored Products, Sponsored Brands and Sponsored Display at daily grain, including per-ASIN advertised-product reports for Products and Display. Sponsored Brands has no per-ASIN cost anywhere in Amazon's API, so its ASIN-level stream reports purchased products rather than spend.

    Troubleshooting

    • The connector rejects your credentials as incomplete: direct mode needs the client ID, the client secret and at least one region refresh token. The message names a complete combination — fill in whichever part is missing.
    • You cannot see Develop Apps: you are signed in as a user without developer permissions, or the account is on an Individual rather than Professional plan.
    • The refresh token is not shown again: Amazon displays it once at authorisation. Re-authorise the app to generate a fresh one.
    • European orders are missing: a refresh token only covers its own region. Add the EU token as well as the US one.
    • The first sync is still running hours later: expected on a deep backfill. Amazon rate-limits several endpoints to roughly one request per minute, and Rig waits rather than being throttled off. Progress is checkpointed, so it resumes if interrupted.
    • Buyer names and addresses are blank: those fields need Amazon-approved restricted roles on your app. Everything else syncs without them.
    • No advertising data: connect the separate Amazon Ads source.
    • You rotated the client secret: update it in Rig before the next sync, or the token refresh will start failing.

    Amazon references

    Was this guide helpful?