Exact Online MCP Server
Sales invoices, relations and journal entries in Exact Online.
होस्ट किया गया MCP सर्वर
npx add-mcp 'https://cotlet.dev/mcp/v1/exact-online'Claude Code, Codex, Cursor और अन्य में इंस्टॉल होता है
दस्तावेज़
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Exact Online API and MCP server
Yes. Exact Online has a full REST API (checked 14 Oct 2026): sales invoices, relations, journal entries, purchase entries and receivables can be read and written per division. It has no official MCP server from Exact, and you must register your own app and handle OAuth and per-division access first.
Sales invoices, relations and journal entries in Exact Online. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Exact Online. Exact Online is a trademark of its owner. If Exact Online's own integrations cover what you need, use them first.
Cloud accounting and ERP software, strong in the Netherlands and Belgium: sales and purchase invoices, relations, general ledger, bank and cash flow for SMEs and their bookkeepers.
What is the Exact Online API?
Cotlet's Exact Online API exposes 12 endpoints for your own Exact Online account: list divisions, search relations, list sales invoices, get sales invoice, list outstanding receivables, list ledger accounts, list journal entries, create relation, create sales invoice, send sales invoice, book journal entry and create purchase entry. The list_divisions endpoint returns the Exact Online companies (divisions) your account can work in. Each endpoint takes simple JSON inputs like division, limit or cursor and works both as an operation of the exact_online_read or exact_online_write MCP tool for agents and as a REST call for scripts.
- Category: Invoicing & freelance CRM
- Endpoints: 12 (7 read, 5 write)
- Updated: 2026-11-17
Yes. Cotlet is a hosted MCP server and REST API for Exact Online with 12 endpoints (7 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.
Does Exact Online have an official API?
Yes. Exact Online has a full REST API (checked 14 Oct 2026): sales invoices, relations, journal entries, purchase entries and receivables can be read and written per division. It has no official MCP server from Exact, and you must register your own app and handle OAuth and per-division access first.
| Task | Exact Online official | Cotlet |
|---|---|---|
| Create a relation (customer or supplier) | Yes: POST to the CRM Accounts endpoint | Yes |
| Create a sales invoice with lines | Yes: SalesInvoices endpoint, available only in some packages | Yes |
| Send an invoice to the customer | Yes: PrintedSalesInvoices can email, post to the customer postbox or send via Peppol | Yes |
| Book a general journal entry | Yes: GeneralJournalEntries; entries get type 90 (Other) | Yes |
| List outstanding receivables | Yes: Cashflow Receivables endpoint, read and prepare collections | Yes |
| Upload a purchase invoice as a purchase entry | Yes: PurchaseEntries with lines; attaching the PDF is a separate document call | Yes |
| Use it from an AI agent without registering an app | No | Yes |
Sources: Exact Online REST API: reference documentation, Exact Online REST API: SalesInvoices, Exact Online REST API: PrintedSalesInvoices, Exact Online REST API: GeneralJournalEntries
Quick reference
Yes. Exact Online has a full REST API (checked 14 Oct 2026): sales invoices, relations, journal entries, purchase entries and receivables can be read and written per division. It has no official MCP server from Exact, and you must register your own app and handle OAuth and per-division access first.
Cotlet provides a hosted MCP server and REST API for Exact Online: 12 tools (7 read, 5 write).
Access Sign up at https://cotlet.dev/app/signup?app=exact-online and request the app in the Cotlet console. ChatGPT and Claude connect with OAuth at https://cotlet.dev/mcp/v1/connect, no API key; code editors and scripts use an API key from the console.
MCP server https://cotlet.dev/mcp/v1
MCP tools exact_online_read, exact_online_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base https://cotlet.dev/api/v1/exact-online, each operation at its own route, e.g. POST /api/v1/exact-online/sales-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_divisions, search_relations, list_sales_invoices, get_sales_invoice, list_receivables, list_gl_accounts, list_journal_entries, create_relation, create_sales_invoice, send_sales_invoice, book_journal_entry, create_purchase_entry
Confirm create_sales_invoice, send_sales_invoice, book_journal_entry, create_purchase_entry (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/exact-online-api-mcp-server.md
How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=exact-online and requests Exact Online in the Cotlet console.
2. The user signs in to Exact Online once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Exact Online for agents. An agent cannot do this step.
3. ChatGPT and Claude: the user adds https://cotlet.dev/mcp/v1/connect as a connector and signs in to Cotlet (OAuth). Code editors and scripts: an API key from the console goes into the MCP client or the REST call as a bearer token.
Fits: people who want a hosted Exact Online server that someone else maintains, including non-developers.
Policy: Cotlet never stores passwords and 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 Exact Online 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 Exact Online 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 Exact Online 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 Exact Online's terms; Cotlet is not affiliated with Exact Online.
What can an AI agent do in Exact Online?
Cotlet is best for SMEs and bookkeepers on Exact Online who want an AI agent to create and send invoices and book entries without running or fixing a server.
- Create and send sales invoices (runs: weekly): "For each customer in this list, create a sales invoice in my main Exact Online company with the hours and rate I give you, then send it to the customer by email. Show me each invoice before sending." →
search_relations,create_sales_invoice,send_sales_invoice - Book recurring journal entries (runs: weekly): "Book this month's accrual as a general journal entry in my main Exact Online company: debit 4000 and credit 1800 for 1,200.00, dated the last day of the month, with the description I give. Show me the entry first." →
list_gl_accounts,list_journal_entries,book_journal_entry - Upload purchase invoices: "Book this supplier invoice as a purchase entry in my main Exact Online company: supplier Acme Supplies, invoice 2026-118, 450.00 net, dated today. Show me the entry first." →
search_relations,create_purchase_entry - List overdue receivables (runs: weekly): "Every Monday, list the receivables in my main Exact Online company that are past due and group them by customer." →
list_receivables - Add new customers as relations: "Add these customers as relations in my main Exact Online company if they do not exist yet, and tell me which ones were new." →
search_relations,create_relation
Can Exact Online automations run on a schedule in n8n, Make or Zapier?
Yes. Cotlet does not replace your automation platform: it gives it a Exact Online 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 create and send sales invoices, 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/exact-online/relations/search. | 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/exact-online/relations/search with your API key. | cron or GitHub Actions. |
Tools
For AI agents: Every endpoint and its schema is public. The 12 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 Exact Online.
list_divisions
The Exact Online companies (divisions) your account can work in. Access: read. REST: GET /api/v1/exact-online/divisions. MCP: exact_online_read → list_divisions.
No parameters.
Returns every division your account has access to, with its code and name. Use the code as the division parameter of the other tools. When a tool gets no division, it uses the current division of your account.
Example response:
{
"divisions": [
{
"division": 1234567,
"name": "Example BV",
"is_current": true
},
{
"division": 1234568,
"name": "Example Holding BV",
"is_current": false
}
]
}
search_relations
Customers and suppliers (relations) by name, with code, city and status. Access: read. REST: GET /api/v1/exact-online/relations/search. MCP: exact_online_read → search_relations.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
query | string | yes | Part of the name or the code. |
limit | integer | no | Records per page. Default: 50. |
cursor | string | no | Next page cursor from the previous call. |
Searches the relations of one division by name or code and returns up to one page of matches. Use the account_id of a match as the customer of create_sales_invoice. An empty list means no relation matches, and create_relation can add it.
Example response:
{
"relations": [
{
"account_id": "8a3f1c20-2b6e-4d44-9e0b-7f4c1d2a9001",
"code": "1042",
"name": "Northwind Studio",
"city": "Utrecht",
"status": "customer"
}
],
"next_cursor": null
}
list_sales_invoices
Sales invoices of a division with number, customer, date and amount. Access: read. REST: GET /api/v1/exact-online/sales-invoices. MCP: exact_online_read → list_sales_invoices.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
from_date | date | no | Only invoices dated on or after this date. |
to_date | date | no | Only invoices dated on or before this date. |
customer | string | no | Relation account_id from search_relations. |
limit | integer | no | Records per page. Default: 50. |
cursor | string | no | Next page cursor from the previous call. |
Lists sales invoices of one division, newest first, filtered by date range or customer. It returns the invoice number, date, customer, amount and the invoice ID that send_sales_invoice needs. The endpoint exists only in some Exact packages.
Example response:
{
"invoices": [
{
"invoice_id": "b21e9d77-5a0c-4f1e-8d13-0c6a77e45002",
"invoice_number": 20260412,
"customer": "Northwind Studio",
"invoice_date": "2026-10-14",
"amount_excl_vat": 1140,
"currency": "EUR"
}
],
"next_cursor": null
}
get_sales_invoice
One sales invoice with all its lines. Access: read. REST: GET /api/v1/exact-online/invoices/{invoice_id}/sales-invoice. MCP: exact_online_read → get_sales_invoice.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
invoice_id | string | yes | Invoice ID from list_sales_invoices or create_sales_invoice. |
Returns one sales invoice by invoice ID with its header and every line: description, quantity, unit price and VAT code. Use it to check a draft before send_sales_invoice.
Example response:
{
"invoice_id": "b21e9d77-5a0c-4f1e-8d13-0c6a77e45002",
"invoice_number": 20260412,
"customer": "Northwind Studio",
"invoice_date": "2026-10-14",
"lines": [
{
"description": "Consulting, October",
"quantity": 12,
"unit_price": 95,
"vat_code": "2",
"amount": 1140
}
],
"amount_excl_vat": 1140,
"currency": "EUR"
}
list_receivables
Payments still to be received, with customer, amount, due date and status. Access: read. REST: GET /api/v1/exact-online/receivables. MCP: exact_online_read → list_receivables.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
status | string | no | Status as Exact shows it, for example Open or Processed. |
due_before | date | no | Only receivables due before this date. |
limit | integer | no | Records per page. Default: 50. |
cursor | string | no | Next page cursor from the previous call. |
Returns the receivables overview of one division: payments to be received, with the customer, amount, due date and status such as Open or Processed. Filter by status or due date to find what is overdue.
Example response:
{
"receivables": [
{
"id": "c4d8e1a0-91f3-4b52-a6d7-3e0b5f8c7003",
"customer": "Bakker Logistics",
"amount": 760,
"currency": "EUR",
"due_date": "2026-09-30",
"status": "Open"
}
],
"next_cursor": null
}
list_gl_accounts
General ledger accounts of a division with code and description. Access: read. REST: GET /api/v1/exact-online/gl-accounts. MCP: exact_online_read → list_gl_accounts.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
query | string | no | Part of the code or the description. |
limit | integer | no | Records per page. Default: 50. |
cursor | string | no | Next page cursor from the previous call. |
Lists the ledger accounts of one division with their code and description. Use the code in book_journal_entry. Search by code or part of the description to find one account.
Example response:
{
"accounts": [
{
"gl_account": "4000",
"description": "Rent",
"type": "expense"
},
{
"gl_account": "1800",
"description": "Accruals",
"type": "liability"
}
],
"next_cursor": null
}
list_journal_entries
General journal entries of a division with date, description and lines. Access: read. REST: GET /api/v1/exact-online/journal-entries. MCP: exact_online_read → list_journal_entries.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
from_date | date | no | Only entries dated on or after this date. |
to_date | date | no | Only entries dated on or before this date. |
description | string | no | Part of the entry description. |
limit | integer | no | Records per page. Default: 50. |
cursor | string | no | Next page cursor from the previous call. |
Lists general journal entries in a division, newest first, filtered by date or description. Each entry shows its number, date, description and lines. Use it to check for an existing entry before book_journal_entry.
Example response:
{
"entries": [
{
"entry_number": 90001198,
"entry_date": "2026-09-30",
"description": "Rent accrual September",
"lines": [
{
"gl_account": "4000",
"debit": 1200
},
{
"gl_account": "1800",
"credit": 1200
}
]
}
],
"next_cursor": null
}
create_relation
Add a customer or supplier (relation) to a division. Access: write. REST: POST /api/v1/exact-online/relations. MCP: exact_online_write → create_relation.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
name | string | yes | Name of the company or person. |
status | enum | no | customer or supplier. Default: customer. |
email | string | no | Email address for invoices. |
city | string | no | City. |
country | string | no | Two-letter country code. |
Creates a relation with a name, status and optional address and email. It returns the account_id to use in other tools. It sends nothing to anyone and moves no money, so it runs without asking first. Search with search_relations before creating to avoid a duplicate.
Example response:
{
"account_id": "8a3f1c20-2b6e-4d44-9e0b-7f4c1d2a9002",
"code": "1043",
"name": "Van Dijk Design",
"status": "customer"
}
create_sales_invoice
Create a sales invoice with its lines for a customer. It does not send it. Access: write, asks the user first. REST: POST /api/v1/exact-online/sales-invoices. MCP: exact_online_write → create_sales_invoice.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
customer | string | yes | Relation name or account_id from search_relations. |
invoice_date | date | yes | Invoice date. |
lines | array | yes | Objects with description, quantity, unit_price and vat_code. |
your_ref | string | no | Your reference shown on the invoice. |
Creates a sales invoice and its lines in one call, because Exact needs the lines together with the header. It returns the invoice ID, number and total as Exact calculated them. It does not send the invoice; send_sales_invoice does. The endpoint exists only in some Exact packages. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"invoice_id": "b21e9d77-5a0c-4f1e-8d13-0c6a77e45002",
"invoice_number": 20260412,
"customer": "Northwind Studio",
"invoice_date": "2026-10-14",
"lines": [
{
"description": "Consulting, October",
"quantity": 12,
"unit_price": 95,
"vat_code": "2",
"amount": 1140
}
],
"amount_excl_vat": 1140,
"currency": "EUR",
"status": "created"
}
send_sales_invoice
Send an existing sales invoice to the customer by email, postbox or Peppol. Access: write, asks the user first. REST: POST /api/v1/exact-online/invoices/{invoice_id}/sales-invoices. MCP: exact_online_write → send_sales_invoice.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
invoice_id | string | yes | Invoice ID from create_sales_invoice or list_sales_invoices. |
channel | enum | yes | email, postbox or peppol. |
sender_email | string | no | Sender address when channel is email. |
Creates the invoice document from an existing sales invoice and sends it by the channel you choose. Exact also creates the financial transaction for the invoice. Sending reaches your customer and cannot be taken back. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"invoice_id": "b21e9d77-5a0c-4f1e-8d13-0c6a77e45002",
"invoice_number": 20260412,
"channel": "email",
"sent_to": "billing@northwind.example",
"status": "sent"
}
book_journal_entry
Book a general journal entry with debit and credit lines. Access: write, asks the user first. REST: POST /api/v1/exact-online/journal-entries. MCP: exact_online_write → book_journal_entry.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
entry_date | date | yes | Date of the entry. |
description | string | yes | Entry description. |
lines | array | yes | Objects with gl_account and either debit or credit. |
Books one general journal entry with its lines. Exact gives entries made this way type 90 (Other), and opening balances cannot be created. Debits and credits must balance. It writes to the ledger. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"entry_number": 90001234,
"entry_date": "2026-10-31",
"description": "Rent accrual October",
"lines": [
{
"gl_account": "4000",
"debit": 1200
},
{
"gl_account": "1800",
"credit": 1200
}
],
"status": "booked"
}
create_purchase_entry
Book a supplier invoice as a purchase entry with its lines. Access: write, asks the user first. REST: POST /api/v1/exact-online/invoices/{invoice_number}/purchase-entries. MCP: exact_online_write → create_purchase_entry.
| Parameter | Type | Required | Description |
|---|---|---|---|
division | integer | no | Division (company) code from list_divisions. Default: the account's current division. |
supplier | string | yes | Relation name or account_id from search_relations. |
invoice_number | string | yes | The supplier's invoice number. |
entry_date | date | yes | Invoice date. |
lines | array | yes | Objects with gl_account, description, amount and vat_code. |
Creates a purchase entry for a supplier with its lines, in one call. It returns the entry number and total. Attaching the invoice PDF is not part of this tool. It writes to the ledger. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"entry_number": 70000456,
"supplier": "Acme Supplies",
"invoice_number": "2026-118",
"entry_date": "2026-10-14",
"amount_excl_vat": 450,
"currency": "EUR",
"status": "booked"
}
How do I connect Exact Online to ChatGPT, Claude, Cursor or Codex?
Connecting Exact Online takes three steps: sign up, sign in to Exact Online once in your Cloud Browser and enable it for agents, then add Cotlet to ChatGPT or Claude as a connector, with no API key, or add one MCP server or call the REST API with an API key.
Connect Exact Online to your agent.
-
Create an account Sign up and add Exact Online in the console. ChatGPT and Claude need no API key: you sign in to Cotlet when you add the connector. Code editors and scripts take an API key from the console.
-
Sign in to Exact Online in your Cloud Browser Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Exact Online 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.
-
Add Cotlet to ChatGPT, Claude or your agent Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
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"
- Ask your agent Ask in plain words. Your agent finds the Exact Online 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.
For each customer in this list, create a sales invoice in my main Exact Online company with the hours and rate I give you, then send it to the customer by email. Show me each invoice before sending.
Call Exact Online from your scripts.
- 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_..."
- Call a tool Every tool is an endpoint under /api/v1/exact-online 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/exact-online/sales-invoices \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"division":1234567,"customer":"Northwind Studio","invoice_date":"2026-10-14","lines":[{"description":"Consulting, October","quantity":12,"unit_price":95,"vat_code":"2"}]}'
- Read the result You get plain JSON back, ready for your script. A failed call costs nothing.
{
"invoice_id": "b21e9d77-5a0c-4f1e-8d13-0c6a77e45002",
"invoice_number": 20260412,
"customer": "Northwind Studio",
"invoice_date": "2026-10-14",
"lines": [
{
"description": "Consulting, October",
"quantity": 12,
"unit_price": 95,
"vat_code": "2",
"amount": 1140
}
],
"amount_excl_vat": 1140,
"currency": "EUR",
"status": "created"
}
How to use the Exact Online REST API
Create your Cotlet API key
Create a Cotlet API key with access to Exact Online and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Exact Online in Cotlet and enable it for agents. Account access: Your own Exact Online account with rights on the company (division) you work in.
Make your first Exact Online API request
REST:
curl https://cotlet.dev/api/v1/exact-online/divisions \
-H "Authorization: Bearer $COTLET_API_KEY"
Read divisions and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "exact-online",
"tool": "list_divisions",
"result": {
"divisions": [
{
"division": 1234567,
"name": "Example BV",
"is_current": true
},
{
"division": 1234568,
"name": "Example Holding BV",
"is_current": false
}
]
}
}
Returns every division your account has access to, with its code and name. Use the code as the division parameter of the other tools.
When a tool gets no division, it uses the current division of your account.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Exact Online workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Payments still to be received, with customer, amount, due date and status. Use list_receivables in your configured operations sheet. |
| Make | HTTP > Make a request | Sales invoices of a division with number, customer, date and amount. Use list_sales_invoices in your configured operations sheet. |
| Python or Node.js | REST API | General journal entries of a division with date, description and lines. Use list_journal_entries in your configured operations sheet. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Exact Online; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Why use Cotlet for Exact Online?
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 ChatGPT, Claude, Claude Code, Codex and Cursor.
Your login stays yours
- You sign in to Exact Online 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 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 Exact Online changes, the tool pauses until we fix it.
- Failed calls cost nothing.
Is it safe to connect Exact Online to Cotlet?
Yes. You sign in to Exact Online yourself, in your own Cloud Browser, and we never save your password. Your agents only get Exact Online 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
- A+ on securityheaders.com: Browser protections sent with every page, all six headers present. Live result
- A+ on Mozilla Observatory: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. Live result
- Clean on Sucuri SiteCheck: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. Live result
How Cotlet protects your access
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 Exact Online integration?
No, Cotlet is independent of Exact Online. Exact Online's own API is open only to approved partners. Cotlet works through your own Exact Online account, the way you use Exact Online in the browser.
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 Exact Online in your console: your agents lose access at once and you stay signed in. Signing out of Exact Online in the browser works too, and Reset browser deletes the whole profile.
Is there a Exact Online MCP server on GitHub?
Exact Online has an official REST API, and developers use it from scripts and from tools like Zapier. Using it from an AI agent means registering your own app, running the OAuth flow, passing a division in every call and writing the tool layer yourself. Cotlet gives your agent a hosted MCP server and the same tools as a REST API, behind one sign-in and one key.
| Official API | Cotlet | |
|---|---|---|
| Setup | Register an app with Exact, run OAuth, store tokens, write the calls | Sign up, sign in to Exact Online once, add one MCP server or API key |
| Companies | Every request names a division; you look the codes up and pass them | list_divisions returns them; tools take a division or use the default |
| When Exact changes | You update your code and handle versions yourself | Our team tests it daily and fixes it for you; failed calls are free |
| Your Exact session | You keep access and refresh tokens, and you refresh them | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Upkeep | You host, monitor and debug it | Nothing to host or update |
| Where it runs | Wherever you deploy your own code | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | The API itself has no extra fee on this page; your time is the cost | 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 Exact Online 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 Exact Online API cost?
Free 7-day trial with 2,000 credits, no card needed. After that, the Exact Online 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 10 to 100 credits (10 for most tools, about $0.04 to $0.06), 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 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $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
How Cotlet holds your access
Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Exact Online 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
- Your sign-in: You sign in to Exact Online 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 Exact Online only after you enable it. When Exact Online signs you out, your agent gives you a link to sign in again. Security
- Revoking access: Press Disable for agents next to Exact Online, sign out of Exact Online 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 or bypass MFA.
- Exact Online's terms: You use your own Exact Online account and stay responsible for following Exact Online's terms. Cotlet is independent and not affiliated with Exact Online. Terms
- Contact: Questions about the company, security or an app: contact@cotlet.dev
Exact Online API and MCP: questions
How do I get access?
Sign up free, open Exact Online in the console and press Activate. Then you create your API key and connect Exact Online there.
Do I need to be technical?
No. You sign in to Exact Online 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 Exact Online to Cotlet?
Yes. You sign in to Exact Online yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Exact Online 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 Exact Online 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 Exact Online 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 Exact Online's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Exact Online 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 Exact Online 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?
Exact Online 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).
How do I connect Exact Online to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Exact Online once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Exact Online account through Cotlet, in their phone apps too.
What can ChatGPT do in Exact Online?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Exact Online: create and send sales invoices; book recurring journal entries; upload purchase invoices. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need to register an app in Exact to use Cotlet?
No. You sign in to your own Exact Online account once. The official REST API needs a registered app and OAuth, and its sales invoice endpoints exist only in some Exact packages.
Can my agent send invoices without asking me?
Only if you switch confirmation off for send_sales_invoice. By default you confirm every invoice that is created, sent or booked, because each one reaches a customer or the ledger.
Can my agent post or send messages in Exact Online without asking me?
No. Every call to create_sales_invoice, send_sales_invoice, book_journal_entry or create_purchase_entry 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_relation runs without asking, because it sends nothing to anyone and one call undoes it.
Can I use the Exact Online 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/exact-online from the HTTP Request node.
Can I use the Exact Online API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
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
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.