Your menu on your site,
orders in your kitchen
Your website or app reads your Cibusy menu, sends orders straight to Cibusy POS and the kitchen and reservations to the venue's reservation list, and hears about every status change through webhooks.
POST /public/v1/venues/{venueId}/orders
X-Api-Key: cbk_••••••••
Idempotency-Key: web-order-2041
{
"type": "Takeaway",
"customer": { "name": "Ayşe", "phone": "+905550000000" },
"paymentMethod": "Card",
"lines": [{
"productId": "5d2c8a41…",
"portionId": "a8e1f6c3…",
"quantity": 2
}]
}
HTTP/1.1 201 Created
{
"success": true,
"data": {
"order": { "number": 57, "status": "Received", … }
}
}
Where to start
The guides take you step by step from your first request to verifying webhooks; the API reference covers every endpoint with its fields and samples.
Your Cibusy venue,
working on your own site
Edit your menu once in Cibusy: your website and your app show the same menu, and every order reaches the same kitchen.
Your menu on your site
Categories, portions, extras, allergens and stock status. A change you make in Cibusy shows in the API right away.
Orders straight to the kitchen
Table, takeaway and delivery orders reach Cibusy POS and the kitchen ticket prints at once. No approval step stands in between, and a request sent twice still reaches the kitchen once.
Reservations on the venue's list
A booking your site takes lands on the same list as the venue's other reservations. You take the times from the venue's own calendar, and your site tells the guest.
Status by webhook
Your server gets a signed notification while an order is prepared, when it is ready and when it is closed, and when a reservation is confirmed or called off. No polling needed.
Cibusy does the pricing
Price a basket before you send it. Your campaigns and service fee apply exactly as they do on an order taken at the till.
One key for your branches
A headquarter's key reaches every branch, while a branch's key reaches that branch only.
Your first request in three steps
Keys are created in the panel with your venue account; staff accounts cannot create them.
Sign in to the panel
Sign in to the Cibusy panel with your venue account and open API Keys under Venue Settings.
Create a key
Name the integration, choose whether it may send orders and take reservations, and add a webhook address. The key is shown only once, so copy it right away.
Call from your server
Send the key in the X-Api-Key header. Keys are used on servers only; calls made from a browser are not accepted.
Limits and rules
Paid at the venue
The API takes no payments; the customer pays at the venue. A mistaken order is cancelled at the till as well.
Rate limits
Each key may make about 120 reads and 30 order or reservation requests a minute. Keep a copy of the menu on your server and refresh it with its ETag.
Orders and reservations need a subscription
A key of a venue whose subscription has ended still reads the menu; sending orders or reservations needs an active subscription.
Create your key,
send your first request
Create an API key in the Cibusy panel with your venue account in a few seconds. The key is shown only once, so copy it right away.