Skip to main content

Amazon Seller Partner

This page contains the setup guide and reference information for Amazon Seller Partner (SP).

Prerequisites​

  • Amazon Seller Central account
  • At least one Amazon SP-API marketplace that the seller account participates in

Setup guide​

  1. Select Amazon Seller Partner from the Source list.

  2. Enter a Source Name.

  3. Select Authorization Marketplace for the Seller Central marketplace used to start OAuth authorization.

  4. Authenticate your Amazon Seller Central account.

  5. After OAuth completes, use Available Amazon Marketplaces to load the marketplaces returned by the SP-API Sellers getMarketplaceParticipations operation for this authorized seller account, then select the marketplace IDs to sync. If Japan or another cross-region marketplace is not returned, re-authorize from the corresponding Seller Central region or verify that the seller account participates there.

    Available Amazon Marketplaces can return marketplace IDs across these selling regions when Amazon returns them for the authorized account:

    • North America: United States (US), Canada (CA), Mexico (MX), Brazil (BR)
    • Europe: Belgium (BE), Germany (DE), Spain (ES), France (FR), Ireland (IE), Italy (IT), United Kingdom (UK), Netherlands (NL), Sweden (SE), Poland (PL), Turkey (TR), South Africa (ZA)
    • Middle East: United Arab Emirates (AE), Saudi Arabia (SA), Egypt (EG)
    • Asia Pacific: Japan (JP), India (IN), Australia (AU), Singapore (SG)

  6. Max wait time for reports (in seconds) is the report-generation wait budget. The connector enforces a safe minimum of 1800 seconds even for existing configurations with a lower value; higher configured values are honored.

    Large text and JSON report documents are downloaded to a bounded temporary file before parsing. Interrupted document transfers are retried up to three times, and no records are emitted until a complete download is available.

    On the native execution path, text reports and Brand Analytics JSON arrays are instead downloaded, decompressed, and parsed incrementally without storing the whole document in memory or temporary storage. An interrupted transfer fails the invocation without a successful checkpoint; it is not restarted midway through the same invocation. Report-generation timeouts are reported as failures, not successful empty reports. Native report waiting has a minimum of 1800 seconds and a maximum of 7200 seconds. Stream selection does not require customer worker or routing permissions.

  7. Period In Days will be used for stream slicing for initial full_refresh sync when no updated state is present for reports that support sliced incremental sync. It does not control GET_EPR_MONTHLY_REPORTS, which uses the connection-level Acquisition Method cycle.

  8. Acquisition Method is configured on the connection, not on the reusable source. Select Cycle Acquisition with Cycle = Last completed calendar month for report streams that use a fixed natural-month acquisition window.

  9. End Date (optional) - any data after this date will not be replicated.

  10. Start Date - Any data before this date will not be replicated.

  11. Replication Span Period (optional) overrides the explicit end date by building a window ending at the configured start date. If no start date is configured, the window ends at the current UTC time.

  12. Click Save & Test.

During Save & Test, Daspire validates the Login with Amazon refresh-token exchange and a low-cost SP-API Orders request for each selected Amazon marketplace. Error messages distinguish LWA credentials, marketplace mismatch, missing SP-API permission, throttling, and Amazon server errors.

Supported sync modes​

The Amazon SP data source supports the following sync modes:

  • Full Refresh
  • Incremental

Supported streams​

This source is capable of syncing the following streams:

Report options​

On native connections, select the required streams in Replication settings and save. Saving a stream selection preserves the connection's existing sync progress and does not require worker or routing permissions. Reports you leave unselected remain disabled; a platform upgrade does not enable them for you.

Configure report request options in the connection Replication settings table. Amazon Seller rows that support report options show a Report settings control next to the stream's sync mode.

  • GET_SALES_AND_TRAFFIC_REPORT supports date aggregation (Daily, Weekly, Monthly) and product aggregation (Parent, Child, SKU).
  • Brand Analytics report streams support a Brand Analytics report period (Daily, Weekly, Monthly, Quarterly) when that period is valid for the selected Amazon report type. If no period has been saved yet, Brand Analytics defaults to Daily; GET_BRAND_ANALYTICS_REPEAT_PURCHASE_REPORT defaults to Weekly because Amazon does not support a daily period for that report type.
  • GET_EPR_MONTHLY_REPORTS uses the connection-level Acquisition Method cycle and currently supports Cycle = Last completed calendar month. This lets multiple connections reuse the same Amazon Seller Partner source while using different report-cycle behavior. Use a monthly connection schedule on day 2 when this stream must run once per month.

Troubleshooting​

An Amazon 403 for a selected report is an access failure, not evidence that the report contains no data. The Native connector preserves this error and does not acknowledge a successful checkpoint for that incomplete run. Check the application's permissions, seller authorization and region; exchanging an LWA access token successfully does not by itself verify access to reports. Do not reset a connection or replay an already committed job to resolve it.

Diagnose the exact denied report instead of treating every 403 as the same credential failure. For example, GET_MERCHANT_LISTINGS_ALL_DATA requires at least one of Amazon's Inventory and Order Tracking, Pricing, Direct to Consumer Shipping (Restricted), or Product Listing roles, while GET_SALES_AND_TRAFFIC_REPORT requires Brand Analytics. Confirm that the role is approved for the developer, applied to the exact application, and included in the seller's authorization for the affected marketplace region.

Amazon requires sellers to reauthorize a public application every 365 days and after the application adds a role. Reauthorization must complete the OAuth callback and replace the stored refresh token. Do not reauthorize solely because a request returned 403: first confirm the exact application, denied report, marketplace region, applied roles, and the seller authorization's last renewal date.

Max number of tables that can be synced at a time is 6,000. We advise you to adjust your settings if it fails to fetch schema due to max number of tables reached.

Data type mapping​

Integration TypeDaspire Type
stringstring
int, float, numbernumber
datedate
datetimedatetime
arrayarray
objectobject