[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)

# e-conomic API and MCP server

> Yes, e-conomic has a full REST API with customers, draft and booked invoices, invoice PDFs and journal vouchers (checked 14 Oct 2026), but you get it through a developer agreement: you create an app that holds an AppSecretToken, and each accounting user grants it access with an AgreementGrantToken. The developer docs list no official MCP server.

Danish cloud accounting software from Visma for small businesses and accountants: customers, products, draft and booked invoices, and journals with vouchers in one agreement.

## What is the e-conomic API?

Cotlet's e-conomic API exposes 11 endpoints for your own e-conomic account: list customers, get customer, list products, list draft invoices, list unpaid invoices, get invoice PDF, list journal entries, create customer, create draft invoice, book invoice and create finance voucher. The list_customers endpoint returns customers in the register with number, name, currency and payment terms. Each endpoint takes simple JSON inputs like limit, cursor or customer_number and works both as an operation of the e_conomic_read or e_conomic_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:** 11 (7 read, 4 write)
- **Updated:** 2026-10-21

Yes, e-conomic has a full REST API with customers, draft and booked invoices, invoice PDFs and journal vouchers (checked 14 Oct 2026), but you get it through a developer agreement: you create an app that holds an AppSecretToken, and each accounting user grants it access with an AgreementGrantToken. Cotlet is a hosted MCP server and REST API for e-conomic with 11 endpoints (7 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does e-conomic have an official API?

Yes, e-conomic has a full REST API with customers, draft and booked invoices, invoice PDFs and journal vouchers (checked 14 Oct 2026), but you get it through a developer agreement: you create an app that holds an AppSecretToken, and each accounting user grants it access with an AgreementGrantToken. The developer docs list no official MCP server.

| Task | e-conomic official | Cotlet |
|---|---|---|
| List and create customers | Yes: GET and POST /customers; currency, customer group, name, payment terms and VAT zone are required | Yes |
| Create draft invoices | Yes: POST /invoices/drafts; the draft is editable and not booked | Yes |
| Book an invoice and send it | Yes: POST /invoices/booked with sendBy none, Email or EAN | Yes |
| List unpaid, overdue and not-due invoices | Yes: Invoice collections under /invoices | Yes |
| Download an invoice PDF | Yes: GET /invoices/booked/{number}/pdf | Yes |
| Create finance vouchers in a journal | Yes: POST /journals/{journal}/vouchers, bulk creation supported | Yes |
| Read journal entries | Yes: GET /journals/{journal}/entries | Yes |
| Use it from an AI agent with one key | No: No MCP server and no single key; you hold two tokens per agreement | Yes |

Sources: [e-conomic Developer: Connect to the REST API](https://www.e-conomic.com/developer/connect), [e-conomic Developer: overview](https://www.e-conomic.com/developer), [e-conomic REST API documentation](https://restdocs.e-conomic.com/), [e-conomic support: booking and sending sales invoices through the API](https://www.e-conomic.dk/support/artikler/booking-and-sending-sales-invoices-through-the-e-conomic-api)

## For AI agents

```text
Yes, e-conomic has a full REST API with customers, draft and booked invoices, invoice PDFs and journal vouchers (checked 14 Oct 2026), but you get it through a developer agreement: you create an app that holds an AppSecretToken, and each accounting user grants it access with an AgreementGrantToken. The developer docs list no official MCP server.
Cotlet provides a hosted MCP server and REST API for e-conomic: 11 tools (7 read, 4 write).
Access       Sign up at https://cotlet.dev/app/signup?app=e-conomic, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    e_conomic_read, e_conomic_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/e-conomic, each operation at its own route, e.g. POST /api/v1/e-conomic/customers/{customer_number}/draft-invoices
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_customers, get_customer, list_products, list_draft_invoices, list_unpaid_invoices, get_invoice_pdf, list_journal_entries, create_customer, create_draft_invoice, book_invoice, create_finance_voucher
Confirm      book_invoice, create_finance_voucher (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/e-conomic-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=e-conomic, requests e-conomic in the Cotlet console and creates an API key there.
2. The user signs in to e-conomic once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables e-conomic 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 e-conomic 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 e-conomic 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 e-conomic 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 e-conomic 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 e-conomic's terms; Cotlet is not affiliated with e-conomic.
```

## What can an AI agent do in e-conomic?

Cotlet is best for Danish and Nordic small businesses and bookkeepers who want an AI agent to draft, book and send e-conomic invoices without running or fixing a server.

- **[Create draft invoices from a billing list](https://cotlet.dev/integrations/e-conomic-api-mcp-server/create-draft-invoices-from-a-list.md)**: "Here is this month's billing list. For each customer, create a draft invoice in e-conomic with the hours and rate I gave. Create customers that do not exist yet. Do not book anything." → `list_customers`, `create_customer`, `list_products`, `create_draft_invoice`
- **[Book drafts and send invoices to customers](https://cotlet.dev/integrations/e-conomic-api-mcp-server/book-and-send-draft-invoices.md)** (runs: weekly): "List my draft invoices in e-conomic. For each draft that has a customer, lines and a date this month, book it and send it by email. Leave drafts with a missing line or a zero total for me." → `list_draft_invoices`, `book_invoice`
- **List unpaid and overdue invoices** (runs: weekly): "Every Monday list overdue invoices in e-conomic with customer, amount and days overdue, largest first, and attach the PDF links." → `list_unpaid_invoices`, `get_customer`, `get_invoice_pdf`
- **[Post recurring bookkeeping vouchers](https://cotlet.dev/integrations/e-conomic-api-mcp-server/post-recurring-vouchers.md)** (runs: weekly): "Post these monthly vouchers to journal 1 in e-conomic with the accounts, amounts and text I gave, and list the voucher numbers." → `list_journal_entries`, `create_finance_voucher`
- **Add customers from a sign-up list**: "Check these new clients against e-conomic by name and create any that are missing with payment terms 2 and our standard customer group." → `list_customers`, `create_customer`

## Can e-conomic automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a e-conomic 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 book drafts and send invoices to customers, 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 GET https://cotlet.dev/api/v1/e-conomic/draft-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 | GET https://cotlet.dev/api/v1/e-conomic/draft-invoices with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 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 e-conomic.

### list_customers

Customers in the register with number, name, currency and payment terms. Access: read. REST: `GET /api/v1/e-conomic/customers`. MCP: `e_conomic_read → list_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | no | Only customers whose name contains this text. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns customers in customer-number order, with currency, customer group, payment terms and VAT zone. Filter by name to find a match before creating a new one. Large registers come in pages; pass the cursor for the next page.

Example response:

```json
{
  "customers": [
    {
      "customer_number": 14,
      "name": "Nordlys ApS",
      "currency": "DKK",
      "payment_terms_number": 2,
      "vat_zone_number": 1,
      "email": "ap@nordlys.example"
    },
    {
      "customer_number": 15,
      "name": "Havn Design",
      "currency": "DKK",
      "payment_terms_number": 2,
      "vat_zone_number": 1,
      "email": "faktura@havn.example"
    }
  ],
  "next_cursor": null
}
```

### get_customer

One customer with contact data, terms and balance. Access: read. REST: `GET /api/v1/e-conomic/customers/{customer_number}`. MCP: `e_conomic_read → get_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_number` | integer | yes | Customer number from list_customers or create_customer. |

Returns the customer record with address, email, currency, payment terms and VAT zone. Use it before drafting an invoice to see the terms the draft will carry.

Example response:

```json
{
  "customer_number": 14,
  "name": "Nordlys ApS",
  "currency": "DKK",
  "payment_terms_number": 2,
  "vat_zone_number": 1,
  "email": "ap@nordlys.example",
  "city": "Aarhus"
}
```

### list_products

Products with number, name and sales price. Access: read. REST: `GET /api/v1/e-conomic/products`. MCP: `e_conomic_read → list_products`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | no | Only products whose name contains this text. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns products by product number. Use a product number on an invoice line so the line takes its name and price from the register.

Example response:

```json
{
  "products": [
    {
      "product_number": "100",
      "name": "Consulting hour",
      "sales_price": 95
    },
    {
      "product_number": "200",
      "name": "Workshop day",
      "sales_price": 250
    }
  ],
  "next_cursor": null
}
```

### list_draft_invoices

Draft invoices with customer, date, line count and totals. Access: read. REST: `GET /api/v1/e-conomic/draft-invoices`. MCP: `e_conomic_read → list_draft_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_number` | integer | no | Only drafts for this customer. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns draft invoices that are not booked yet, newest first. Each draft shows its customer, date, number of lines and totals, so you can see which are complete. Drafts are still editable.

Example response:

```json
{
  "drafts": [
    {
      "draft_invoice_number": 118,
      "customer_number": 14,
      "customer_name": "Nordlys ApS",
      "date": "2026-10-31",
      "lines": 2,
      "total_net": 1200,
      "currency": "DKK"
    },
    {
      "draft_invoice_number": 121,
      "customer_number": 15,
      "customer_name": "Havn Design",
      "date": "2026-10-31",
      "lines": 0,
      "total_net": 0,
      "currency": "DKK"
    }
  ],
  "next_cursor": null
}
```

### list_unpaid_invoices

Booked invoices with a remaining balance, with due date and days overdue. Access: read. REST: `GET /api/v1/e-conomic/unpaid-invoices`. MCP: `e_conomic_read → list_unpaid_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | unpaid, overdue or not_due. Default: unpaid. |
| `customer_number` | integer | no | Only invoices for this customer. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns booked invoices that still have an unpaid amount. Choose all unpaid, only overdue or only not yet due. Each row has the remaining amount, due date and a PDF link for get_invoice_pdf. Sorted by due date, oldest first.

Example response:

```json
{
  "invoices": [
    {
      "invoice_number": 1038,
      "customer_number": 14,
      "customer_name": "Nordlys ApS",
      "remaining": 1500,
      "currency": "DKK",
      "due_date": "2026-09-30",
      "days_overdue": 14
    },
    {
      "invoice_number": 1040,
      "customer_number": 15,
      "customer_name": "Havn Design",
      "remaining": 625,
      "currency": "DKK",
      "due_date": "2026-10-20",
      "days_overdue": 0
    }
  ],
  "next_cursor": null
}
```

### get_invoice_pdf

Download link for the PDF of a booked invoice. Access: read. REST: `GET /api/v1/e-conomic/invoices/{invoice_number}/pdf`. MCP: `e_conomic_read → get_invoice_pdf`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | integer | yes | Booked invoice number from list_unpaid_invoices. |

Returns the PDF of a booked invoice as a download link that works for a short time. The PDF is the one e-conomic produces for the invoice, with its layout.

Example response:

```json
{
  "invoice_number": 1038,
  "pdf_url": "https://files.cotlet.dev/e-conomic/invoice-1038.pdf",
  "expires_in_seconds": 900
}
```

### list_journal_entries

Entries in a journal, filtered by type, text or voucher number. Access: read. REST: `GET /api/v1/e-conomic/journal-entries`. MCP: `e_conomic_read → list_journal_entries`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `journal_number` | integer | yes | Journal number, e.g. 1. |
| `entry_type` | string | no | financeVoucher, supplierInvoice, supplierPayment, customerPayment or manualCustomerInvoice. |
| `text` | string | no | Only entries whose text contains this. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns entries booked in a journal with account, contra account, amount, date, text and voucher number. Use it before posting to see whether a voucher already exists.

Example response:

```json
{
  "entries": [
    {
      "voucher_number": 310,
      "entry_type": "financeVoucher",
      "account_number": 7200,
      "contra_account_number": 1920,
      "amount": 4500,
      "date": "2026-09-30",
      "text": "Office rent September"
    }
  ],
  "next_cursor": null
}
```

### create_customer

Add a customer to the register. Access: write. REST: `POST /api/v1/e-conomic/customer-groups/{customer_group_number}/customers`. MCP: `e_conomic_write → create_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Customer name. |
| `currency` | string | yes | Currency code, e.g. DKK. |
| `customer_group_number` | integer | yes | Customer group number from the register. |
| `payment_terms_number` | integer | yes | Payment terms number from the register. |
| `vat_zone_number` | integer | yes | VAT zone number from the register. |
| `email` | string | no | Email for invoices. |
| `customer_number` | integer | no | Own number. Default: next free number. |

Creates a customer with name, currency, customer group, payment terms and VAT zone, which e-conomic requires. If you give no customer number, e-conomic assigns the next one. It reaches no one and the customer can be edited in e-conomic, so it runs without asking first.

Example response:

```json
{
  "customer_number": 16,
  "name": "Birk & Co",
  "currency": "DKK",
  "payment_terms_number": 2,
  "vat_zone_number": 1,
  "created": true
}
```

### create_draft_invoice

Create a draft invoice for a customer with lines. The draft is not booked. Access: write. REST: `POST /api/v1/e-conomic/customers/{customer_number}/draft-invoices`. MCP: `e_conomic_write → create_draft_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_number` | integer | yes | Customer number from list_customers or create_customer. |
| `date` | date | yes | Invoice date, YYYY-MM-DD. |
| `currency` | string | yes | Currency code, e.g. DKK. |
| `payment_terms_number` | integer | yes | Payment terms number from the customer. |
| `layout_number` | integer | yes | Layout number for the invoice. |
| `lines` | array | yes | Lines: product_number (optional), description, quantity, unit_price. |

Creates a draft with the customer, date, currency, payment terms, layout and lines. The recipient name and VAT zone are copied from the customer. The draft stays editable and is not booked, so it reaches no one and runs without asking first. Lines take a product number or a free text with quantity and unit price. Returns the draft number and net, VAT and gross totals.

Example response:

```json
{
  "draft_invoice_number": 118,
  "customer_number": 14,
  "date": "2026-10-31",
  "currency": "DKK",
  "lines": 2,
  "total_net": 1200,
  "total_vat": 300,
  "total_gross": 1500,
  "booked": false
}
```

### book_invoice

Book a draft invoice, and optionally send it by email or EAN. Access: write, asks the user first. REST: `POST /api/v1/e-conomic/draft-invoices/{draft_invoice_number}/invoices`. MCP: `e_conomic_write → book_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `draft_invoice_number` | integer | yes | Draft invoice number from list_draft_invoices or create_draft_invoice. |
| `send_by` | string | no | none, email or ean. Default: none. |
| `book_with_number` | integer | no | Own invoice number. Default: next number in the sequence. |

Books the draft, which gives it an invoice number, and a booked invoice cannot be edited any more. With send_by email or ean, the invoice is sent to the customer after booking, and only if booking succeeds. Without it nothing is sent. An EAN invoice needs your CVR and country in master data and a recipient identifier on the customer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_number": 1042,
  "draft_invoice_number": 118,
  "customer_number": 14,
  "total_gross": 1500,
  "currency": "DKK",
  "sent_by": "email",
  "status": "booked"
}
```

### create_finance_voucher

Post a finance voucher to a journal. Access: write, asks the user first. REST: `POST /api/v1/e-conomic/journals/{journal_number}/finance-vouchers`. MCP: `e_conomic_write → create_finance_voucher`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `journal_number` | integer | yes | Journal number, e.g. 1. |
| `accounting_year` | string | yes | Accounting year, e.g. 2026. |
| `date` | date | yes | Voucher date, YYYY-MM-DD. |
| `account_number` | integer | yes | Account number. |
| `contra_account_number` | integer | yes | Contra account number. |
| `amount` | number | yes | Amount. Negative marks the opposite side. |
| `text` | string | no | Entry text, up to 250 characters. |
| `vat_code` | string | no | VAT code for the entry. |

Creates a voucher with one finance entry: account, contra account, amount, date and text of up to 250 characters, with an optional VAT code. A negative amount marks the opposite side. It changes the books, so check the accounts in the call. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "voucher_number": 312,
  "accounting_year": "2026",
  "journal_number": 1,
  "account_number": 7200,
  "contra_account_number": 1920,
  "amount": 4500,
  "date": "2026-10-31",
  "text": "Office rent October"
}
```

## How do I connect e-conomic to Claude Code, Codex or Cursor?

Connecting e-conomic takes three steps: sign up, sign in to e-conomic 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 e-conomic to your agent.

1. **Create an account** Sign up and add e-conomic in the console. Your API key is there too.

2. **Sign in to e-conomic in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to e-conomic 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 e-conomic 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.

```
Here is this month's billing list. For each customer, create a draft invoice in e-conomic with the hours and rate I gave. Create customers that do not exist yet. Do not book anything.
```

### Call e-conomic 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/e-conomic 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/e-conomic/customers/14/draft-invoices \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-10-31","currency":"DKK","payment_terms_number":2,"layout_number":1,"lines":[{"description":"Consulting, October","quantity":10,"unit_price":95},{"description":"Workshop day","quantity":1,"unit_price":250}]}'
```

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

```
{
  "draft_invoice_number": 118,
  "customer_number": 14,
  "date": "2026-10-31",
  "currency": "DKK",
  "lines": 2,
  "total_net": 1200,
  "total_vat": 300,
  "total_gross": 1500,
  "booked": false
}
```

## Why use Cotlet for e-conomic?

**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 e-conomic 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 e-conomic changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect e-conomic to Cotlet?

Yes. You sign in to e-conomic yourself, in your own Cloud Browser, and we never save your password. Your agents only get e-conomic 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 e-conomic integration?**

No, Cotlet is independent of e-conomic. e-conomic's own API is open only to approved partners. Cotlet works through your own e-conomic account, the way you use e-conomic 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 e-conomic in your console: your agents lose access at once and you stay signed in. Signing out of e-conomic in the browser works too, and Reset browser deletes the whole profile.

## Is there a e-conomic MCP server on GitHub?

Yes. Open-source e-conomic MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it your AppSecretToken and AgreementGrantToken, and keep it running yourself; when the API or your tokens change, it stops until you fix it. The official REST API is the other route: you register a developer app and write the calls yourself. Cotlet hosts the same kind of server for you with one key, and our team keeps it working.

|  | GitHub MCP server or the official API | Cotlet |
|---|---|---|
| Setup | Sign up for a developer agreement, create an app, generate a grant token, install the server and add the tokens to each MCP client | Sign up, sign in to e-conomic once, add one MCP server or API key |
| When e-conomic changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your e-conomic access | An app secret and a grant token in a file on your computer | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you generate a new token by hand | Your Cloud Browser keeps you signed in; if e-conomic logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time; the API itself lists no fee | 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 e-conomic 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 e-conomic API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the e-conomic 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 e-conomic 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 e-conomic 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 e-conomic only after you enable it. When e-conomic 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 e-conomic, sign out of e-conomic 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.
- **e-conomic's terms:** You use your own e-conomic account and stay responsible for following e-conomic's terms. Cotlet is independent and not affiliated with e-conomic. [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 e-conomic in the console and press Request access. Then you create your API key and connect e-conomic there.

**Do I need to be technical?**

No. You sign in to e-conomic 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 e-conomic to Cotlet?**

Yes. You sign in to e-conomic yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get e-conomic 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 e-conomic 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 e-conomic 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 e-conomic's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. e-conomic 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 e-conomic 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?**

e-conomic 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).

**Do I need a developer agreement and tokens to use Cotlet with e-conomic?**

No. Cotlet signs in with your own e-conomic user. The official route needs a free developer agreement, an app with an AppSecretToken and an AgreementGrantToken that an accounting user generates for each agreement.

**Can my agent change an invoice after it is booked?**

No. e-conomic documents that a booked invoice cannot be edited, so the agent works on drafts and books them only after your OK.

**Can my agent post or send messages in e-conomic without asking me?**

No. Every call to book_invoice or create_finance_voucher waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_customer, create_draft_invoice runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the e-conomic 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/e-conomic 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.