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

# Bokio API and MCP server

> Yes, Bokio has a public REST API for invoices, customers, journal entries, uploads and supplier invoices (checked 14 Oct 2026), but it depends on your price plan and on the kind of integration: a private integration token works for one company only, and a tool that serves several companies must be registered as a public integration with OAuth 2.0. Bokio publishes no MCP server of its own.

Swedish online bookkeeping and invoicing software for sole traders and small companies: customer invoices, uploaded receipts, journal entries and bank payments in one account.

## What is the Bokio API?

Cotlet's Bokio API exposes 13 endpoints for your own Bokio account: list invoices, get invoice, list customers, list accounts, list journal entries, list uploads, create customer, create invoice, publish invoice, send invoice, record invoice payment, upload receipt and create journal entry. The list_invoices endpoint returns customer invoices with number, customer, dates, status and amounts. Each endpoint takes simple JSON inputs like page, page_size or invoice_id and works both as an operation of the bokio_read or bokio_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:** 13 (6 read, 7 write)
- **Updated:** 2026-10-18

Yes, Bokio has a public REST API for invoices, customers, journal entries, uploads and supplier invoices (checked 14 Oct 2026), but it depends on your price plan and on the kind of integration: a private integration token works for one company only, and a tool that serves several companies must be registered as a public integration with OAuth 2.0. Cotlet is a hosted MCP server and REST API for Bokio with 13 endpoints (6 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Bokio have an official API?

Yes, Bokio has a public REST API for invoices, customers, journal entries, uploads and supplier invoices (checked 14 Oct 2026), but it depends on your price plan and on the kind of integration: a private integration token works for one company only, and a tool that serves several companies must be registered as a public integration with OAuth 2.0. Bokio publishes no MCP server of its own.

| Task | Bokio official | Cotlet |
|---|---|---|
| Create customers | Yes: POST customers | Yes |
| Create a draft invoice | Yes: POST invoices; the invoice stays a draft with no invoice number | Yes |
| Publish an invoice | Yes: POST publish assigns the invoice number | Yes |
| Email an invoice to the customer | No: Bokio states that publishing through the API does not email the invoice | Yes |
| Record an invoice payment | Yes: payments plus a record call to book it | Yes |
| Upload a receipt | Yes: PDF, JPEG and PNG | Yes |
| Create a journal entry | Yes: debits must equal credits, supported accounts only | Yes |
| List unpaid and overdue invoices | Yes: filter by status | Yes |

Sources: [Bokio API docs: Welcome](https://docs.bokio.se/docs/welcome), [Bokio API docs: Price plan requirements](https://docs.bokio.se/docs/price-plan-requirements), [Bokio API docs: Public vs private integrations](https://docs.bokio.se/docs/public-private-integrations), [Bokio API docs: Publish an invoice](https://docs.bokio.se/reference/post-invoices-invoiceid-publish)

## For AI agents

```text
Yes, Bokio has a public REST API for invoices, customers, journal entries, uploads and supplier invoices (checked 14 Oct 2026), but it depends on your price plan and on the kind of integration: a private integration token works for one company only, and a tool that serves several companies must be registered as a public integration with OAuth 2.0. Bokio publishes no MCP server of its own.
Cotlet provides a hosted MCP server and REST API for Bokio: 13 tools (6 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=bokio, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    bokio_read, bokio_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/bokio, each operation at its own route, e.g. POST /api/v1/bokio/customers/{customer_id}/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_invoices, get_invoice, list_customers, list_accounts, list_journal_entries, list_uploads, create_customer, create_invoice, publish_invoice, send_invoice, record_invoice_payment, upload_receipt, create_journal_entry
Confirm      publish_invoice, send_invoice, record_invoice_payment, create_journal_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/bokio-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=bokio, requests Bokio in the Cotlet console and creates an API key there.
2. The user signs in to Bokio once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Bokio 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 Bokio server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Bokio MCP server instead.

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 Bokio 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 Bokio 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 Bokio 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 Bokio's terms; Cotlet is not affiliated with Bokio.
```

## What can an AI agent do in Bokio?

Cotlet is best for Swedish sole traders and small businesses who want an agent to invoice, file receipts and record payments in Bokio without running or fixing a server.

- **[Create and send invoices from a list](https://cotlet.dev/integrations/bokio-api-mcp-server/create-and-send-invoices.md)** (runs: weekly): "Here are this week's billable jobs for Nordlys Design AB. Create one Bokio invoice with a line for each job, show me the total, and after I say OK publish it and email it to their finance address." → `list_customers`, `create_customer`, `create_invoice`, `publish_invoice`, `send_invoice`
- **[Upload receipts to your books](https://cotlet.dev/integrations/bokio-api-mcp-server/upload-receipts.md)** (runs: daily): "Take the PDF and photo receipts from this folder and upload each one to Bokio with the shop name and date as the description. Tell me which ones were already there." → `list_uploads`, `upload_receipt`
- **[Record customer payments on invoices](https://cotlet.dev/integrations/bokio-api-mcp-server/record-invoice-payments.md)** (runs: weekly): "Here is this week's bank statement. Match each incoming payment to an unpaid Bokio invoice by amount and reference, and record the payment on account 1930 on the date it arrived. List what you could not match." → `list_invoices`, `get_invoice`, `record_invoice_payment`
- **Weekly report of unpaid and overdue invoices** (runs: weekly): "Every Monday, list my unpaid Bokio invoices, newest due date last, and flag the ones that are overdue with the customer and amount." → `list_invoices`
- **Book a recurring journal entry**: "On the 25th, book the monthly office rent as a journal entry: debit 5010 and credit 1930, 8 000 SEK. Show me the entry first." → `list_accounts`, `create_journal_entry`

## Can Bokio automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Bokio 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 invoices from a list, 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/bokio/customers. | 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/bokio/customers with your API key. | cron or GitHub Actions. |

## Tools

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

### list_invoices

Customer invoices with number, customer, dates, status and amounts. Access: read. REST: `GET /api/v1/bokio/invoices`. MCP: `bokio_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | draft, published, paid, overPaid, underPaid, overdue, credited or credit. |
| `due_before` | string | no | Only invoices due on or before this date, YYYY-MM-DD. |
| `customer_id` | string | no | Customer ID from list_customers. |
| `page` | integer | no | Page number. Default: 1. |
| `page_size` | integer | no | 1 to 100. Default: 25. |

Lists invoices of the company, 25 per page by default and up to 100. Filter by status (draft, published, paid, overPaid, underPaid, overdue, credited, credit), by due date or by customer. Each item carries total, VAT and the amount paid so far, so unpaid invoices are the ones where paid_amount is below total.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "f2d84b1a-6c30-4e97-8a5b-1d9c7e3a40b2",
      "invoice_number": "2026-1042",
      "customer": "Nordlys Design AB",
      "status": "overdue",
      "invoice_date": "2026-09-13",
      "due_date": "2026-10-13",
      "currency": "SEK",
      "total_amount": 13125,
      "total_tax": 2625,
      "paid_amount": 0
    }
  ],
  "total_items": 1,
  "total_pages": 1,
  "current_page": 1
}
```

### get_invoice

One invoice with all lines, amounts, payments and status. Access: read. REST: `GET /api/v1/bokio/invoices/{invoice_id}`. MCP: `bokio_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or create_invoice. |

Returns one invoice with its line items, tax rate per line, totals and the payments registered on it. A draft has status draft and no invoice number. Use it right before recording a payment to check that nothing was paid already.

Example response:

```json
{
  "invoice_id": "f2d84b1a-6c30-4e97-8a5b-1d9c7e3a40b2",
  "invoice_number": "2026-1042",
  "status": "overdue",
  "customer": "Nordlys Design AB",
  "currency": "SEK",
  "invoice_date": "2026-09-13",
  "due_date": "2026-10-13",
  "payment_reference": "2026104242",
  "lines": [
    {
      "description": "Website audit",
      "quantity": 8,
      "unit_price": 1200,
      "tax_rate": 25
    },
    {
      "description": "Hosting setup",
      "quantity": 1,
      "unit_price": 900,
      "tax_rate": 25
    }
  ],
  "total_amount": 13125,
  "total_tax": 2625,
  "paid_amount": 0,
  "payments": []
}
```

### list_customers

Customers with name, type, organisation number and payment terms. Access: read. REST: `GET /api/v1/bokio/customers`. MCP: `bokio_read → list_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Part of the name or email. |
| `page` | integer | no | Page number. Default: 1. |
| `page_size` | integer | no | 1 to 100. Default: 25. |

Lists the customers of the company and searches by name or email. Use customer_id from each item in create_invoice. Pages hold up to 100 customers.

Example response:

```json
{
  "customers": [
    {
      "customer_id": "c7a1e5d2-3b94-4f60-9a1d-5e2f0b8c6d11",
      "name": "Nordlys Design AB",
      "type": "company",
      "org_number": "556000-0000",
      "email": "ekonomi@nordlys.example"
    }
  ],
  "total_items": 1,
  "total_pages": 1,
  "current_page": 1
}
```

### list_accounts

The chart of accounts: account numbers and names you can book on. Access: read. REST: `GET /api/v1/bokio/accounts`. MCP: `bokio_read → list_accounts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Part of the account number or name. |

Returns the accounts of the company's chart of accounts with number and name. Bokio's API only books on accounts it supports, and a journal entry with another account is rejected, so check here first.

Example response:

```json
{
  "accounts": [
    {
      "account": "1930",
      "name": "Företagskonto"
    },
    {
      "account": "5010",
      "name": "Lokalhyra"
    }
  ]
}
```

### list_journal_entries

Booked journal entries with date, title and debit and credit rows. Access: read. REST: `GET /api/v1/bokio/journal-entries`. MCP: `bokio_read → list_journal_entries`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date_from` | string | no | First date, YYYY-MM-DD. |
| `date_to` | string | no | Last date, YYYY-MM-DD. |
| `page` | integer | no | Page number. Default: 1. |
| `page_size` | integer | no | 1 to 100. Default: 25. |

Lists journal entries of the company with their rows, 25 per page by default and up to 100. Use it to check whether an entry for the month is already booked before creating another.

Example response:

```json
{
  "journal_entries": [
    {
      "journal_entry_id": "9b3e61d4-27a8-4c15-b0f2-7d4a5e8c1f36",
      "date": "2026-09-25",
      "title": "Office rent September",
      "items": [
        {
          "account": "5010",
          "debit": 8000,
          "credit": 0
        },
        {
          "account": "1930",
          "debit": 0,
          "credit": 8000
        }
      ]
    }
  ],
  "total_items": 1,
  "total_pages": 1,
  "current_page": 1
}
```

### list_uploads

Receipts and documents already uploaded, with description and file type. Access: read. REST: `GET /api/v1/bokio/uploads`. MCP: `bokio_read → list_uploads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `page` | integer | no | Page number. Default: 1. |
| `page_size` | integer | no | 1 to 100. Default: 25. |

Lists the files in the Uppladdat page of the company with description, content type and the journal entry each is attached to, if any. An upload with no journal entry is still waiting to be booked.

Example response:

```json
{
  "uploads": [
    {
      "upload_id": "d41c8e07-5a2b-4f93-8c60-3e1b9a7d2f54",
      "description": "Elgiganten 2026-10-02",
      "content_type": "application/pdf",
      "journal_entry_id": null
    }
  ]
}
```

### create_customer

Add a customer with name, type and contact details. Access: write. REST: `POST /api/v1/bokio/customers`. MCP: `bokio_write → create_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Customer name. |
| `type` | string | yes | company or individual. |
| `email` | string | no | Email address for invoices. |
| `org_number` | string | no | Organisation number, for a company. |
| `vat_number` | string | no | VAT number, for a company. |

Creates a customer and returns its ID for create_invoice. type is company or individual. The customer reaches no one and can be removed in Bokio, so create_customer runs without asking first.

Example response:

```json
{
  "customer_id": "c7a1e5d2-3b94-4f60-9a1d-5e2f0b8c6d11",
  "name": "Nordlys Design AB",
  "type": "company"
}
```

### create_invoice

Create a draft invoice for a customer with its lines. Access: write. REST: `POST /api/v1/bokio/customers/{customer_id}/invoices`. MCP: `bokio_write → create_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | yes | Customer ID from list_customers or create_customer. |
| `currency` | string | no | Currency code such as SEK. Default: SEK. |
| `invoice_date` | string | yes | YYYY-MM-DD. |
| `due_date` | string | yes | YYYY-MM-DD. |
| `lines` | array | yes | Objects with description, quantity, unit_price and tax_rate (percent). |

Creates an invoice as a draft with status draft and no invoice number, and returns net, VAT and total so you can check them. Bokio has no discount per line: add a line with a negative unit price instead. A draft reaches no one and can be deleted in Bokio, so create_invoice runs without asking first; publishing is a separate tool.

Example response:

```json
{
  "invoice_id": "f2d84b1a-6c30-4e97-8a5b-1d9c7e3a40b2",
  "status": "draft",
  "invoice_number": null,
  "customer": "Nordlys Design AB",
  "currency": "SEK",
  "invoice_date": "2026-10-14",
  "due_date": "2026-11-13",
  "total_amount": 13125,
  "total_tax": 2625
}
```

### publish_invoice

Turn a draft into a published invoice with an invoice number. Access: write, asks the user first. REST: `POST /api/v1/bokio/invoices/{invoice_id}/publish`. MCP: `bokio_write → publish_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or create_invoice. |

Publishes a draft invoice, which assigns the invoice number and the payment reference and makes it final for the customer. Publishing does not email the invoice; use send_invoice for that. A published invoice is no longer edited like a draft. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "f2d84b1a-6c30-4e97-8a5b-1d9c7e3a40b2",
  "status": "published",
  "invoice_number": "2026-1042",
  "payment_reference": "2026104242"
}
```

### send_invoice

Email a published invoice to the customer from Bokio. Access: write, asks the user first. REST: `POST /api/v1/bokio/invoices/{invoice_id}`. MCP: `bokio_write → send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or create_invoice. |
| `recipients` | array | yes | Email addresses, up to four. |
| `attach_pdf` | boolean | no | true attaches the PDF, false sends a link to it. Default: false. |

Sends a published invoice by email from Bokio, as a link to a PDF or an attached PDF, to up to four recipients. Bokio can show whether a recipient opened a PDF link. The email goes out under your company name and cannot be recalled. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "f2d84b1a-6c30-4e97-8a5b-1d9c7e3a40b2",
  "invoice_number": "2026-1042",
  "status": "sent",
  "recipients": [
    "ekonomi@nordlys.example"
  ],
  "sent_at": "2026-10-14T10:12:00+02:00"
}
```

### record_invoice_payment

Register and book a customer payment on an invoice. Access: write, asks the user first. REST: `POST /api/v1/bokio/invoices/{invoice_id}/payment`. MCP: `bokio_write → record_invoice_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or create_invoice. |
| `date` | string | yes | Date the money arrived, YYYY-MM-DD. |
| `amount` | number | yes | Amount paid, in the company's base currency. |
| `account` | string | yes | Bookkeeping account the payment went to, for example 1930. |

Registers a payment with its date and amount on the account you name and books it, which clears the receivable. An amount below the total leaves the invoice open as a partial payment. It changes the books and the invoice status. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "f2d84b1a-6c30-4e97-8a5b-1d9c7e3a40b2",
  "payment_id": "a8e2c5f1-9d40-4b73-b6a2-0c7f3d18e594",
  "amount": 13125,
  "date": "2026-10-13",
  "account": "1930",
  "booked": true,
  "invoice_status": "paid",
  "paid_amount": 13125
}
```

### upload_receipt

Add a receipt or invoice document to Bokio as an upload. Access: write. REST: `POST /api/v1/bokio/receipts`. MCP: `bokio_write → upload_receipt`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `file_url` | string | yes | Address of the file to upload: PDF, JPEG or PNG. |
| `description` | string | no | Shown in the list. Default: the file name. |
| `journal_entry_id` | string | no | Journal entry ID to attach the upload to. |

Uploads one PDF, JPEG or PNG to the Uppladdat page. Without a description Bokio uses the file name. The file waits there to be booked, reaches no one and can be deleted in Bokio, so upload_receipt runs without asking first.

Example response:

```json
{
  "upload_id": "d41c8e07-5a2b-4f93-8c60-3e1b9a7d2f54",
  "description": "Clas Ohlson 2026-10-09",
  "content_type": "image/jpeg",
  "journal_entry_id": null
}
```

### create_journal_entry

Book a manual journal entry with a title, date and balanced rows. Access: write, asks the user first. REST: `POST /api/v1/bokio/journal-entries`. MCP: `bokio_write → create_journal_entry`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date` | string | yes | YYYY-MM-DD. |
| `title` | string | yes | Title of the entry. |
| `items` | array | yes | Rows with account, debit and credit; the sums of debit and credit must be equal. |

Books a manual journal entry. Debits must equal credits, and only accounts Bokio supports are accepted; look them up with list_accounts. The entry goes straight into the books. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "journal_entry_id": "9b3e61d4-27a8-4c15-b0f2-7d4a5e8c1f36",
  "date": "2026-10-25",
  "title": "Office rent October",
  "items": [
    {
      "account": "5010",
      "debit": 8000,
      "credit": 0
    },
    {
      "account": "1930",
      "debit": 0,
      "credit": 8000
    }
  ]
}
```

## How do I connect Bokio to Claude Code, Codex or Cursor?

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

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

2. **Sign in to Bokio in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Bokio 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 Bokio 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 are this week's billable jobs for Nordlys Design AB. Create one Bokio invoice with a line for each job, show me the total, and after I say OK publish it and email it to their finance address.
```

### Call Bokio 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/bokio 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/bokio/customers/c7a1e5d2-3b94-4f60-9a1d-5e2f0b8c6d11/invoices \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"currency":"SEK","invoice_date":"2026-10-14","due_date":"2026-11-13","lines":[{"description":"Website audit","quantity":8,"unit_price":1200,"tax_rate":25},{"description":"Hosting setup","quantity":1,"unit_price":900,"tax_rate":25}]}'
```

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

```
{
  "invoice_id": "f2d84b1a-6c30-4e97-8a5b-1d9c7e3a40b2",
  "status": "draft",
  "invoice_number": null,
  "customer": "Nordlys Design AB",
  "currency": "SEK",
  "invoice_date": "2026-10-14",
  "due_date": "2026-11-13",
  "total_amount": 13125,
  "total_tax": 2625
}
```

## Why use Cotlet for Bokio?

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

## Is it safe to connect Bokio to Cotlet?

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

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

## Is there a Bokio MCP server on GitHub?

Yes. Community Bokio MCP servers exist on GitHub, usually maintained by one person. You install one yourself, create a Bokio integration token and keep the server running; when the Bokio API changes, you or the maintainer fix it. Cotlet hosts the same kind of server for you, adds the one thing the API does not do (emailing an invoice from Bokio), and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, create an integration token under API Tokens, add it to each MCP client | Sign up, sign in to Bokio once, add one MCP server or API key |
| When Bokio 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 Bokio access | A long-lived token in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Several companies | One private token per company | The companies your Bokio user can open, with one key |
| 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 | 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 Bokio 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 Bokio API cost?

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

**Do I need to be technical?**

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

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

Bokio 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 Bokio plan do I need?**

Cotlet works in your own Bokio account and does not use the API, so it needs no API token or integration add-on. Creating and sending invoices needs invoicing in your plan: Bokio does not include it in Basic and sells it there as an add-on.

**Does the official API email the invoice?**

No. Bokio states that publishing an invoice through the API does not email it to the customer. send_invoice sends it from Bokio itself.

**Can my agent post or send messages in Bokio without asking me?**

No. Every call to publish_invoice, send_invoice, record_invoice_payment or create_journal_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_customer, create_invoice, upload_receipt runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Bokio 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/bokio 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.