[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.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)

# Számlázz.hu API and MCP server

> Yes. Számlázz.hu has an official API called Számla Agent, in operation since 2010, that issues, reverses and queries invoices and records payments over HTTP with XML (checked 14 Oct 2026). It is an extra-cost add-on on every package, including the free one, it speaks XML only, and there is no official MCP server.

Hungarian online invoicing for small businesses: invoices and receipts that the service reports to the tax authority NAV, payment tracking, PDF copies and an invoice list.

## What is the Számlázz.hu API?

Cotlet's Számlázz.hu API exposes 8 endpoints for your own Számlázz.hu account: list invoices, get invoice, get invoice PDF, get NAV status, create invoice, cancel invoice, record payment and settle invoices. The list_invoices endpoint returns outgoing invoices with number, buyer, dates, gross amount and payment status, newest first. Each endpoint takes simple JSON inputs like invoice_number, comment or date and works both as an operation of the szamlazz_hu_read or szamlazz_hu_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm.md)
- **Endpoints:** 8 (4 read, 4 write)
- **Updated:** 2026-10-21

Yes. Cotlet is a hosted MCP server and REST API for Számlázz.hu with 8 endpoints (4 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Számlázz.hu have an official API?

Yes. Számlázz.hu has an official API called Számla Agent, in operation since 2010, that issues, reverses and queries invoices and records payments over HTTP with XML (checked 14 Oct 2026). It is an extra-cost add-on on every package, including the free one, it speaks XML only, and there is no official MCP server.

| Task | Számlázz.hu official | Cotlet |
|---|---|---|
| List and filter outgoing invoices | No: Agent looks up one invoice by number, order number or external ID | Yes |
| Read one invoice with items and payments | Yes: Query document (XML) | Yes |
| Download an invoice PDF | Yes: Query document (PDF) | Yes |
| Read the NAV submission status of an invoice | No: The documented query response has no NAV status | Yes |
| Issue an invoice | Yes: Regular, prepayment, final, corrective or pro forma, from XML | Yes |
| Cancel an invoice with a storno invoice | Yes | Yes |
| Record a payment on an invoice | Yes: Credit entry, partial payments allowed | Yes |
| Settle many invoices in one step | Partly: One XML request per invoice | Yes |

Sources: [Számla Agent: What is Számla Agent?](https://docs.szamlazz.hu/agent/basics/what-is), [Számla Agent: Authentication (API key)](https://docs.szamlazz.hu/agent/basics/authentication), [Számlázz.hu: Packages and prices](https://www.szamlazz.hu/csomagok-es-arak), [Számlázz.hu knowledge base: NAV](https://tudastar.szamlazz.hu/gyik/nav?hsLang=hu)

## For AI agents

```text
Yes. Számlázz.hu has an official API called Számla Agent, in operation since 2010, that issues, reverses and queries invoices and records payments over HTTP with XML (checked 14 Oct 2026). It is an extra-cost add-on on every package, including the free one, it speaks XML only, and there is no official MCP server.
Cotlet provides a hosted MCP server and REST API for Számlázz.hu: 8 tools (4 read, 4 write).
Access       Sign up at https://cotlet.dev/app/signup?app=szamlazz-hu, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    szamlazz_hu_read, szamlazz_hu_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/szamlazz-hu, each operation at its own route, e.g. POST /api/v1/szamlazz-hu/invoices/{invoice_number}/payments
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_invoices, get_invoice, get_invoice_pdf, get_nav_status, create_invoice, cancel_invoice, record_payment, settle_invoices
Confirm      create_invoice, cancel_invoice, record_payment, settle_invoices (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=szamlazz-hu, requests Számlázz.hu in the Cotlet console and creates an API key there.
2. The user signs in to Számlázz.hu once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Számlázz.hu for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Számlázz.hu server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Számlázz.hu in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Számlázz.hu only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Számlázz.hu login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Számlázz.hu's terms; Cotlet is not affiliated with Számlázz.hu.
```

## What can an AI agent do in Számlázz.hu?

Cotlet is best for Hungarian freelancers, agencies and small shops who issue and reconcile Számlázz.hu invoices every week and want an agent to do it without running or fixing a server.

- **Issue an invoice from a paid order** (runs: daily): "Issue a Számlázz.hu invoice for the order below: Blue Fern Studio Kft., tax number 12345678-2-42, 3 x Website retainer at 40,000 HUF net, 27% VAT, bank transfer, due in 8 days. Do not email the customer. Show me the totals first." → `create_invoice`, `get_invoice_pdf`
- **[Check whether invoices reached NAV](https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server/check-nav-submission-status.md)** (runs: daily): "List the invoices I issued in the last 7 days in Számlázz.hu. For each one, read the NAV submission status and tell me which are not Sikeres adatszolgáltatás, with the warning or reason if the app shows one." → `list_invoices`, `get_nav_status`
- **[Cancel an invoice with a storno](https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server/cancel-invoice-with-storno.md)**: "Cancel invoice ABC-2026-00131 in Számlázz.hu with a storno invoice. The reason is a duplicate order. Show me the invoice details and ask me before you cancel." → `get_invoice`, `cancel_invoice`
- **[Record invoice payments](https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server/record-invoice-payments.md)** (runs: daily): "Here are this morning's bank transfers: ABC-2026-00140 paid 127,000 HUF on 2026-10-13, ABC-2026-00142 paid 50,000 HUF on 2026-10-13. Record each as a payment in Számlázz.hu, and tell me what is still outstanding on each." → `get_invoice`, `record_payment`
- **Find unpaid and overdue invoices** (runs: weekly): "List my unpaid Számlázz.hu invoices past their due date, oldest first, with buyer, amount outstanding and days late. Fetch the PDF of the three oldest so I can attach them to reminders." → `list_invoices`, `get_invoice_pdf`

## Can Számlázz.hu automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Számlázz.hu connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to issue an invoice from a paid order, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as POST https://cotlet.dev/api/v1/szamlazz-hu/invoices. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/szamlazz-hu/invoices with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 8 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Számlázz.hu.

### list_invoices

Outgoing invoices with number, buyer, dates, gross amount and payment status, newest first. Access: read. REST: `GET /api/v1/szamlazz-hu/invoices`. MCP: `szamlazz_hu_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `issued_from` | date | no | Only invoices issued on or after this date. |
| `issued_to` | date | no | Only invoices issued on or before this date. |
| `buyer` | string | no | Part of the buyer name. |
| `payment_status` | string | no | Filter by payment status. 'paid', 'unpaid' or 'overdue'. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the invoices in Outgoing invoices, newest first, the way the list in the app shows them, and applies the same kind of filters as the Szűrő button. Payment status and the outstanding amount need a paid package and permission to manage payment status; without them those fields are left out. Returns up to 100 per page and a cursor for the next page.

Example response:

```json
{
  "invoices": [
    {
      "invoice_number": "ABC-2026-00142",
      "buyer": "Blue Fern Studio Kft.",
      "issue_date": "2026-10-09",
      "delivery_date": "2026-10-09",
      "due_date": "2026-10-17",
      "gross": 127000,
      "currency": "HUF",
      "payment_status": "unpaid",
      "outstanding": 127000
    },
    {
      "invoice_number": "ABC-2026-00140",
      "buyer": "Kovács és Társa Bt.",
      "issue_date": "2026-10-07",
      "delivery_date": "2026-10-07",
      "due_date": "2026-10-15",
      "gross": 127000,
      "currency": "HUF",
      "payment_status": "unpaid",
      "outstanding": 127000
    }
  ],
  "next_cursor": null
}
```

### get_invoice

One invoice with buyer, items, VAT, totals and recorded payments. Access: read. REST: `GET /api/v1/szamlazz-hu/invoices/{invoice_number}`. MCP: `szamlazz_hu_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | string | yes | Invoice number as shown in Outgoing invoices, from list_invoices. |

Returns one issued invoice: buyer with tax number, line items with quantity, unit net price, VAT rate and gross, totals per VAT rate, the payment method, the delivery and due dates and every payment recorded so far. Use it before cancel_invoice or record_payment so the agent works on the right document.

Example response:

```json
{
  "invoice_number": "ABC-2026-00142",
  "type": "invoice",
  "buyer": {
    "name": "Blue Fern Studio Kft.",
    "tax_number": "12345678-2-42",
    "email": "billing@bluefern.example"
  },
  "issue_date": "2026-10-09",
  "delivery_date": "2026-10-09",
  "due_date": "2026-10-17",
  "payment_method": "Átutalás",
  "currency": "HUF",
  "items": [
    {
      "name": "Website retainer",
      "quantity": 2,
      "unit": "db",
      "net_unit_price": 50000,
      "vat_rate": "27%",
      "net": 100000,
      "vat": 27000,
      "gross": 127000
    }
  ],
  "totals": {
    "net": 100000,
    "vat": 27000,
    "gross": 127000
  },
  "payments": [],
  "outstanding": 127000
}
```

### get_invoice_pdf

The invoice PDF as Számlázz.hu produced it, base64 encoded. Access: read. REST: `GET /api/v1/szamlazz-hu/invoices/{invoice_number}/pdf`. MCP: `szamlazz_hu_read → get_invoice_pdf`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | string | yes | Invoice number as shown in Outgoing invoices, from list_invoices. |

Returns the PDF copy of one issued invoice, base64 encoded, with its file name and size. Use it to attach the invoice to an email or save it to storage. It returns the document as issued; it does not change the invoice or send anything.

Example response:

```json
{
  "invoice_number": "ABC-2026-00142",
  "file_name": "ABC-2026-00142.pdf",
  "size_bytes": 48213,
  "content_base64": "JVBERi0xLjQKJc..."
}
```

### get_nav_status

The NAV submission status of one invoice, as the app shows it, with transaction ID and any warning. Access: read. REST: `GET /api/v1/szamlazz-hu/invoices/{invoice_number}/nav-status`. MCP: `szamlazz_hu_read → get_nav_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | string | yes | Invoice number as shown in Outgoing invoices, from list_invoices. |

Reads the Háttéradatok / NAV tab of the invoice. Returns the status text as the app shows it (Sikeres adatszolgáltatás, Sikeres, de figyelmeztetéssel befogadott adatszolgáltatás or Sikertelen vagy elutasított adatszolgáltatás), the transaction ID once a submission succeeded and the warning text if there is one. An invoice that Számlázz.hu has not submitted yet shows no transaction ID.

Example response:

```json
{
  "invoice_number": "ABC-2026-00147",
  "status": "Sikertelen vagy elutasított adatszolgáltatás",
  "transaction_id": null,
  "warning": null
}
```

### create_invoice

Issue a new invoice for a buyer with line items, payment method and dates. Access: write, asks the user first. REST: `POST /api/v1/szamlazz-hu/invoices`. MCP: `szamlazz_hu_write → create_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `buyer_name` | string | yes | Buyer name as it should print on the invoice. |
| `buyer_tax_number` | string | no | Buyer tax number, for business buyers. |
| `buyer_address` | string | yes | Postal code, city and street. |
| `buyer_email` | string | no | Email for the invoice copy; used only if send_email is true. |
| `items` | array | yes | Line items: name, quantity, unit, net_unit_price and vat_rate, for example "27%". |
| `payment_method` | string | yes | Payment method as the invoice form names it, for example 'Átutalás'. |
| `delivery_date` | date | yes | Delivery (teljesítés) date. |
| `due_date` | date | yes | Payment due date. |
| `currency` | string | no | Currency code such as 'HUF'. Default: HUF. |
| `comment` | string | no | Comment printed on the invoice. |
| `send_email` | boolean | no | Email the invoice to the buyer. Default: false. |

Issues a numbered invoice, which Számlázz.hu then reports to NAV. Returns the invoice number and the net, VAT and gross totals. The buyer gets the invoice by email only if send_email is true; the default is false. An issued invoice cannot be deleted, only cancelled with cancel_invoice. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_number": "ABC-2026-00148",
  "net": 120000,
  "vat": 32400,
  "gross": 152400,
  "currency": "HUF",
  "emailed": false
}
```

### cancel_invoice

Cancel an issued invoice by creating a storno invoice with a reason. Access: write, asks the user first. REST: `POST /api/v1/szamlazz-hu/invoices/{invoice_number}/cancel`. MCP: `szamlazz_hu_write → cancel_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | string | yes | Invoice number as shown in Outgoing invoices, from list_invoices. |
| `reason` | string | no | Reason for the storno, printed on the storno invoice. |

Creates a storno invoice for the original, with the same delivery date, and adds your reason to it. Returns the storno invoice number and the amounts. The storno is a legal document that goes to NAV, which accepts it only if the original was submitted successfully. A storno made by mistake is fixed in the app, not by this tool. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "storno_invoice_number": "ABC-2026-00149",
  "original_invoice_number": "ABC-2026-00131",
  "reason": "Duplicate order",
  "gross": -127000,
  "currency": "HUF"
}
```

### record_payment

Record a full or part payment on an invoice with credit date, amount and title. Access: write, asks the user first. REST: `POST /api/v1/szamlazz-hu/invoices/{invoice_number}/payments`. MCP: `szamlazz_hu_write → record_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | string | yes | Invoice number as shown in Outgoing invoices, from list_invoices. |
| `date` | date | yes | Credit date (jóváírás dátuma). |
| `amount` | number | yes | Amount in the invoice currency. |
| `title` | string | no | Payment type or title (jogcím), for example the way it was paid. |
| `comment` | string | no | Optional comment on the credit entry. |

Opens Pénzügyek / Befizetések for the invoice and adds one payment with the credit date, amount and title. A smaller amount is recorded as a part payment, and you can record several payments on one invoice. Returns the paid total and the amount still outstanding. Needs a paid package and permission to manage payment status. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_number": "ABC-2026-00142",
  "recorded": {
    "date": "2026-10-13",
    "amount": 50000,
    "title": "Bank transfer"
  },
  "paid_total": 50000,
  "outstanding": 77000,
  "currency": "HUF"
}
```

### settle_invoices

Mark several invoices as paid on one credit date. Access: write, asks the user first. REST: `POST /api/v1/szamlazz-hu/invoices/settle`. MCP: `szamlazz_hu_write → settle_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_numbers` | array | yes | Invoice numbers from list_invoices. |
| `date` | date | yes | Credit date for all of them. |

Does what Bizonylatok kiegyenlítése does in the invoice list: marks the selected invoices as settled and gives all of them the same credit date. The app cannot undo it, and a wrong date is corrected one invoice at a time. Returns the invoices that were settled. Needs a paid package and permission to manage payment status. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "settled": [
    "ABC-2026-00138",
    "ABC-2026-00139"
  ],
  "date": "2026-10-13"
}
```

## How do I connect Számlázz.hu to Claude Code, Codex or Cursor?

Connecting Számlázz.hu takes three steps: sign up, sign in to Számlázz.hu once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Számlázz.hu to your agent.

1. **Create an account** Sign up and add Számlázz.hu in the console. Your API key is there too.

2. **Sign in to Számlázz.hu in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Számlázz.hu there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Számlázz.hu tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Issue a Számlázz.hu invoice for the order below: Blue Fern Studio Kft., tax number 12345678-2-42, 3 x Website retainer at 40,000 HUF net, 27% VAT, bank transfer, due in 8 days. Do not email the customer. Show me the totals first.
```

### Call Számlázz.hu from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/szamlazz-hu with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/szamlazz-hu/invoices/ABC-2026-00142/payments \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-10-13","amount":50000,"title":"Bank transfer"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "invoice_number": "ABC-2026-00142",
  "recorded": {
    "date": "2026-10-13",
    "amount": 50000,
    "title": "Bank transfer"
  },
  "paid_total": 50000,
  "outstanding": 77000,
  "currency": "HUF"
}
```

## Why use Cotlet for Számlázz.hu?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Számlázz.hu yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Számlázz.hu changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Számlázz.hu to Cotlet?

Yes. You sign in to Számlázz.hu yourself, in your own Cloud Browser, and we never save your password. Your agents only get Számlázz.hu once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Számlázz.hu integration?**

No, Cotlet is independent of Számlázz.hu. Számlázz.hu's own API comes only with a paid plan. Cotlet works through your own Számlázz.hu account, the way you use Számlázz.hu in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Számlázz.hu in your console: your agents lose access at once and you stay signed in. Signing out of Számlázz.hu in the browser works too, and Reset browser deletes the whole profile.

## Is there a Számlázz.hu MCP server on GitHub?

The official route is the Számla Agent API. It works well, but it is an extra-cost add-on, it needs an Agent key from your account, and you build XML requests and host the code that sends them. Open-source MCP servers on top of it exist; they are usually maintained by one person and you run and fix them yourself. Cotlet hosts the same tools for you behind one key and one sign-in, and adds the invoice list and the NAV status that the API does not document.

|  | Official API or a GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Buy the Agent add-on, create an Agent key, write XML requests or install a server, add it to each MCP client | Sign up, sign in to Számlázz.hu once, add one MCP server or API key |
| When Számlázz.hu changes | You update your XML and code; a server breaks until its maintainer fixes it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Számlázz.hu access | An Agent key with the same permissions as every other key in the account, stored by you | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click; no key to paste |
| Invoice list and NAV status | Not in the documented operations: you look up one invoice at a time and check NAV in the web interface | list_invoices filters your outgoing invoices and get_nav_status reads the status the app shows |
| Upkeep | You keep XML, field order and error codes current and monitor it | Nothing to host or update |
| Where it runs | Your code or your computer | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Add-on fee from Számlázz.hu, plus your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Számlázz.hu changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Számlázz.hu API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Számlázz.hu API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Számlázz.hu account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Számlázz.hu yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Számlázz.hu only after you enable it. When Számlázz.hu signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Számlázz.hu, sign out of Számlázz.hu in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Számlázz.hu's terms:** You use your own Számlázz.hu account and stay responsible for following Számlázz.hu's terms. Cotlet is independent and not affiliated with Számlázz.hu. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Számlázz.hu in the console and press Request access. Then you create your API key and connect Számlázz.hu there.

**Do I need to be technical?**

No. You sign in to Számlázz.hu once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Számlázz.hu to Cotlet?**

Yes. You sign in to Számlázz.hu yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Számlázz.hu once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Számlázz.hu sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Számlázz.hu cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Számlázz.hu's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Számlázz.hu sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Számlázz.hu login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Számlázz.hu offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Which Számlázz.hu package do I need?**

Invoicing works on the free package, which lists unlimited paper-based invoices and receipts. Recording payment status is not available there, so record_payment and settle_invoices need #start or higher (checked 14 Oct 2026). The Számla Agent API is a separate extra-cost add-on, but Cotlet does not use it.

**Does the agent report invoices to NAV itself?**

No. Számlázz.hu reports each invoice to NAV on its own. get_nav_status only reads the status the app shows, and the app keeps retrying when NAV is slow.

**Can my agent post or send messages in Számlázz.hu without asking me?**

No. Every call to create_invoice, cancel_invoice, record_payment or settle_invoices waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Számlázz.hu API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/szamlazz-hu from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.