FousZomato Restaurant Partner
Pull your Zomato payouts and orders into your systems
Read the Order Level tab of your Weekly Payout statement, your Order history and each outlet's status from Zomato with one API call each. A workflow can hand the week's Net Order Value per order to accounting every Monday.
Works with your own Zomato Restaurant Partner account. Fous is an independent product.
What you can build on Zomato
Get the weekly payout statement
Build thisReads the Order Level tab of the Weekly Payout statement in the Payout section for one outlet and one payout week.
- Takes
- Outlet, week
- Returns
- Order ID, order date, Order Value, service fee, other charges, Net Order Value, Food Rescue flag
Get order history
Build thisReads the Order history section for one outlet and a date range: each order, its items, its status and its value.
- Takes
- Outlet, from date, to date, status (optional)
- Returns
- Order ID, placed at, items, status, rejection or cancellation reason, Order Value
Check outlet status and timings
Build thisReads whether an outlet is on or off for orders, the offline reason when it is off, and its operational hours.
- Takes
- Outlet
- Returns
- Outlet name, online or offline, offline reason, operational hours by day
Mark a menu item out of stock
Build thisFinds an item on the outlet's menu and marks it out of stock, or back in stock.
- Takes
- Outlet, item name, in stock or out of stock
- Returns
- Outlet name, item name, category, stock status
Automate Zomato with a workflow
A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.
Weekly Payout statement, order by order, to accounting
Build this- Starts
- Every Monday at 10:00 India time
- Step 1
- For each outlet you name, get the Order Level tab of last week's Weekly Payout statement.
- Step 2
- Keep each order's ID, date, Order Value, service fee and Net Order Value.
- Step 3
- Post the rows, one batch per outlet, to your accounting system's webhook.
Outlets switched off during service hours
Build this- Starts
- Every day at 12:00 and 19:00 India time
- Step 1
- For each outlet, check its status and timings.
- Step 2
- Keep the outlets that are offline inside their operational hours.
- Step 3
- Email you the list with each outlet's offline reason.
Yesterday's rejected and cancelled orders
Build this- Starts
- Every day at 8:00 India time
- Step 1
- For each outlet, get yesterday's Order history.
- Step 2
- Keep the orders that were rejected or cancelled.
- Step 3
- Group them by reason with an AI step and post them to your Slack webhook.
You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.
Once built, one call from your code
Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get the weekly payout statement” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "zomato.com/get_weekly_payout_statement",
"input": {
"outlet": "Acme Kitchen, Indiranagar",
"week": "2026-11-02"
}
}'
{
"status": "completed",
"data": {
"outlet": "Acme Kitchen, Indiranagar",
"week": "2026-11-02 to 2026-11-08",
"orders": [
{
"order_id": "7310045821",
"order_date": "2026-11-03",
"order_value": 642,
"service_fee": 128.4,
"other_charges": 12.84,
"net_order_value": 500.76,
"food_rescue": false
}
],
"total_order_value": 1031,
"total_net_order_value": 804.18,
"currency": "INR",
"count": 1
}
}
An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.
Zomato’s own options
Zomato's POS Integration API manages menus, orders and outlets, but it is for POS vendors: Zomato asks for 500 onboarded restaurants or 50,000 orders a month, 99.999% uptime and a 24x7 on-call channel, and decides eligibility itself. A restaurant uses it through such a POS. Payouts and the Order history are in the Restaurant Partner app and web dashboard.
| Option | What it covers | What it takes |
|---|---|---|
| Zomato POS Integration API | Menu, order and outlet management over JSON REST APIs, with Zomato's updates, customer complaints included, sent to the vendor's webhooks. | A POS vendor with 500 restaurants or 50,000 monthly orders, full critical feature parity and 99.999% uptime. Zomato decides. |
| A POS integrated with Zomato | Orders arrive in the POS, which also updates the menu, stock and outlet hours on Zomato. | A POS from a vendor already integrated with Zomato. |
| Zomato by hand | The Restaurant Partner app and web dashboard: Order history, the Payout section and the Weekly Payout statement, one outlet at a time. | A Zomato restaurant partner account. |
Read on November 12, 2026: Zomato POS Integration API: overview, Zomato POS integration prerequisites, Terms and Conditions for Online Ordering.
Signing in to Zomato
Zomato's restaurant partners work in the Restaurant Partner app, in the Merchant Application on a tablet or Zomato device, or in a Zomato web dashboard. With Fous you sign in once through Zomato's own partner sign-in with your own account. The login is sealed with AES-256, never returned by the API or written to logs, and code and AI agents never see it.
Worth knowing
- The API is for POS vendors
- Zomato's POS Integration API asks for 500 onboarded restaurants or 50,000 orders a month, 99.999% uptime and an on-call channel answering within 10 minutes. A single restaurant reaches it only through such a POS.
- Weekly or daily payouts
- Payouts are weekly by default. Daily payouts, announced in January 2024 for partners with 100 or fewer orders a month, settle sales from three days earlier and are switched on in the Payout section at no extra cost.
- Reconcile on Net Order Value
- Zomato's terms define Net Order Value as the Order Value less the service fee and other charges due to Zomato. Reconcile each order on that figure, not on the Order Value.
- Food Rescue orders in two places
- A cancelled order claimed through Food Rescue shows in Order history and in the Weekly Payout statement's Order Level tab. You keep the original order's compensation plus a portion of what the new customer paid.
More in Food service, restaurants and alcohol
- SGWS Proof
- Provi
- myCoke
- BEES
- METRO Online-Kundenkonto
- Sligro
- Deliveroo Partner Hub
- DoorDash Merchant Portal
- foodpanda Partner Portal
- Glovo Manager Portal
- GrabMerchant
- Grubhub for Restaurants
- iFood Portal do Parceiro
- Just Eat Partner Hub
- PedidosYa Partner Portal
- Rappi Aliados
- Swiggy Partner
- Uber Eats Manager
- Wolt Merchant Portal
- 饿了么商家版
- 배민셀프서비스
- Gordon Ordering
- PFG CustomerFirst
- Sysco Shop
- US Foods MOXē
- Bidfood Direct
- Brakes
- Transgourmet Webshop
- レストランボード
- OpenTable GuestCenter
- TheFork Manager
- Restaurant365
- 食べログ店舗管理画面
- Oracle MICROS Simphony Reporting & Analytics
- Toast Web
- Insights C3M
Other industries: Maybank2E, WEX Online, SIPP Online, Income Tax e-Filing Portal, Alloggiati Web, DGI Servicios en Línea.
Frequently asked questions
Not for restaurants directly. Zomato's POS Integration API covers menus, orders and outlets for POS vendors that meet its prerequisites, such as 500 onboarded restaurants or 50,000 monthly orders and 99.999% uptime. A restaurant uses it through such a POS, or works in the Restaurant Partner app and dashboard.
Yes, if you qualify. Zomato announced daily payouts in January 2024 for restaurant partners with 100 or fewer orders a month. They settle sales from three days earlier, cost nothing extra and are switched on in the Payout section of the Restaurant Partner app.
Because Zomato deducts its service fee and other charges. Its terms define Net Order Value as the Order Value less the service fee and any other amounts due to Zomato, so reconcile each order on Net Order Value.
In the Order history section of the Restaurant Partner app and in the Order Level tab of the Weekly Payout statement. You can opt out of Food Rescue in the Restaurant Partner app and dashboard.
No. Fous is an independent product. You use it with your own Zomato restaurant partner account, and a method reads and does only what that account can.
Put Zomato Restaurant Partner behind an API call
Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read next饿了么商家版배민셀프서비스Gordon OrderingMaybank2EHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Zomato Restaurant Partner (Eternal (Zomato)). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.