What the Open API does not cover
Sellers manage these areas in Seller Center. We list them explicitly so you can scope accurately rather than discover each gap during a build.
| Area | Status | Where it lives |
|---|---|---|
| Balance, withdrawals, bank accounts | Deliberately deferred | Seller Center → Balance |
| Income statements, tax documents, settlement reports | Deliberately deferred | Seller Center → Income (production only; the Sandbox Seller Center has no payout reports — see Payouts in sandbox in the Sandbox guide) |
| Shop settings — shipping, payment, product defaults | Read-only via API; no write path | Seller Center → Shop settings |
| Vacation mode | Readable via GET /shop/status; no write path | Seller Center → Vacation mode |
| Chat and customer service | Not exposed | Seller Center → Customer service |
| Review management | Not exposed | Seller Center → Reviews |
| Business insights and analytics | Not exposed | Seller Center → Business insights |
| Listing violations and violation history | Not exposed | Seller Center → Violations |
| Product attribute values | Definitions readable; no write path | Seller Center → Product edit |
| Product image upload | Not exposed — supply https URLs | Your own CDN |
| Variant add, edit or removal after creation | Not exposed | Seller Center → Product edit |
| Bulk product update | Not exposed — bulk is create-only | Seller Center → Mass update |
On the finance endpoints specifically. These are deferred by design rather than overlooked. They will be
revisited once commission rate rules are frozen, the payout schedule is signed off, and the finance team confirms which
fields can be exposed externally. Until then, derive equivalent reporting from GET /orders and
GET /payouts combined with your own commission model.
Endpoints that are not fully available
Some endpoints are in the API reference but carry a known limitation, or are documented ahead of production support. Their reference page shows a badge next to the method and path, and a workaround where one exists. An endpoint with no badge is fully available.
| Tier | Badge | What it means |
|---|---|---|
| Available | None | Works as documented in sandbox and production. Build on it. |
| Limited | Limited | You can call it, but part of its behaviour is limited or not yet confirmed for production use. The page says which part, and the workaround says how to cover it — usually by doing that step in Seller Center for now. |
| Not yet available | Not yet available | The contract is published so you can plan for it, but it is not yet supported for production integrations. Do not build a production flow on it; use the workaround where the page gives one. |
Request and response examples are shown on Available and Limited pages. Not yet available pages omit them.