Your own system, connected by webhook.
Using your own POS, ERP or a system that isn’t in our directory? Orderli sends every order to a URL you choose, with your own product ids.
Your orders in Orderli
Your own system- Orders and payments
- Menu and bill
What the Webhook API sends
Everything marked yes goes across automatically.
| What | Does it work? |
|---|---|
| Orders to your URLAs JSON: order type (table, takeaway or delivery), table number, requested time, comment, guest details and the lines with your product and option ids. | Yes |
| ConfirmYour system replies with a plain OK once the order is in. | Yes |
| Menu from your own systemOrderli asks for your menu and your system sends it back. Nothing is typed twice. | Yes |
| Fetch the billOptional: Orderli requests a table’s bill, so guests can pay at the end. | Yes |
| Report paymentOptional: when a guest pays the bill, your system receives the table number and amount. | Yes |
What the integration costs is on the pricing page. See pricing
How you go live with the Webhook API
We do the technical work. You tell us how your venue runs.
Give us a URL or ask for a token
You give us the address orders should go to, or we create a token for you.
Choose what goes across
We agree which data your system receives and what it sends back.
A test message first
A test order goes to your system. Only when it arrives correctly does it go live.
Venues already using Orderli
Questions about the Webhook API
When do I choose the Webhook API?
When your POS or system isn’t in our directory, or when you build your own software.
Is there documentation?
Yes. We send you the contract with example messages and help you think through the setup.
Is this the same as the Orderli API?
No. The Webhook API sends orders to your system. With the Orderli API your system fetches data itself, with a key that can only do what is needed.
Do I have to build everything?
No. Receiving orders is enough to start. Fetching the menu and settling bills can be added whenever you like.
Your question not here?
