App & API Docs

Build integrations against Cartisto stores over a versioned REST API. Every store is isolated (multi-tenant), every response has the same shape, and access is granted with scoped API keys a merchant controls.

Start here

• Getting started — base URL, your first authenticated call.
• Authentication — the store identities and how API keys work.
• API keys — creating, scoping, and rotating keys.
• Conventions — response envelope, errors, pagination, rate limits.
• Endpoint catalog — every resource under /api/v1, grouped by domain.
• Resource reference — field-level detail: Products, Orders, Customers.
• Webhooks — subscribe to store events and verify delivery.

The shape of everything

{ "success": true, "message": "…", "data": { } }

Every endpoint returns this envelope. Errors set success: false with a message and an HTTP status. That predictability is the point — see Conventions.

Multi-tenancy in one paragraph

Each store is a tenant, isolated at the database level. A request is resolved to a tenant by its host (the store’s domain/subdomain), and your API key is scoped to that store. You never pass a tenant id — it’s inferred from where the request lands, and the platform enforces that you only ever see one store’s data.