[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Petpooja API and MCP server: Let your AI agent run the Petpooja back office. > Petpooja publishes no API documentation or API keys page for restaurants and has no MCP server (checked 31 Oct 2026). Its integrations page asks partners to contact Petpooja to connect their service. Cotlet runs 11 Petpooja tools hosted, over MCP for agents and REST for scripts, in your own back office login. Sales, menu items, stock and online orders across your Petpooja outlets. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST. [MCP setup](https://cotlet.dev/integrations/petpooja-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/petpooja-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Petpooja - Page: https://cotlet.dev/integrations/petpooja-api-mcp-server ## What can you automate in Petpooja? - Read sales and tax per outlet - Switch off an item that ran out - Check Swiggy and Zomato payouts - Review cancelled and discounted bills - Find raw materials running low - Change the price of a dish ## Does Petpooja have an MCP server or an API? - The pricing page lists Core, Growth and Scale with feature lists, no price and no API line. Every plan has a "Book A Demo" button. - The integrations page says "Become our integration partner" and has a "Contact us" button. developer.petpooja.com and api.petpooja.com show nothing. - Zapier and n8n have no Petpooja app; both pages answered 404 on 31 Oct 2026. | What you need | Partner route | Back office by hand | Cotlet | |---|---|---|---| | Sales and tax for every outlet | No public docs | Yes, one outlet at a time | Yes | | Swiggy and Zomato payout check | No public docs | Yes, in the reconciliation report | Yes | | Switch an item off online | No public docs | Yes | Yes | | Change a price | No public docs | Yes | Yes, after your OK | | Low stock and open purchase orders | No public docs | Yes | Yes | | Who can get it | Partners Petpooja agrees to | Any user with the rights | Any user with the rights | Checked 31 Oct 2026. Sources: [Petpooja Integrations](https://www.petpooja.com/poss/restaurant-integrations), [Petpooja Pricing](https://www.petpooja.com/pricing), [Petpooja Reports and Analytics](https://www.petpooja.com/poss/reports-and-analytics), [Petpooja Online Order Management](https://www.petpooja.com/poss/online-order-management-software) ## How does Cotlet connect to Petpooja? 1. **Sign in to Petpooja.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your Petpooja password, and no price change or outlet switch goes through until you approve it. ## Connect Petpooja to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Sign in to Petpooja once.** Create a Cotlet account, open Petpooja in its Cloud Browser, sign in at billing.petpooja.com and press Enable for agents. 2. **Add the Cotlet address.** Put https://cotlet.dev/mcp/v1 in the MCP server or connector list of your agent. 3. **Allow the connection.** Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts take an API key from the console. Petpooja sits on `https://cotlet.dev/mcp/v1` with the other apps of your Cotlet account. If you turn Petpooja on after connecting, refresh the connector and its tools appear. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-petpooja \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-petpooja": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-petpooja] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: petpooja_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: petpooja_write ``` ## How to use the Petpooja REST API ### Create your Cotlet API key Create a Cotlet API key with access to Petpooja and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect Petpooja in Cotlet and enable it for agents. Account access: Your own Petpooja login at billing.petpooja.com (an owner or a user whose rights cover reports, menu and inventory). ### Make your first Petpooja API request REST: ``` curl "https://cotlet.dev/api/v1/petpooja/outlets/out_101/sales-report?from=2026-10-29&to=2026-10-30" \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read the sales report and apply the operation limits A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "petpooja", "tool": "get_sales_report", "result": { "outlet_id": "out_101", "currency": "INR", "days": [ { "date": "2026-10-29", "bills": 412, "gross_sales": 61200, "discounts": 2800, "tax": 2920, "net_sales": 58400 }, { "date": "2026-10-30", "bills": 389, "gross_sales": 55600, "discounts": 2100, "tax": 2675, "net_sales": 53500 } ], "totals": { "bills": 801, "gross_sales": 116800, "discounts": 4900, "tax": 5595, "net_sales": 111900 } } } ``` Returns one row per day for one outlet: bills, gross sales, discounts, tax and net sales, plus totals, in the outlet's currency. Net sales are gross sales minus discounts. Your Petpooja login needs the rights that open the reports for that outlet. Replace `out_101` with an `outlet_id` from `list_outlets`. Without `from` and `to` the call returns yesterday. The report has no cursor, so request one range per call and compare the figures of a day you already stored, because bills can be corrected after the day closes. ### Petpooja workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Read yesterday's sales for each outlet and send the totals to your own chat or sheet. Use `get_sales_report` in your configured business report. | | Make | HTTP > Make a request | List raw materials at or below their low stock level for an outlet. Use `list_raw_materials` in your configured business report. | | Python or Node.js | REST API | Check the Swiggy and Zomato payout for a week against what the platform pays. Use `get_online_order_reconciliation` in your configured business report. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Petpooja; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/petpooja-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Petpooja API endpoints and MCP tools ### Outlets and reports One outlet per call, except list_outlets. Your login needs the rights that open the reports. - **List outlets** (`list_outlets`, read): Outlets of your account with name, city and whether online ordering is on. - **Get sales report** (`get_sales_report`, read): Day by day sales, discounts and tax for one outlet. - **List bill exceptions** (`list_bill_exceptions`, read): Cancelled, discounted or modified bills and cash drawer operations, with who did them. - **Get online order reconciliation** (`get_online_order_reconciliation`, read): Per platform: orders, order value, commission, charges, taxes and expected payout. ### Menu and online ordering Items come 100 per page. A switched off item stays off until you switch it on. A price change moves to the connected aggregators, as it does by hand. - **List menu items** (`list_menu_items`, read): Menu items of an outlet with category, price and whether they are on for online orders. - **Set item availability** (`set_item_availability`, write): Switch a menu item on or off for online orders. - **Update item price** (`update_item_price`, write, asks first): Change the price of a menu item. - **Set outlet online status** (`set_outlet_online_status`, write, asks first): Switch online ordering for a whole outlet on or off. ### Stock and purchasing Read only. Needs the Inventory module on your plan. - **List raw materials** (`list_raw_materials`, read): Raw materials of an outlet with current stock and the low stock level. - **List purchase orders** (`list_purchase_orders`, read): Purchase orders of an outlet with supplier, status and item count. ### Customers Read only, from the CRM. Contact details of your guests, so keep the agent's login to the outlets that need it. - **List customers** (`list_customers`, read): CRM customers with visits, reward points and last visit. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/petpooja-api-mcp-server#tools ## Who can see my Petpooja session, and how do I revoke it? - **What we store.** Your signed-in back office profile, AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 11 Petpooja tools. No cookie, no partner credentials. - **What the session sees.** The outlets your login opens: sales, menu, stock, guest contact details. - **What no tool touches.** Billing, payments, subscriptions, staff rights and the cash drawer. - **If Petpooja asks to verify.** A code or a new sign-in goes through you. We never type it. - **How to cut access.** Disable for agents, reset the browser, or remove the user in Petpooja. Petpooja sets rights per user. Give the agent a login that opens only the outlets and screens it needs, so a mistake stays there. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). We have no SOC 2 report or third-party pentest yet. ## Is it against Petpooja's terms? Account safety > You represent and warrant that Your Content was not submitted via the use of any automated process such as a script bot > > [Petpooja Terms and Conditions, Your Content, 31 Oct 2026](https://www.petpooja.com/terms-and-conditions) > Petpooja reserves the right to suspend or cease providing any services relating to the apps published by it, with or without notice > > [Petpooja Terms and Conditions, Service Suspension, 31 Oct 2026](https://www.petpooja.com/terms-and-conditions) The first sentence sits in the clause on content you submit, and the terms do not mention AI agents, scraping or browser automation. Cotlet uses no partner keys: it works in the back office under your login, the way you would. Petpooja could still read an agent as an automated process, so read the [terms](https://www.petpooja.com/terms-and-conditions) before you connect one. We found no public case of an account suspended for automation. How we keep your account looking like you: - Your own login, signed in by you - One Cloud Browser with its own IP and cookies - Price changes and outlet switches wait for your OK - No tool creates bills, takes payments or changes staff rights - If Petpooja objects, we pause the Petpooja tools for everyone within 24 h > Your staff use the same account for billing during service. Let the agent read reports and change the menu before you open or after you close, and leave the rush to the counter. ## What happens when Petpooja changes? - **12 h** between tests of the Petpooja reads and item switches - **24 h** between tests of price and outlet changes customers would notice - **$0** for a call to a Petpooja tool paused for repair Petpooja updates its back office on its own schedule, and screens will move. When one does, the repair is ours and a scheduled run keeps its prompt. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the menu.** The items of the outlet and category you named, with today's prices. 2. **Proposes new prices.** One line per item, old price and new price. 3. **Waits for your OK.** Each price change shows up in your Cotlet console first. 4. **Reports back.** Changed items, their new prices, and the ones left alone. | Action | Undo | |---|---| | Switch an item off | Yes, switch it on with the same tool | | Change a price | Set the old price again with update_item_price | | Switch an outlet off | Switch it on again; orders missed meanwhile stay missed | | Switch an outlet on | Switch it off again; orders may already have come in | 2 of 11 tools ask first: update_item_price and set_outlet_online_status. set_item_availability runs at once, because switching off a dish messages nobody and one more call switches it on again. Switch the wait off per tool for a scheduled run. > An outlet left switched off is an easy reason for a quiet evening. When online orders stop, have the agent run list_outlets first. MCP call: ``` { "name": "update_item_price", "arguments": { "outlet_id": "out_101", "item_id": "itm_2207", "price": 70 } } ``` REST: ``` curl -X PATCH https://cotlet.dev/api/v1/petpooja/outlets/out_101/items/itm_2207/price \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"price":70}' ``` Response: ``` { "outlet_id": "out_101", "item_id": "itm_2207", "name": "Filter Coffee", "old_price": 60, "price": 70, "currency": "INR" } ``` Scripts reach the same tools over REST at `/api/v1/petpooja`, with the same key and price, so a cron job can pull yesterday's sales every morning. A call to an item or outlet that does not exist fails and costs nothing. The tools table lists the REST path of each tool. ## How much does the Petpooja MCP server cost? **About $27 a month** for two outlets, 4,680 credits. Your Petpooja plan is billed by Petpooja as before. | Job | Calls | Credits | |---|---|---| | Daily sales for 2 outlets | 3 × 30 | 900 | | Low stock round, switch items off | 6 × 30 | 1,800 | | Swiggy and Zomato payouts, weekly | 2 × 4 | 80 | | Cancelled and discounted bills, weekly | 3 × 4 | 120 | | Price changes after your OK | 6 × 2 | 120 | | Open purchase orders, weekly | 4 × 4 | 160 | | Cloud Browser, 30 days | | 1,500 | | Total | | 4,680 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - No partner agreement or API keys needed The month is our example: Petpooja publishes no count of outlets per account, so we took two. The daily stock round is the biggest line; an owner who reads one report a day pays mostly for the browser. Dollars at the $29 pack rate. ## Petpooja MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [Petpooja integration partners](https://www.petpooja.com/poss/restaurant-integrations) | Services that Petpooja connects to its POS, listed on its integrations page. | Petpooja decides who gets in. There is no public documentation and no sign-up for owners. | | [itsmerk2004/petpooja-sales-data](https://github.com/itsmerk2004/petpooja-sales-data) | A Python script that fetches sales records for a date range into SQLite. | Needs an app key, app secret and access token. Reads sales only, 0 stars, last push 23 Oct 2026. | | [aleefakram/hookpooja](https://github.com/aleefakram/hookpooja) | A webhook server that pushes Petpooja JSON payloads to a Power BI dataset. | Receives data Petpooja sends. It cannot read reports, change a menu or switch an item off. 0 stars, last push May 2025. | | Zapier and n8n | No Petpooja app in either: both pages answered 404 on 31 Oct 2026. | Nothing to connect to. Make answered 403, so its status is unknown. | | MCP servers on GitHub | None. A search for "petpooja mcp" returned 0 repositories on 31 Oct 2026. | No server to install. | A software company that wants its product inside Petpooja should ask Petpooja about the partner route. A finance team with sales credentials can script the sales endpoint. Cotlet is for the owner or manager who wants an agent to do the back office work of their own outlets. ## Who runs Cotlet Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273). It has worked since 2019 and was founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Petpooja tools to contact@cotlet.dev. ## Petpooja API and MCP: questions ### How do I get access? Make a free account at https://cotlet.dev, open Petpooja under Integrations in the console and sign in to the Petpooja back office in its Cloud Browser. The trial starts with your first app, and no card is asked. ### How do I connect Petpooja to ChatGPT or Claude? Sign up at cotlet.dev, log in to Petpooja once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Petpooja account through Cotlet, in their phone apps too. ### What can ChatGPT do in Petpooja? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Petpooja: send yesterday\; switch off items that ran out of stock; check Swiggy and Zomato payouts. You ask in plain words, and anything that reaches other people waits for your OK first. ### Which Petpooja plan or user rights does the agent need? The tools can only do what your login can do. Petpooja's pricing page lists the Inventory Module, Menu management and 80+ reports among its plan features and shows no price (checked 31 Oct 2026), so ask Petpooja which plan includes each module. Petpooja also sets rights per user, so give the agent a login that covers only the outlets and screens it needs. ### How do I sign in to Petpooja for the agent? Petpooja's sign-in page at billing.petpooja.com asks for a phone number with a country code, or Sign in with Google (checked 31 Oct 2026). You sign in yourself in your Cloud Browser and complete any check Petpooja sends. Cotlet never types or stores it. ### Does a change reach Swiggy and Zomato? Petpooja says menu changes, prices and item switches in its POS update across the aggregators connected to your outlet (online order management page, checked 31 Oct 2026). Cotlet makes the change in Petpooja the way you would, so the same sync applies. The agent cannot see the Swiggy or Zomato screens. ### Does Petpooja have webhooks? None for owners are documented. To catch changes, run your agent on a schedule, for example get_sales_report every morning or list_raw_materials with low_stock_only every few hours. ### Does it work with my other Petpooja add-ons? The tools cover reports, menu, stock, purchase orders and the CRM. Kitchen display, captain ordering, the restaurant website and loyalty add-ons have no tool. ### Is the MCP server different from the REST API? Only the way in differs. Both carry the same 11 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and cron jobs use REST. ### Is Cotlet affiliated with Petpooja? No. Cotlet is independent and not affiliated with Prayosha Food Services Private Limited or Petpooja. ### Can I use the Petpooja API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.