The public API behind every Queek storefront,so yours can live on any site you build.
- Give any AI your key and one URL. It builds your store.
- Your catalogue, your brand, your checkout, on any site you build.
The Storefront API is the public, read-and-cart API behind every Queek storefront. Build your own site on it, or hand your key to an AI and let it build one for you. Checkout stays on Queek, so you never touch payments.
Request
GET/store/info
X-Client-Key: pk_live_…
Returns
- name"Mama's Kitchen"
- currency"NGN"
- brand.colors{ primary, accent, … }
- checkout_url"https://…"
A storefront API usually stops at the page. This one carries the cart to a real Queek checkout.
Everything an AI needs to build your store, at one address.
Paste this URL into any AI that can read the web, give it your key, and it has the whole API: what to call, what comes back, and how checkout works. Humans get the same page, plus the OpenAPI spec.
https://client.usequeek.com/llms.txtGet a key, read the store, hand the cart to checkout.
Every request carries one header. Reads cover the store and its catalogue; the cart returns a checkout_url that Queek takes from there.
- 01
Get a key
Create it in the Queek dashboard under Settings → API keys. A pk_live_ public key is safe in browser code from the origins you allowlist; an sk_live_ private key is for your servers.
X-Client-Key: pk_live_… - 02
Read the store and catalogue
Profile, brand kit, products with search, filters and pagination, categories, collections, promotions, reviews, pages, policies, blog and galleries. Every price is the final customer price.
GET /v1/store/info - 03
Cart, then checkout_url
Add items to a cart. The reply carries checkout_url. Redirect the shopper there and Queek runs address, delivery, payment and order confirmation on the merchant's own storefront.
POST /v1/store/cart/items
The whole storefront, as data.
Everything a Queek storefront renders is readable over the API, so whatever you build can be as complete as the store it comes from.
Store profile & brand kit
Logo, colours, fonts, contact details and socials.
Products
Search, filters and pagination, priced at the final customer price.
Categories & collections
The store's own structure, ready to navigate.
Promotions
What is on offer, as the store has set it up.
Reviews & Q&A
Real customer reviews and questions per product.
Pages & policies
About, shipping, returns and every custom page.
Blog & galleries
Posts and image galleries the store publishes.
Cart
Add, update, remove, then a checkout_url to hand off.
Two calls and you have a store with a working checkout.
Read the store to pick up its brand, add to a cart to get a checkout_url. Responses below are trimmed to the fields that matter; the full shapes are in the OpenAPI spec.
Read the store
GET/store/info
- name:"Mama's Kitchen"
- currency:"NGN"
- brand.colors:{ primary, accent, … }
- checkout_url:"https://…"
Add to the cart
POST/store/cart/items
- result:"added"
- cart.checkout_url:"https://…"
- Every price returned is the final customer price.
- Reads support ETag and 304 Not Modified.
- Errors are JSON with an error_code.
Every endpoint, live from the spec.
The reference below is rendered from the same OpenAPI document the service publishes, so it is always current.
Straight answers about building on it.
What the API does, what Queek keeps, and the one thing that does not exist yet.
Do I need to build checkout?
No. The cart reply carries a checkout_url. Send the shopper there and Queek runs address, delivery, payment and order confirmation on the merchant's own Queek storefront. Your build never touches payments. It is the same model as Shopify Headless: catalogue and cart on the API, hosted checkout.
Can my AI use it?
Yes. Give it your key and https://client.usequeek.com/llms.txt. That one page describes the whole API in a form an AI can read, so it can build the store for you.
Which key goes where?
A pk_live_ public key belongs in browser code and works from the origins the merchant allowlists. An sk_live_ private key belongs on your servers and must never ship to a browser. Both are created in the Queek dashboard under Settings → API keys, and both are sent in the X-Client-Key header.
Is there a sandbox?
Not yet. Keys are live keys; test on a store you own.
Your catalogue, your brand, your checkout, on any site you build.
Create a key in the dashboard, hand the docs to yourself or your AI, and ship a storefront that checks out on Queek.