Tenant from the token
The store you act on comes from your signed token, never from a header you set.
Developers
Build on the APIs we build on.
Our admin, website builder and checkout are clients of the same documented APIs you get. Take the whole platform or just the parts you need, and keep your own frontend.
# Read: instant
GET /api/2026-10/storefront/recommendations?productId=…
Authorization: Bearer <storefront token>
# Write: safe to retry
POST /api/2026-10/payments
Authorization: Bearer <integration token>
Idempotency-Key: 6f1c…e9
# Or let an agent do it, with a preview first
> confirm_action { action_id: "act_8Qm2…" }Principles
Boring in the right places.
Idempotent writes
Send an Idempotency-Key on anything that could double-apply: payments, bulk jobs, webhooks.
One error shape
Every error is the same structured body with a correlation ID, across every service.
One paging shape
Every list returns the same page envelope — no per-endpoint surprises.
Signed webhooks
Per-store secrets shown once, rotation, pause, and a delivery log.
Plain-language OpenAPI
Each endpoint says what it does in words a new engineer — or an agent — can act on.
Auth
Keys, tokens and shoppers.
- Scoped API keys, rotated with a grace period, revocable
- Client-credentials exchange for a one-hour integration token
- Storefront channel keys and shopper tokens: guest, password and refresh
- Staff roles and invitations with two-step verification
Surfaces
Admin API — for your back office and integrations
Storefront API — for any storefront, including ours
MCP tools — for AI agents, with preview and confirm
Webhooks and events — for your systems
Want API access or a technical walkthrough?
Tell us what you’re building and we’ll set up a sandbox store and walk through the contracts.