DatriseAI-first ETL

Source connector

Amazon Seller Partner connector

Amazon Seller Partner integration for databases, warehouses and BI tools

Seller data for Amazon marketplace operations. Datrise captures Amazon Seller Partner entities such as orders, order items, listings, inventory, settlements and FBA shipments, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Amazon Selling Partner API (SP-API) authenticates with OAuth 2.0, incremental runs key on LastUpdatedAfter / CreatedAfter (Orders), and Amazon Seller Partner caps calls at A per-operation token bucket of rate plus burst, scoped to the selling-partner and application pair — getOrders is 0.0167 requests per second with a burst of 20, getOrder and getOrderItems 0.5 per second with a burst of 30; an empty bucket returns HTTP 429.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `amazon_seller_partner_orders`) with a schema derived from the Amazon Seller Partner API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Amazon Seller Partner pipeline page, and join the waitlist to get the Amazon Seller Partner connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Amazon Seller Partner data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

ObjectLanding tableSync mode
ordersamazon_seller_partner_ordersUpsert by primary key, incremental on updated-at
order itemsamazon_seller_partner_order_itemsUpsert by primary key, incremental on updated-at
listingsamazon_seller_partner_listingsUpsert by primary key, incremental on updated-at
inventoryamazon_seller_partner_inventoryUpsert by primary key, incremental on updated-at
settlementsamazon_seller_partner_settlementsUpsert by primary key, incremental on updated-at
FBA shipmentsamazon_seller_partner_fba_shipmentsAppend-only, incremental by timestamp

Amazon Seller Partner API: setup facts for the connector

Verified against the vendor documentation on 2026-09-03. Unknown values are left blank rather than guessed.

APIAmazon Selling Partner API (SP-API)
AuthenticationOAuth 2.0 — Login with Amazon: a refresh token is exchanged at `https://api.amazon.com/auth/o2/token` for an access token sent in the `x-amz-access-token` header.
Paginationtoken — `nextToken` from the response is passed back as the page token on the following call; the key is absent from the pagination object on the last page.
Rate limitA per-operation token bucket of rate plus burst, scoped to the selling-partner and application pair — getOrders is 0.0167 requests per second with a burst of 20, getOrder and getOrderItems 0.5 per second with a burst of 30; an empty bucket returns HTTP 429
Incremental cursorLastUpdatedAfter / CreatedAfter (Orders) — History is bounded by the marketplace: most expose the last two years, while JP, AU and SG go back to 2016.
WebhooksYes — Notifications API (delivered to Amazon SQS or EventBridge, not to an HTTP endpoint)
Bulk exportYes — Reports API v2021-06-30 (request a report, poll for it, then download the report document)
Deletes detectableNot published

Official API reference

What bites when replicating Amazon Seller Partner

  • `getOrders` is rate limited at 0.0167 requests per second — one call a minute — with a burst of 20, so a backfill drains the burst in seconds and then crawls; plan order syncs around the Reports API instead of paging orders.
  • The Login with Amazon access token expires 3,600 seconds after it is issued, so any export longer than an hour has to refresh mid-run rather than authenticate once at the start.
  • `x-amzn-RateLimit-Limit` is returned on a best-effort basis only and Amazon explicitly says not to depend on it being present, so a client cannot reliably discover its own remaining budget.
  • Limits are scoped per selling-partner and application pair, so adding threads for a single seller buys nothing while the same application scales naturally across many sellers.

Compare this against every other documented API

Popular destinations for Amazon Seller Partner

Choose a destination below to open the ready pipeline page.

  • A
    Airtable

    Relational spreadsheet destination for ops and go-to-market teams.

    View pipeline
  • A
    Amazon Athena

    Serverless SQL over S3 data lake tables.

    View pipeline
  • A
    Amazon DynamoDB

    Serverless key-value and document store on AWS.

    View pipeline
  • A
    Amazon QuickSight

    AWS serverless BI with SPICE and embedded analytics.

    View pipeline
  • A
    Amazon Redshift

    AWS petabyte-scale warehouse with Spectrum.

    View pipeline
  • A
    Amazon S3 Data Lake

    Object storage landing zone for parquet and snapshots.

    View pipeline
  • A
    Apache Superset

    Open-source BI for SQL exploration, charts, and dashboard publishing.

    View pipeline
  • A
    Azure Data Lake Storage

    ADLS Gen2 object storage for analytics workloads.

    View pipeline
  • A
    Azure Synapse

    Microsoft analytics workspace with SQL pools.

    View pipeline

Amazon Seller Partner connector FAQ

What Amazon Seller Partner data does the connector extract?
6 objects: orders, order items, listings, inventory, settlements and FBA shipments. Each lands in its own table with types preserved; history-style objects (1: FBA shipments) load as append-only streams.
Is the Amazon Seller Partner integration incremental?
Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Amazon Seller Partner data?
Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Amazon Seller Partner → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Amazon Seller Partner pipeline with guided onboarding

Join the waitlist to get priority access for Amazon Seller Partner integrations with guided setup, schema-aware mapping, and production-grade incremental sync.