Queek developer docs

Build on a Queek store with the Headless API (formerly the Storefront API), the Merchant API, apps, themes and Queek OS. Pick what you are building and follow its quickstart.

Queek runs the shop: catalogue, cart, checkout, payment and delivery. What you build sits on top of it. Pick the thing you are building.

What are you building?

A website, mobile app or AI agent for a store

Connect it from Channels → Headless API, read the catalogue and hand the cart to Queek checkout. Headless API.

An integration for a store's own systems

Sync stock, move orders, manage the catalogue from your server with a scoped private key. Merchant API.

An app merchants install

An embedded page in the merchant dashboard, signed webhooks, scoped API access and storefront blocks.

A storefront theme

React and CSS on the Queek theme kit. Preview, check and submit with the queek CLI.

Store management from an AI assistant

Queek OS connects a store to Claude or ChatGPT so a merchant can run it in conversation.

Fastest path to a first response

A merchant (or you, on a dev store) opens Channels → Headless API in the Queek dashboard, presses Connect a site or app and gets a key.
Send it in the X-Client-Key header:

curl https://client.usequeek.com/v1/store/info \
  -H "X-Client-Key: pk_live_your_key_here" \
  -H "Accept: application/json"

That call returns the store's name, currency and opening hours. The Headless API quickstart takes it from there to a cart and a checkout handoff. The Merchant quickstart does the same for server-side work.

From quickstart to production

Step	What to do	Where
1. Build	Work against a dev store. Its orders never touch real money, customers or couriers.	Dev stores
2. Handle failure	Branch on `error.code`, honour `Retry-After`, send an `Idempotency-Key` on writes.	Versioning & errors, Merchant idempotency & limits
3. Receive events	Verify the signature on the raw body, dedupe on `webhook-id`, acknowledge fast.	Webhooks
4. Go live	Swap the `_test_` key for the `_live_` key. No path, header or body changes.	Dev stores

Shared conventions

Every Queek API follows the same rules, documented once.

Webhooks: order, product, customer, stock and translation events, signed with Standard Webhooks.
Dev stores: a developer-owned sandbox with sk_test_ and pk_test_ keys.
Versioning & errors: what v1 guarantees and the one error envelope.
Changelog: what changed and when.
Support: where to ask, and what to include.

Every page here is also available as plain Markdown for tools and agents: /llms.txt lists them and /llms-full.txt carries the lot.