Can I Get GoFood, GrabFood and ShopeeFood Orders Into My Own POS by API, Without Changing POS?
Short answer: yes. You keep your own POS, ERP or kitchen system. The delivery apps connect to klikit, and your system connects to klikit through the klikit Partner API: a webhook tells your system the moment an order is created, changes status or has its items changed, and your system can read the full order by REST. You build and test against a free sandbox. Production access is reviewed by klikit. You don't buy a klikit package on top: the Partner API fee covers it, with indicative pricing from US$49 per store per month for 1–10 stores.
Who this is for
- Restaurant groups with their own POS or ERP who want delivery orders to land in the system they already run, with their own stock and reporting.
- POS and ERP vendors whose customers ask for GoFood, GrabFood and ShopeeFood orders inside the vendor's product.
- Integrators and agencies building this connection for a merchant.
If you would rather use klikit's own POS and order screen, you don't need the API: the Omni add-on connects the delivery apps directly. See packages.
How it works
- The delivery apps connect to klikit. Your outlets are set up in klikit, and GoFood, GrabFood, ShopeeFood and the other apps you sell on are connected there. Every order from every app arrives in klikit in one format.
- klikit pushes each order event to your system. You give klikit a receiver URL and subscribe to three events:
klikit.order.created.v2: a new order.klikit.order.status.updated: the order moved on, including cancellation.klikit.order.cart.updated: the items or quantities in the order changed.
- Your system reads the details. REST endpoints return the full order (cart, customer, payment and fulfilment details), the list of orders filtered by brand, branch, status and date, and each store's menu with its overrides applied.
- Your system writes back (on the full Partner API): move an order through accepted, ready and picked up, or reject or cancel it with a reason code, and mark menu items in or out of stock, one at a time or in bulk.
Every credential is scoped to one business, so a key can only see that business's brands and branches. Authentication is HTTP Basic with a partner key and secret.
Sandbox and testing
Yes, there is a sandbox, and it is free. klikit's development environment is the sandbox: it has realistic data in exactly the same shapes as production, and separate credentials, so nothing you do there touches live orders. Sign in to the Partner Portal with your work email, read the Getting Started track and the Integration Playbook, and apply for sandbox keys. The Playbook takes you from your first call to a test order you can accept, mark ready and mark picked up.
Getting production access
Production keys are not self-serve. You apply from the portal with the merchant you are integrating for, your legal entity and your use case, and the klikit team confirms the merchant and the scopes before you can generate production keys. Production keys are shown once and can be revoked at any time.
What it costs
The Partner API fee is the whole cost: you don't need a klikit POS package (Core or Omni) as well. Indicative pricing, in US dollars. Final pricing is confirmed at production approval, based on active stores and order volume.
| Tier | Stores | Price | Includes |
|---|---|---|---|
| Sandbox | Any | Free, always | Development environment |
| Starter | 1–10 | US$49 / store / month | Webhooks only, order and menu events, standard support |
| Growth | 11–50 | US$39 / store / month | Webhooks only, order and menu events, priority support |
| Scale | 51–200 | US$29 / store / month + custom build fee | Full Partner API, Inventory and Disbursement, named integrations lead |
| Enterprise | 200+ | Custom + build fee | Everything in Scale, volume pricing, custom SLA |
So a 24-outlet group falls in Growth, at an indicative US$39 per outlet per month. If you need to write order status or stock back to klikit at that size, say so when you apply: the full Partner API is listed from the Scale tier.
Common questions
Can I subscribe to the delivery-app integration only, without using klikit's POS?
Yes. Your staff keep using your own POS. Your outlets are still set up in klikit, because that is where the delivery apps connect, and your POS takes the orders from klikit through the Partner API. You don't pay for a klikit POS package as well: the Partner API fee covers it.
Is there a webhook for new GoFood, GrabFood and ShopeeFood orders?
Yes. klikit.order.created.v2 fires for new orders from every connected delivery app, so you write one receiver rather than one per app. Status changes (including cancellation) and item or quantity changes have their own events.
Do you charge per order?
The indicative Partner API pricing is per store per month. Final pricing is confirmed at production approval and takes active stores and order volume into account.
How long does it take?
Sandbox keys are a fast track once you have signed in and applied. The Integration Playbook is written as a phased plan, from first call through webhooks to a production checklist. How long the build takes depends on your system; production access follows a review of the merchant and scopes by the klikit team.
Is there a public developer portal or self-serve API key?
The documentation and sandbox application are on the Partner Portal. Production credentials are only issued after the klikit team approves the application; you cannot generate them from inside klikit Cloud.
We already use klikit's GrabFood or GoFood integration. Does that include API access?
No. The delivery-app integrations bring orders into klikit for the merchant. API access to klikit for your own system is the Partner API, which is a separate application. See Does klikit have an API for developers or partners?
Next step
Read the Partner API overview, download the primer from the Partner Portal, and apply for sandbox keys. If you are a restaurant group and not a developer, contact us and tell us your outlets, the apps you sell on and the POS or ERP you run.