| name | amazon-seller-central |
| description | Amazon Seller Central integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Amazon Seller Central. Routes through Apideck with serviceId "amazon-seller-central".
|
| license | Apache-2.0 |
| alwaysApply | false |
| metadata | {"author":"apideck","version":"1.0.0","serviceId":"amazon-seller-central","unifiedApis":["ecommerce"],"authType":"oauth2","tier":"1c","verified":true,"status":"beta"} |
Amazon Seller Central (via Apideck)
Access Amazon Seller Central through Apideck's Ecommerce unified API — one of 17 Ecommerce connectors that share the same method surface. Code you write here ports to Shopify, BigCommerce, Shopify (Public App) and 13 other Ecommerce connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Amazon Seller Central plumbing.
Beta connector. Amazon Seller Central is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
Quick facts
When to use this skill
Activate this skill when the user explicitly wants to work with Amazon Seller Central — for example, "list orders in Amazon Seller Central" or "sync products in Amazon Seller Central". This skill teaches the agent:
- Which Apideck unified API covers Amazon Seller Central (Ecommerce)
- The correct
serviceId to pass on every call (amazon-seller-central)
- Amazon Seller Central-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
For the raw OpenAPI spec:
Minimal example (TypeScript)
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
const { data } = await apideck.ecommerce.orders.list({
serviceId: "amazon-seller-central",
});
Portable across 17 Ecommerce connectors
The Apideck Ecommerce unified API exposes the same methods for every connector in its catalog. Switching from Amazon Seller Central to another Ecommerce connector is a one-string change — no rewrite, no new SDK.
await apideck.ecommerce.orders.list({ serviceId: "amazon-seller-central" });
await apideck.ecommerce.orders.list({ serviceId: "shopify" });
await apideck.ecommerce.orders.list({ serviceId: "bigcommerce" });
This is the compounding advantage of using Apideck over integrating Amazon Seller Central directly: code against the unified Ecommerce API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
Authentication
- Type: OAuth 2.0
- Managed by: Apideck Vault — Apideck handles the full OAuth dance (authorization code flow, token exchange, refresh). Never ask the user for API keys or tokens directly.
- User setup: Users authorize via the Vault modal. Connection state progresses
available → added → authorized → callable.
- Token refresh: automatic. Expired tokens are refreshed transparently on the next API call.
Setup guide: Apideck publishes a step-by-step guide for registering an OAuth app / configuring credentials for Amazon Seller Central — see https://developers.apideck.com/connectors/amazon-seller-central/docs/consumer+connection. Use that as the authoritative source when walking users through connection setup.
See apideck-best-practices for Vault setup, connection lifecycle, and handling re-auth flows.
Verifying coverage
Not every Ecommerce operation is supported by every connector. Always verify before assuming a method works:
curl 'https://unify.apideck.com/connector/connectors/amazon-seller-central' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}"
See apideck-connector-coverage for patterns around UnsupportedOperationError and connector-specific fallbacks.
Escape hatch: Proxy API
When an endpoint isn't covered by the Ecommerce unified API, use Apideck's Proxy to call Amazon Seller Central directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Amazon Seller Central's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: amazon-seller-central" \
-H "x-apideck-downstream-url: <target endpoint on Amazon Seller Central>" \
-H "x-apideck-downstream-method: GET"
See Amazon Seller Central's API docs for available endpoints.
Sibling connectors
Other Ecommerce connectors that share this unified API surface (same method signatures, just change serviceId):
shopify (beta), bigcommerce (beta), shopify-public-app (beta), woocommerce (beta), ebay (beta), etsy (beta), magento (beta), bol-com (beta), and 8 more.
See also
