[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 eZee Optimus API

> eZee Optimus restaurant data can be read through Yanolja Cloud Solution's Connectivity API, with a production account on request. 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/ezee-optimus

eZee Optimus: Yanolja Cloud Solution's Connectivity API reads menus, orders and sales, with a production account on request (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your eZee Optimus 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 eZee Optimus session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=ezee-optimus)

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

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

curl Node.js Python

curl

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

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/open-orders";
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-20" }),
});
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/open-orders",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-20"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"order": "D-1042",
"type": "dine-in",
"table": "Table 4",
"opened": "19:40",
"amount": 86.4
},
{
"order": "T-0318",
"type": "takeaway",
"table": "",
"opened": "20:10",
"amount": 32.5
}
]
}
```

01 Build

## How do you build an eZee Optimus endpoint with Cotlet?

1. 01  
app.ipos247.com  
Signed in  
### Sign in to eZee Optimus in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List the dine-in and takeaway orders still open today, with the table, time and amount.  
### Do the job once with your agent.  
For example: "List the dine-in and takeaway orders still open today, with the table, time and amount."
3. 03  
Save endpoint  
Name  
open-orders  
Input  
date  
Returns  
order, type, table, opened, amount  
### 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/open-orders  
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 eZee Optimus session.

02 Endpoints

## Example endpoints you could build for eZee Optimus

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

- POST `/api/v1/custom/open-orders`  
### Open orders  
Order, type, table, time opened and amount of each open order
- POST `/api/v1/custom/sales-by-payment`  
### Sales by payment type  
Cash, card and other payments for a day or period
- POST `/api/v1/custom/top-items`  
### Best-selling items  
Items sold most in a period, with quantity and amount
- POST `/api/v1/custom/discounts-given`  
### Discounts given  
Bills with a discount, who gave it and how much
- POST `/api/v1/custom/takeaway-order` writes  
### Enter a takeaway order  
A takeaway order with its items and pickup time
- 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/open-orders" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-20"}'
```

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

Response · 200 OK

```
{
"data": [
{
"order": "D-1042",
"type": "dine-in",
"table": "Table 4",
"opened": "19:40",
"amount": 86.4
},
{
"order": "T-0318",
"type": "takeaway",
"table": "",
"opened": "20:10",
"amount": 32.5
}
]
}
```

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 eZee Optimus endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A closing report at 10 pm.  
Open orders and the day's sales by payment type, sent to the owner.
- Voice agent endpoint takeaway order  
### Phone orders from a voice agent.  
An AI phone agent enters each pickup order as a takeaway ticket.
- Schedule endpoint Google Sheets  
### Weekly sales in a sheet.  
Best-selling items and discounts pulled into Google Sheets.
- Website form endpoint takeaway order  
### Online orders from your website.  
A form on your site sends each pickup order into eZee Optimus.

04 Access

## What can an endpoint see and change?

An endpoint works in your own eZee Optimus session, so it can read and change only what your eZee Optimus 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 entering a takeaway order, 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/takeaway-order

would POST app.ipos247.com/... enter a takeaway order for 19:00 pickup

`takeaway-order`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does eZee Optimus have an official API?

Yanolja Cloud Solution's Connectivity API has an F&B section for eZee Optimus that retrieves the menu, orders, sales, purchases, outlets and financial accounts. Credentials are given to you, and "Contact us to get production account information." No webhooks for eZee Optimus were found (checked 20 Nov 2026). The full picture with sources: [Does eZee Optimus have an API or MCP server?](https://cotlet.dev/api-status/ezee-optimus.md)

Want ChatGPT or Claude to work in eZee Optimus instead of code? See the [eZee Optimus MCP server](https://cotlet.dev/integrations/ezee-optimus-api-mcp-server.md).

1/3

Official API

On request

[Full API & MCP report](https://cotlet.dev/api-status/ezee-optimus.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.

## eZee Optimus API with Cotlet: questions

### Is this an official eZee Optimus API?

No. Cotlet is independent and not affiliated with eZee Optimus. The endpoints you build run in your own signed-in eZee Optimus 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 eZee Optimus changes its screens?

An endpoint works while eZee Optimus works the way it did when you built it. If eZee Optimus 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 eZee Optimus 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=ezee-optimus)

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.
