Skip to main content
Use the @bijection/connectors/amazon-selling-partner entrypoint to declare Amazon Selling Partner API resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Orders

pull: Fixed LastUpdated windows paged by NextToken

The following example matches configuration standard.

Configuration: standard

Case: amazon-selling-partner/orders/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: amazon-selling-partner. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: orders
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection dials the regional endpoint https://sellingpartnerapi-{region}.amazon.com (region setup: na, eu or fe) and reads the marketplaceIds setup (comma-separated). The credential is an OAuth refresh envelope over the seller’s Login with Amazon (LWA) refresh token. SP-API takes the access token in x-amz-access-token with no scheme, so the envelope’s token protocol sets bearer_header; without it the engine sends Authorization: Bearer, which SP-API refuses:
The Sellers API names marketplaces, not the seller, so the connection asserts no account identity. orders.pull reads Orders API v0 getOrders in one fixed window [LastUpdatedAfter, LastUpdatedBefore] per pass, fixed on its first page three minutes before the clock (Amazon requires two) and paged by NextToken, 100 an answer. The first pass reaches back two years; a finished pass carries the window’s end and the next begins five minutes before it. Re-read orders deduplicate by LastUpdateDate. OrderStatus is kept as stated; OrderTotal.Amount is exact decimal text with its CurrencyCode. getOrders is a burst of 20 and one a minute, declared as the connection’s token bucket. Not built: buyer and address fields need a restricted data token, which no credential envelope mints; Orders v2026-01-01; the Reports API (a report document is a gzipped tab-separated file at a presigned storage address, outside the connection’s origin and the provider-job result contract); notifications (SQS or EventBridge destinations only); writes. Nothing here has run against Amazon or been qualified; the bearer_header presentation is unit-tested in the engine only.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.