Build on any Queek store.
Read a store's catalogue, build a cart and hand the shopper to Queek checkout. Follow every order with webhooks, and test it all on a dev store first.
- OpenAPI spec
- Dev store sandbox
- Signed webhooks
$ curl …/v1/store/products \ -H "X-Client-Key: sk_test_…"→ 200 OK · X-Queek-Mode: test$ curl -X POST …/v1/store/cart/items→ "checkout_url": "https://…"# Queek checkout completes the order
orders/paid200 OK
POST yourapp.com/hooks/queek
Pick your way into a Queek store.
Build a storefront, react to every order, or let an assistant run the store. It's the same catalogue and the same orders either way.
- Storefront API
Your own website or app on a Queek store.
Read the store, catalogue, pages and blog, manage a cart, and send shoppers to Queek checkout.
GET /store/products - Webhooks
Know the moment anything changes.
Signed events for orders, products, customers and stock levels, retried if your endpoint is down.
orders/paid - API overview
Keys, test mode, errors and limits.
Public, private and test keys, idempotency keys and a stable error vocabulary.
X-Client-Key: pk_live_… - MCP server
Run a store from Claude or ChatGPT.
Queek OS is the MCP server for a Queek store. Merchants add it to their assistant and manage one store in plain words.
tools/call list_orders
From test key to first order.
Build against a dev store first. Its orders never touch real money or deliveries, and going live is swapping the key.
- 1
Create a dev store
Create one free in your dashboard under Developers → Dev stores, and copy its sk_test_ key.
- 2
Read the catalogue
Send the key as X-Client-Key and read products, collections, pages and the blog. Every price is the final customer price.
- 3
Build a cart
Add items to a cart. Every cart reply carries a checkout_url that opens Queek checkout.
- 4
Follow the order
Queek checkout completes delivery, payment and the order, and webhooks tell your server as it moves.
# 1. Send the key on every requestX-Client-Key: sk_test_…# 2. Read the catalogueGET /store/products→ X-Queek-Mode: test# 3. Build a cartPOST /store/cart/items→ "checkout_url": "https://…"# 4. Queek completes the order→ orders/create→ orders/paid
A dev store behind every build.
Create a dev store in the Developers area. It is a standalone sandbox — never a copy of a live store and never promotable. Test keys only reach it, its orders never touch real money or deliveries, and every response says so.
Live store
pk_live_…sk_live_…Real orders, real money
Dev store
sk_test_…A standalone sandbox. Responses say X-Queek-Mode: test
Built to be read by people and agents.
Everything is documented, machine-readable and consistent across stores.
Read the docsOpenAPI spec
The full schema at client.usequeek.com/openapi.json.
An endpoint list for agents
client.usequeek.com/llms.txt, written for AI builders.
Public and private keys
Origin-locked keys for browsers, private keys for servers.
Dev stores
Test keys reach only your dev store.
Idempotency keys
Retry safely without double-writing.
Metafields and metaobjects
Custom fields and content types, typed and filterable.
Go deeper in the docs.
- Storefront quickstartRead a store's catalogue with an API key, then hand a cart to Queek checkout.docs.usequeek.com/docs/storefront
- AuthenticationOne header, two kinds of key, and the rules the browser key plays by.docs.usequeek.com/docs/storefront/authentication
- Dev storesA dev store with its own test keys, and nothing that can reach a real customer.docs.usequeek.com/docs/sandbox
- WebhooksTopics, the headers on a delivery, signature checks, retries and secret rotation.docs.usequeek.com/docs/webhooks
- Versioning and errorsWhat v1 promises, how a change is announced, and the shape every failure answers in.docs.usequeek.com/docs/versioning-and-errors
- ChangelogEvery change to the Storefront API, generated from the OpenAPI spec.docs.usequeek.com/docs/changelog
Developer questions, answered.
What you can build today.
Frequently asked questions
Can I create orders directly through the API?
No. You build a cart through the API, and every cart carries a checkout_url. Queek-hosted checkout then completes address, delivery, payment and the order.
Where do I get a key?
The merchant creates keys in their Queek dashboard under Settings, API keys. Public keys work from allowed origins; private keys are for servers.
Is there a sandbox?
Yes. Create a dev store in your dashboard under Developers → Dev stores. It is a standalone sandbox with its own sk_test_ keys, and its orders never move real money.
Can an AI build on the API?
Yes. client.usequeek.com/llms.txt describes the whole API on one page written for AI builders, and the OpenAPI spec carries the full schema.
Which plans include the API?
Every plan can use the API, the free plan included. Higher plans give private keys a larger request quota.
$ curl client.usequeek.com/llms.txt
Start building on Queek.
Read the docs, create a dev store, and ship.