Partner API
Build on klikit.
One API layer on top of the POS you already run. Connect to klikit merchants for orders, menus, stock and payouts, from a free sandbox to production keys.
The idea
Keep your POS. Add every channel.
Your hardware, staff training and counter workflow stay exactly as they are. The Partner API connects your system to klikit merchants through REST, webhooks and MCP.
You keep
Your POS: hardware, staff training and counter workflow, unchanged.
Delivery channels
Orders from every delivery app, in your system.
Menus everywhere
Read menus, push availability and visibility.
Stock and kitchen
Inventory and production, in step with sales.
Payouts
Disbursement for the money your merchants are owed.
AI agents
An MCP server so coding agents read the docs themselves.
Who builds on klikit
POS, ERP and loyalty platforms
Connect your product to klikit merchants: orders, menus, stock.
Merchant tech teams
Build your own tooling on top of your klikit data.
Integrators and agencies
Deliver klikit integrations on behalf of merchants.
AI coding agents
Read the docs directly while writing integration code.
What you can do today
Read orders
List and fetch orders across a business, filtered by brand, branch, status and date.
Read menus
Pull one store's menu with its overrides applied, or the whole business's.
Push availability
Mark items in or out of stock, one at a time or in bulk, safely retried.
Subscribe to events
Real-time webhooks when orders are created, change status or change cart.
Two integration paths
Pick the path that fits your system.
POS or kitchen system
Orders flow from klikit into your POS, and status updates (accepted, ready, picked up) flow back.
Aggregator or marketplace
klikit menus appear on your surface, and you toggle items in and out of stock and hide stores.
Both paths add real-time webhooks and finish with a production checklist.
How it works
From sign-in to production keys.
- Steps 1–3 · Sandbox · Fast track01
Sign in
Work email and a one-time code. No passwords.
- Steps 1–3 · Sandbox · Fast track02
Read
The Getting Started track and the Integration Playbook.
- Steps 1–3 · Sandbox · Fast track03
Apply
Pick products and sign the partner terms. klikit confirms your merchant.
- Steps 4–6 · Production · Team review04
Build
Sandbox keys, the playground, Ask AI and your own coding agent.
- Steps 4–6 · Production · Team review05
Review
Apply for production. The klikit team reviews the merchant and scopes.
- Steps 4–6 · Production · Team review06
Go live
Generate production keys. They are shown once.
Environments
Sandbox and production, side by side.
| Sandbox | Production | |
|---|---|---|
| Purpose | Build and test on realistic data. | Live data for a real klikit merchant. |
| You provide | Integration type, products, market. | Plus the merchant you integrate for, your legal entity and your use case. |
| Review | Fast track. | The klikit team confirms the merchant and the scopes. |
Every credential is scoped to one business, production keys are shown once, and access can be revoked at any time.
Indicative guide · USD
Pricing that scales with volume.
Starter
1–10 stores
US$49/store/mo
- Webhooks only
- Order and menu events
- Standard support
Growth
11–50 stores
US$39/store/mo
- Webhooks only
- Order and menu events
- Priority support
Scale
51–200 stores
US$29/store/mo
+ Custom build fee applies
- Full Partner API
- Inventory and Disbursement
- Named integrations lead
Enterprise
200+ stores
Custom
+ Custom build fee applies
- Everything in Scale
- Volume pricing
- Custom SLA
Indicative only. Final pricing is confirmed at production approval, based on active stores and order volume.
For AI coding agents
Let your agent read the docs itself.
The Partner Portal has an MCP server and plain-text docs, so Claude Code, Cursor and other coding agents can search and read the integration guide while they write your integration.
1. Create a docs token
A person on your team signs in at portal.klikit.io and creates a personal token (kpt_…) for each agent or machine. Up to 10 at a time; revoke one without affecting the others.
2. Connect your agent
Add the MCP server with your token. Any MCP client that supports Streamable HTTP and custom headers works.
3. What your agent can do
Three read-only tools, up to 120 calls a minute per token:
search_docsfinds the sections that best match a query, with URLs and a snippet.get_pagereads a page in full, as Markdown.list_pageslists every page with its URL and description.
Without MCP
Send the same token as a Bearer header to fetch every page as one text file, or add .md to any page URL. The page index at /llms.txt is public.
A docs token only reads the docs. It cannot call the Partner API: API credentials come from your approved application in the portal and should live in your secrets manager, never in code or git.
Claude Code
claude mcp add --transport http klikit-docs https://portal.klikit.io/mcp \ --header "Authorization: Bearer kpt_…"
Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"klikit-docs": {
"url": "https://portal.klikit.io/mcp",
"headers": { "Authorization": "Bearer kpt_…" }
}
}
}VS Code (.vscode/mcp.json)
{
"servers": {
"klikit-docs": {
"type": "http",
"url": "https://portal.klikit.io/mcp",
"headers": { "Authorization": "Bearer kpt_…" }
}
}
}Brief for your agent
Paste this into your coding agent's context before it starts.
You are building an integration with klikit, a restaurant operating system used by merchants across Asia. Docs: https://portal.klikit.io (MCP server at https://portal.klikit.io/mcp, page index at https://portal.klikit.io/llms.txt). Use search_docs / get_page before writing code; prefer the docs over assumptions. What the klikit Partner API covers: reading orders and menus, pushing item availability (in/out of stock) and store visibility, and webhooks for order events. Inventory and Disbursement are separate products with their own docs. How to work: 1. Read the Integration Playbook first. It is phased: foundation (credentials, environment, scopes), map the business (brands and branches), then ONE path: POS/kitchen system (orders in, status back) or aggregator/marketplace (menus out, availability and visibility in), then webhooks, then the production checklist. 2. Every credential is scoped to one business. Build and test against the sandbox (development) environment; production access requires an approved application. 3. Send an Idempotency-Key on every write. Verify webhook signatures before trusting a payload. 4. Never hard-code or commit credentials. Read them from environment variables or a secrets manager. A docs token (kpt_…) only reads the docs; it cannot call the Partner API. 5. When something in the docs is unclear, stop and ask the human rather than guessing at behaviour.
Get started
Start in the sandbox today.
Sign in with your work email, read the playbook and apply for sandbox keys. It's free, and your team or your coding agent can start building straight away.