[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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)

# Create your own Restroworks API

> Restroworks's API comes with every account, but access goes through a request and its account team. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/restroworks-restaurant-pos

Restroworks includes API access in every account, with sandbox keys on request and its account team for production (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Restroworks account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Restroworks session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=restroworks-restaurant-pos)

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Restroworks. Restroworks is a trademark of its owner. If Restroworks's own integrations cover what you need, use them first.

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/sales-by-outlet" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-19"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/sales-by-outlet";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ date: "2026-11-19" }),
});
const { data } = await res.json();
```

Python

```
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/sales-by-outlet",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-19"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"outlet": "Downtown",
"net_sales": 4860,
"orders": 212,
"voids": 3,
"discounts": 140
},
{
"outlet": "Uptown",
"net_sales": 5310,
"orders": 236,
"voids": 1,
"discounts": 330
}
]
}
```

01 Build

## How do you build a Restroworks endpoint with Cotlet?

1. 01  
www.restroworks.com  
Signed in  
### Sign in to Restroworks in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List the sales for each outlet on a date, with orders, voids and discounts.  
### Do the job once with your agent.  
For example: "List the sales for each outlet on a date, with orders, voids and discounts."
3. 03  
Save endpoint  
Name  
sales-by-outlet  
Input  
date  
Returns  
outlet, net\_sales, orders, voids, discounts  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a date or an outlet, and the fields it returns.
4. 04  
$ POST /api/v1/custom/sales-by-outlet  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in Restroworks session.

02 Endpoints

## Example endpoints you could build for Restroworks

Cotlet ships no fixed list of Restroworks endpoints. You decide which endpoints you build and what each one returns.

- POST `/api/v1/custom/sales-by-outlet`  
### Sales by outlet  
Net sales, orders, voids and discounts for each outlet on a date
- POST `/api/v1/custom/items-below-par`  
### Items below par  
Item, stock, par level and usual supplier at an outlet
- POST `/api/v1/custom/top-items`  
### Top items for a period  
Items by quantity and sales, by outlet
- POST `/api/v1/custom/reservations-for-day`  
### Reservations for a day  
Time, guest, party size and table for each reservation
- POST `/api/v1/custom/mark-item-unavailable` writes  
### Mark an item unavailable  
The item you name switched off at an outlet, with the time it covers
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/sales-by-outlet" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-19"}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"outlet": "Downtown",
"net_sales": 4860,
"orders": 212,
"voids": 3,
"discounts": 140
},
{
"outlet": "Uptown",
"net_sales": 5310,
"orders": 236,
"voids": 1,
"discounts": 330
}
]
}
```

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

## What can you use your Restroworks endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A morning sales report in n8n or Make.  
Yesterday's sales by outlet, sent to Slack or email before service.
- Schedule endpoint Google Sheets  
### A stock sheet for the buyer.  
Items below par at every outlet, pulled each morning into Google Sheets.
- Schedule endpoint Dashboard  
### A dashboard for the owners.  
Top items and sales by outlet pulled into Looker Studio or your own tool.
- Chat agent endpoint stock  
### Your own ordering assistant.  
A chat agent that checks stock before it promises a dish for a large order.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Restroworks session, so it can read and change only what your Restroworks login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as marking an item unavailable, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

DRY RUN · nothing sent

$ POST /api/v1/custom/mark-item-unavailable

would POST www.restroworks.com/... mark lamb biryani unavailable at Downtown

`mark-item-unavailable`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Restroworks have an official API?

Restroworks says API access is part of every account, with documentation, sandbox keys on request and the account team for the step to production, and that webhooks send order, payment, menu and inventory updates (checked 20 Nov 2026). No Restroworks MCP server was found. The full picture with sources: [Does Restroworks have an API or MCP server?](https://cotlet.dev/api-status/restroworks-restaurant-pos.md)

Want ChatGPT or Claude to work in Restroworks instead of code? See the [Restroworks MCP server](https://cotlet.dev/integrations/restroworks-restaurant-pos-api-mcp-server.md).

1/3

Official API

On request

[Full API & MCP report](https://cotlet.dev/api-status/restroworks-restaurant-pos.md)

06 Pricing

## What does it cost?

per successful call

 10 credits

when a call fails

 0

in the smallest pack

≈ 500 calls

free trial, no card

 7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

## Restroworks API with Cotlet: questions

### Is this an official Restroworks API?

No. Cotlet is independent and not affiliated with Restroworks. The endpoints you build run in your own signed-in Restroworks account.

### Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

### What happens when Restroworks changes its screens?

An endpoint works while Restroworks works the way it did when you built it. If Restroworks changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

### How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

POST /api/v1/custom/<name>

## Build your first Restroworks endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=restroworks-restaurant-pos)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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.
