Skip to content
sandadocs
Console Start free trial

Amazon Seller Partner

Connect Amazon Seller Partner to sanda: what to prepare, the fields the connection form asks for, and how its data lands in your warehouse.

View as Markdown

Connect Amazon Seller Partner

  1. Open the catalogue. In the console, go to Data · Connections and press New connection.
  2. Choose Amazon Seller Partner. It is listed under commerce; you can also search for it by name.
  3. Fill in the form. Enter the fields below. Credentials go straight to sanda’s sync engine and are never stored in sanda’s database.
  4. Choose what to sync. Pick the streams you want, and a sync mode for each. See choose what to sync.
  5. Run the first sync. sanda tests the connection, then lands each stream as a table in your warehouse.

Configuration fields

What the connection form asks for. Required fields are marked; the rest are optional.

Field Type Required Description
Environment string Yes Select the Environment. One of PRODUCTION, SANDBOX. Default PRODUCTION.
Region string Yes Select the Region. One of AE, AU, BE, BR, CA, DE, EG, ES, FR, GB, IE, IN, IT, JP, MX, NL, PL, SA, SE, SG, TR, UK, US. Default US.
Seller Partner Account Type string Yes The type of Amazon Seller Partner account to authorise. One of Seller, Vendor. Default Seller.
Application ID string, secret No Your Amazon Application ID.
LWA Client Id string, secret Yes Your Login with Amazon Client ID.
LWA Client Secret string, secret Yes Your Login with Amazon Client Secret.
Refresh Token string, secret Yes The Refresh Token obtained via OAuth flow authorization.
Start Date string No UTC date and time in the format 2017-01-25T00:00:00Z. Any data before this date will not be replicated. If start date is not provided or older than 2 years ago from today, the date 2 years ago from today will be used.
End Date string No UTC date and time in the format 2017-01-25T00:00:00Z. Any data after this date will not be replicated.
Period In Days integer No For syncs spanning a large date range, this option is used to request data in a smaller fixed window to improve sync reliability. This time window can be configured granularly by day. Default 90.
Sales and Traffic Report ASIN Granularity string No The level of ASIN granularity for the Sales and Traffic report streams. PARENT returns data aggregated at the parent ASIN level. CHILD returns data at the child ASIN level with populated childAsin values. SKU returns data at the individual SKU level with populated childAsin and sku values. One of PARENT, CHILD, SKU. Default PARENT.
Report Options array No Additional information passed to reports. This varies by report type.
Financial Events Step Size string No The time window size for fetching financial events data in chunks for the ListFinancialEvents and ListFinancialEventGroups streams. Options include hourly (1H, 6H, 12H) and daily (1D, 7D, 14D, 30D, 60D, 90D, 180D) granularity. Hourly step sizes (e.g., 1H, 6H) are recommended for very high data volumes where daily windows cause pagination token expiration (TTL errors). They fetch smaller chunks per request, reducing the risk of timeouts. Daily step sizes (e.g., 1D, 7D) are better for moderate data volumes. They balance sync speed with API efficiency. Larger step sizes (e.g., 30D, 180D) are better for smaller data volumes. They fetch more data per request, speeding up syncing and reducing the number of API calls. Select a step size that matches your data volume to optimize syncing speed and API performance. One of 1H, 2H, 4H, 6H, 8H, 12H, 1D, 7D, 14D, 30D, 60D, 90D, 180D. Default 180D.
Max Age of Completed Reports to Reuse (Hours) integer No When the connector finds an existing completed (DONE) report matching the same date range and marketplace, it can reuse that report instead of creating a new one. This setting controls how old (in hours) a completed report can be and still be reused. Set to 0 to always create new reports. Maximum is 72 hours. Default 0.
Number of Workers integer No The number of workers to use for the connector when syncing concurrently. Default 2.
Maximum Concurrent Async Job Count integer No The maximum number of concurrent asynchronous job requests that can be active at a time. Default 2.
Include PII (Personally Identifiable Information) boolean No When enabled, the connector requests a Restricted Data Token (RDT) to access PII fields such as BuyerInfo and ShippingAddress in the Orders and OrderItems streams. Your Amazon SP-API developer profile must have an approved Restricted Role (Direct-to-Consumer Shipping or Tax Invoicing). If the RDT request is denied (HTTP 403), the connector falls back to the standard token automatically and PII fields remain empty. Default false.
Financial Events Max Results Per Page integer No The maximum number of results to return per page for the ListFinancialEvents stream. If the response exceeds the maximum number of transactions or 10 MB, the API returns an InvalidInput error. Lower this value if you encounter InvalidInput errors during sync. Valid range is 1-100. Default 100.
Report Stream Lookback Window (Hours) integer No Number of hours to re-fetch for incremental report streams on each sync. Increase this value if Amazon continues updating report data after the previous sync has completed. Duplicates from the lookback window are handled by destination deduplication. Set to 0 to disable. This does not apply to GET_SALES_AND_TRAFFIC_REPORT_BY_MONTH or GET_VENDOR_SALES_REPORT, which use monthly or date-only report boundaries. Default 0.
Failed Report Retry Wait Time (Seconds) integer No Time in seconds to wait before retrying a report that returned FATAL status. Amazon enforces per-report-type cooldowns after generating a report. Near-real-time FBA reports have an approximately 30-minute cooldown, daily FBA reports approximately 4 hours. The default of 1800 seconds covers the most common cooldown. Increase this value if you see repeated FATAL errors on daily FBA reports. Default 1800.
Report Creation 429 Max Retries integer No Maximum number of retry attempts when the report creation API returns HTTP 429 (Too Many Requests). Each retry uses exponential backoff based on the x-amzn-RateLimit-Limit header. Reduce this value to avoid exhausting rate limits on retrying requests. Default 5.
Stop Sync When Report Streams Are Rate Limited boolean No Only applies to report streams. When enabled, the source stops retrying immediately once the rate limit retry budget is exhausted and fails with an actionable configuration error. This is useful when persistent rate limiting indicates the connector configuration needs adjustment (such as reducing the number of report streams or increasing the sync interval). When disabled (default), the source applies its backoff and retry strategy; if all retry attempts are exhausted, a transient error is thrown and the sync may be rescheduled automatically. Default false.
Inbound Replication Mode string No Settings only for Fulfillment Inbound streams. Use fixed datetimes or rolling window (last N days). When inbound_replication_mode=fixed, inbound_start_datetime is required. When inbound_replication_mode=rolling_days, inbound_rolling_days is required. One of fixed, rolling_days. Default rolling_days.
Inbound Start Datetime string No Only used when inbound_replication_mode=fixed. Required when inbound_replication_mode=fixed. UTC datetime in format 2026-01-25T00:00:00Z.
Inbound End Datetime string No Only used when inbound_replication_mode=fixed. Optional when inbound_replication_mode=fixed. If not set, the connector uses the current UTC time. UTC datetime in format 2026-01-25T00:00:00Z.
Inbound Rolling Days integer No Only used when inbound_replication_mode=rolling_days. Required when inbound_replication_mode=rolling_days. Fetch data including today, for the last N days. Default 30.

Something unclear or out of date? Tell us, and we will fix the page.