At a glance
REST API (live)
Catalog, cart, checkout session, and subscription portal endpoints are available today.
Platform
Headless API and MCP
Use Quickshops as your commerce backend while you own the frontend. Pro unlocks API keys, MCP tools, and Telegram.
The Quickshops headless API lets you render your own storefront, mobile app, or internal tool while Quickshops runs catalog reads, carts, Stripe Checkout session creation, and subscription portals. Your API keys stay on the server—never in browser code.
Pro unlocks API keys, MCP server access, and Telegram for the store agent. The hosted storefront editor remains available if you want both a default shop and a custom frontend for specific flows.
MCP tools (Pro)
Expose store operations to MCP clients. Available on the Pro plan with OAuth or API key auth.
Secure key management
Create expiring keys on Pro, track last used timestamps, and revoke access instantly from the dashboard.
Documentation
Full API reference, authentication guides, and SDK examples.
Read the Quickshops developer docs for endpoints, request examples, MCP setup, and the TypeScript SDK. The API base URL is https://api.quickshops.app. MCP clients connect at https://mcp.quickshops.app/mcp.
Common use cases
When the hosted editor is not your frontend but Quickshops should still run commerce.
Custom storefronts
Render your own UI in Next.js, React Native, or any stack while Quickshops owns catalog reads, carts, and Stripe Checkout session creation. You control design; Quickshops controls commerce logic.
Server-side checkout
Create carts and checkout sessions from your backend with API keys that never ship to the browser. Fits teams that already have auth and want checkout as one API call from trusted infrastructure.
Agent and automation tooling
Connect MCP-compatible clients—Claude Desktop, Cursor, or your own agents—to the same API surface for workflow and ops automation alongside human sellers using dashboard chat.
Authentication and safety
Designed for trusted backend environments.
API keys from the dashboard
Issue, rotate, and revoke keys from Settings → API keys on Pro. Keys use the qk_ prefix format.
Per-key rate limits
Production traffic is rate-limited per API key. Responses include x-request-id for debugging support requests.
Server-side only
API keys belong in backend code. Missing or invalid keys return standard authentication errors. Do not embed keys in client bundles or mobile apps without a backend proxy.
Get your first key
Create a Pro account and issue a key from the dashboard.
Open Settings → API keys on Pro to issue your first key. The TypeScript SDK targets https://api.quickshops.app out of the box.
Need a workflow we do not cover yet? Tell us what you are building. Pair the API with payments docs if you are wiring checkout for the first time.
Explore more
See how this feature fits with the rest of the Quickshops stack.