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

# Fakturownia (InvoiceOcean) API and MCP server

> Yes. Fakturownia has a documented REST API that creates invoices, clients and payments, sends invoices by email and sends them to KSeF (checked 14 Oct 2026). Its official MCP server is read-only, so an agent cannot issue, send or pay anything through it. Every write needs a raw API token that you create in your account settings and keep yourself, per account.

Online invoicing for small businesses, sold in Poland as Fakturownia and abroad as InvoiceOcean: sales and cost invoices, clients, products, payments and sending invoices to the Polish KSeF e-invoicing system.

## What is the Fakturownia (InvoiceOcean) API?

Cotlet's Fakturownia (InvoiceOcean) API exposes 14 endpoints for your own Fakturownia (InvoiceOcean) account: list invoices, get invoice, list clients, list products, list payments, get invoice PDF, get KSeF status, create client, create invoice, send invoice by email, mark invoice paid, record payment, send invoice to KSeF and cancel invoice. The list_invoices endpoint returns sales or cost invoices for a period, with status, totals and due date. Each endpoint takes simple JSON inputs like invoice_id, page or name and works both as an operation of the fakturownia_read or fakturownia_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:** 14 (7 read, 7 write)
- **Updated:** 2026-10-20

Yes. Cotlet is a hosted MCP server and REST API for Fakturownia (InvoiceOcean) with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Fakturownia (InvoiceOcean) have an official API?

Yes. Fakturownia has a documented REST API that creates invoices, clients and payments, sends invoices by email and sends them to KSeF (checked 14 Oct 2026). Its official MCP server is read-only, so an agent cannot issue, send or pay anything through it. Every write needs a raw API token that you create in your account settings and keep yourself, per account.

| Task | Fakturownia (InvoiceOcean) official | Cotlet |
|---|---|---|
| List and read invoices | Yes: Paginated, up to 100 per page; the official MCP reads too | Yes |
| Create an invoice | Yes: POST /invoices.json with an API token | Yes |
| Send an invoice by email | Yes: With KSeF on, the app emails an invoice only after it has a KSeF number | Yes |
| Mark an invoice paid or record a payment | Yes: change_status and banking payments | Yes |
| Add a client | Yes | Yes |
| Download an invoice PDF | Yes | Yes |
| Send an invoice to KSeF and read its status | Yes: KSeF must already be connected in the account | Yes |
| Cancel an invoice | Yes: Cancelling cannot be undone in the app | Yes |

Sources: [Fakturownia API documentation (GitHub)](https://github.com/fakturownia/api), [Fakturownia API: KSeF integration guide](https://github.com/fakturownia/api/blob/master/KSeF.md), [Fakturownia: AI assistant over MCP (read-only)](https://fakturownia.pl/asystent-ai-mcp), [InvoiceOcean pricing (API on every plan)](https://www.invoiceocean.com/pricing)

## For AI agents

```text
Yes. Fakturownia has a documented REST API that creates invoices, clients and payments, sends invoices by email and sends them to KSeF (checked 14 Oct 2026). Its official MCP server is read-only, so an agent cannot issue, send or pay anything through it. Every write needs a raw API token that you create in your account settings and keep yourself, per account.
Cotlet provides a hosted MCP server and REST API for Fakturownia (InvoiceOcean): 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=fakturownia, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    fakturownia_read, fakturownia_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/fakturownia, each operation at its own route, e.g. POST /api/v1/fakturownia/clients/{client_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_clients, list_products, list_payments, get_invoice_pdf, get_ksef_status, create_client, create_invoice, send_invoice_email, mark_invoice_paid, record_payment, send_invoice_to_ksef, cancel_invoice
Confirm      create_invoice, send_invoice_email, mark_invoice_paid, record_payment, send_invoice_to_ksef, cancel_invoice (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/fakturownia-api-mcp-server.md

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

## What can an AI agent do in Fakturownia (InvoiceOcean)?

Cotlet is best for freelancers and small businesses on Fakturownia or InvoiceOcean who want their AI agent to issue invoices, record payments and send to KSeF without running or fixing a server.

- **[Issue an invoice from a deal or message](https://cotlet.dev/integrations/fakturownia-api-mcp-server/issue-invoice-from-deal.md)** (runs: daily): "Issue a VAT invoice in Fakturownia for Blue Fern Studio: 2 x Website retainer from my product list, payment due in 14 days. Find the client first and add it if it is missing. Show me the invoice before you save it." → `list_clients`, `create_client`, `list_products`, `create_invoice`
- **[Record payments and mark invoices paid](https://cotlet.dev/integrations/fakturownia-api-mcp-server/record-invoice-payments.md)** (runs: weekly): "Here is this week's bank export. For each incoming transfer find the unpaid Fakturownia invoice with the same number in the title and amount, record the payment, and list what did not match." → `list_invoices`, `list_payments`, `record_payment`, `mark_invoice_paid`
- **[Send invoices to KSeF](https://cotlet.dev/integrations/fakturownia-api-mcp-server/send-invoices-to-ksef.md)** (runs: daily): "Check Fakturownia for invoices issued today that are not in KSeF. For each one for a Polish company, show me the buyer and the total, and send it to KSeF after I approve. Report any that come back with an error." → `list_invoices`, `get_ksef_status`, `send_invoice_to_ksef`
- **Weekly unpaid and overdue invoices report** (runs: weekly): "Every Monday, list my unpaid Fakturownia sales invoices, group them by client and show who is past the due date and by how many days." → `list_invoices`, `get_invoice`
- **Email invoices to clients after approval** (runs: daily): "Send every issued but unsent Fakturownia invoice to its client by email with the PDF attached, after I confirm the list." → `list_invoices`, `send_invoice_email`

## Can Fakturownia (InvoiceOcean) automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Fakturownia (InvoiceOcean) connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to issue an invoice from a deal or message, 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/fakturownia/clients. | 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/fakturownia/clients with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 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 Fakturownia (InvoiceOcean).

### list_invoices

Sales or cost invoices for a period, with status, totals and due date. Access: read. REST: `GET /api/v1/fakturownia/invoices`. MCP: `fakturownia_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `period` | string | no | this_month, last_30_days, last_month, this_year, last_year, last_12_months, all or more. Default: this_month. |
| `date_from` | string | no | YYYY-MM-DD. Needed when period is more. |
| `date_to` | string | no | YYYY-MM-DD. Needed when period is more. |
| `status` | string | no | Keep only invoices with this status: issued, sent, partial, paid or rejected. |
| `kind` | string | no | Document kind, for example vat, proforma, advance, correction, estimate. |
| `income` | boolean | no | false returns cost invoices. Default: true. |
| `client_id` | integer | no | Only invoices of this client, from list_clients. |
| `page` | integer | no | Page number. Default: 1. |
| `per_page` | integer | no | 1 to 100. Default: the app default. |

Returns invoices for the period you choose, newest issue date first unless you set order. Each item has number, kind, status, buyer, net, VAT and gross totals, due date and paid amount. Fakturownia pages results at up to 100 per page. Set income to false for cost invoices.

Example response:

```json
{
  "invoices": [
    {
      "id": 5120,
      "number": "14/10/2026/1",
      "kind": "vat",
      "status": "issued",
      "buyer_name": "Blue Fern Studio",
      "price_net": "1000.00",
      "price_tax": "230.00",
      "price_gross": "1230.00",
      "currency": "PLN",
      "issue_date": "2026-10-14",
      "payment_to": "2026-10-28",
      "paid": "0.00"
    },
    {
      "id": 5104,
      "number": "09/10/2026/3",
      "kind": "vat",
      "status": "partial",
      "buyer_name": "Harbor Print Ltd",
      "price_net": "650.41",
      "price_tax": "149.59",
      "price_gross": "800.00",
      "currency": "PLN",
      "issue_date": "2026-10-09",
      "payment_to": "2026-10-23",
      "paid": "500.00"
    }
  ],
  "page": 1
}
```

### get_invoice

One invoice with its line items, buyer, payments and KSeF fields. Access: read. REST: `GET /api/v1/fakturownia/invoices/{invoice_id}`. MCP: `fakturownia_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | yes | Invoice ID from list_invoices. |

Returns one invoice with its positions, buyer and seller data, status and the payments linked to it. When KSeF is on for the account, it also returns gov_status and the KSeF number.

Example response:

```json
{
  "id": 5120,
  "number": "14/10/2026/1",
  "kind": "vat",
  "status": "issued",
  "buyer_name": "Blue Fern Studio",
  "client_id": 4817,
  "positions": [
    {
      "name": "Website retainer",
      "quantity": 2,
      "tax": "23",
      "total_price_gross": "1230.00"
    }
  ],
  "price_net": "1000.00",
  "price_tax": "230.00",
  "price_gross": "1230.00",
  "currency": "PLN",
  "payment_to": "2026-10-28",
  "paid": "0.00",
  "gov_status": null
}
```

### list_clients

Clients, searchable by name, email, short name or tax number. Access: read. REST: `GET /api/v1/fakturownia/clients`. MCP: `fakturownia_read → list_clients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | no | Client name. |
| `tax_no` | string | no | Tax number (NIP). |
| `email` | string | no | Client email address. |
| `shortcut` | string | no | Short name of the client. |
| `page` | integer | no | Page number. Default: 1. |

Returns clients from your Fakturownia client list. Pass one search field to find a buyer before you invoice them. Without a filter it returns the first page of all clients.

Example response:

```json
{
  "clients": [
    {
      "id": 4817,
      "name": "Blue Fern Studio",
      "tax_no": "1234563218",
      "email": "billing@bluefern.example",
      "city": "Gdansk",
      "country": "PL",
      "company": true
    }
  ],
  "page": 1
}
```

### list_products

Your product and service list with price, VAT rate and unit. Access: read. REST: `GET /api/v1/fakturownia/products`. MCP: `fakturownia_read → list_products`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `page` | integer | no | Page number. Default: 1. |
| `per_page` | integer | no | 1 to 100. Default: the app default. |

Returns the products and services saved in your account. Use the id as product_id in create_invoice so the VAT rate and unit come from your own list.

Example response:

```json
{
  "products": [
    {
      "id": 2203,
      "name": "Website retainer",
      "price_net": "500.00",
      "tax": "23",
      "unit": "month"
    }
  ],
  "page": 1
}
```

### list_payments

Payments recorded in Fakturownia, with the invoices they cover. Access: read. REST: `GET /api/v1/fakturownia/payments`. MCP: `fakturownia_read → list_payments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `include_invoices` | boolean | no | Include the invoices each payment is linked to. |
| `page` | integer | no | Page number. Default: 1. |

Returns payments recorded in the account. Set include_invoices to see which invoices each payment is attached to, so a transfer is not booked twice.

Example response:

```json
{
  "payments": [
    {
      "id": 9031,
      "name": "Transfer 2026-10-09 Harbor Print",
      "price": "500.00",
      "paid": true,
      "invoice_ids": [
        5104
      ]
    }
  ],
  "page": 1
}
```

### get_invoice_pdf

The invoice as a PDF file, base64 encoded. Access: read. REST: `GET /api/v1/fakturownia/invoices/{invoice_id}/pdf`. MCP: `fakturownia_read → get_invoice_pdf`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | yes | Invoice ID from list_invoices. |

Returns the PDF of one invoice as base64 with its file name. For an invoice sent to KSeF, the PDF shows the KSeF number, verification link and QR code.

Example response:

```json
{
  "invoice_id": 5120,
  "file_name": "14-10-2026-1.pdf",
  "content_base64": "JVBERi0xLjQKJcfsj6IK..."
}
```

### get_ksef_status

Where an invoice stands in KSeF: not sent, processing, accepted or an error. Access: read. REST: `GET /api/v1/fakturownia/invoices/{invoice_id}/ksef-status`. MCP: `fakturownia_read → get_ksef_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | yes | Invoice ID from list_invoices. |

Returns gov_status, the KSeF number once there is one, the send date and error messages for one invoice. Statuses include ok, processing, send_error, server_error, offline and not_connected. A null status means the invoice was not sent.

Example response:

```json
{
  "invoice_id": 5120,
  "gov_status": "ok",
  "gov_id": "1234563218-20261014-A1B2C3D4E5F6",
  "gov_send_date": "2026-10-14T10:30:00+02:00",
  "gov_error_messages": null
}
```

### create_client

Add a client to your Fakturownia client list. Access: write. REST: `POST /api/v1/fakturownia/clients`. MCP: `fakturownia_write → create_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Client name. |
| `tax_no` | string | no | Tax number (NIP). |
| `email` | string | no | Email address for sending invoices. |
| `street` | string | no | Street and number. |
| `post_code` | string | no | Postal code. |
| `city` | string | no | City. |
| `country` | string | no | Country code. |
| `company` | boolean | no | false for a private person. Default: true. |
| `last_name` | string | no | Needed when company is false. |

Creates a client record. Only name is required. A private person needs company set to false and a last name. Nothing is sent to anyone and the client can be edited or deleted in the app, so create_client runs without asking first.

Example response:

```json
{
  "id": 4832,
  "name": "Harbor Print Ltd",
  "tax_no": "7654321098",
  "email": "office@harborprint.example",
  "company": true
}
```

### create_invoice

Issue an invoice for a client with products or free lines. Access: write, asks the user first. REST: `POST /api/v1/fakturownia/clients/{client_id}/invoices`. MCP: `fakturownia_write → create_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | integer | yes | Client ID from list_clients or create_client. |
| `positions` | array | yes | Lines: {product_id, quantity}, or {name, tax, quantity, total_price_gross}. |
| `kind` | string | no | vat, proforma, advance, final, estimate, bill or receipt. Default: vat. |
| `payment_to_kind` | integer | no | Days until due. Use payment_to for a fixed date. |
| `payment_to` | string | no | YYYY-MM-DD due date. |
| `issue_date` | string | no | YYYY-MM-DD. Default: today. |
| `sell_date` | string | no | YYYY-MM-DD or YYYY-MM. Default: issue date. |
| `department_id` | integer | no | Company or department that issues the invoice. |

Saves an invoice with the next number in your series. Lines use product_id and quantity, or name, tax, quantity and total_price_gross. Without department_id it uses your default company data. If automatic KSeF sending is on for this account, saving also sends the invoice to KSeF, which is legally binding. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "id": 5120,
  "number": "14/10/2026/1",
  "kind": "vat",
  "status": "issued",
  "client_id": 4817,
  "price_net": "1000.00",
  "price_tax": "230.00",
  "price_gross": "1230.00",
  "currency": "PLN",
  "payment_to": "2026-10-28",
  "gov_status": null
}
```

### send_invoice_email

Email an invoice to the client, with the PDF attached. Access: write, asks the user first. REST: `POST /api/v1/fakturownia/invoices/{invoice_id}/email`. MCP: `fakturownia_write → send_invoice_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | yes | Invoice ID from list_invoices. |
| `email_to` | array | no | Up to 5 recipient addresses. Default: the client email. |
| `email_cc` | array | no | Addresses in copy. |
| `email_pdf` | boolean | no | Attach the PDF. Default: true. |
| `update_buyer_email` | boolean | no | Save email_to as the client email. |

Emails one invoice to up to 5 addresses, with the PDF attached when email_pdf is true. With KSeF on, Fakturownia emails an invoice only after it has a KSeF number. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": 5120,
  "status": "sent",
  "email_to": [
    "billing@bluefern.example"
  ],
  "email_pdf": true
}
```

### mark_invoice_paid

Set an invoice status, for example paid, without recording a transfer. Access: write, asks the user first. REST: `POST /api/v1/fakturownia/invoices/{invoice_id}/paid/mark`. MCP: `fakturownia_write → mark_invoice_paid`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | yes | Invoice ID from list_invoices. |
| `status` | string | no | issued, sent, paid, partial or rejected. Default: paid. |

Changes the status of one invoice. Setting paid also sets the payment date, and for cash VAT invoices it settles the VAT on that day. Use record_payment when there is a transfer to record. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": 5120,
  "status": "paid",
  "paid_date": "2026-10-14"
}
```

### record_payment

Record a payment and attach it to one or more invoices. Access: write, asks the user first. REST: `POST /api/v1/fakturownia/payments`. MCP: `fakturownia_write → record_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Payment name, for example the transfer title. |
| `price` | number | yes | Amount received. |
| `invoice_ids` | array | yes | Invoice IDs from list_invoices, paid in this order. |
| `paid` | boolean | no | Default: true. |

Adds a payment and links it to the invoices in invoice_ids, which are paid in the order given: the first in full, the next with what is left. Fakturownia then sets paid or partial. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "id": 9040,
  "name": "Transfer 2026-10-14 Blue Fern Studio",
  "price": "1230.00",
  "paid": true,
  "invoice_ids": [
    5120
  ]
}
```

### send_invoice_to_ksef

Send one invoice to the Polish KSeF e-invoicing system. Access: write, asks the user first. REST: `POST /api/v1/fakturownia/invoices/{invoice_id}/to-ksef`. MCP: `fakturownia_write → send_invoice_to_ksef`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | yes | Invoice ID from list_invoices. |

Sends the invoice to KSeF and returns processing; the KSeF number appears after processing, so read it with get_ksef_status. KSeF must already be connected in the account, and your user needs send permission. Proformas are not eligible. Invoices sent after their issue day go offline24 and cannot be edited. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": 5120,
  "gov_status": "processing",
  "gov_id": null
}
```

### cancel_invoice

Cancel an issued invoice with a reason. Cannot be undone. Access: write, asks the user first. REST: `POST /api/v1/fakturownia/cancel-invoices/{cancel_invoice_id}/invoice/cancel`. MCP: `fakturownia_write → cancel_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `cancel_invoice_id` | integer | yes | Invoice ID from list_invoices. |
| `cancel_reason` | string | no | Reason shown on the cancelled document. |

Cancels the invoice and records the reason at the top of the document. The newest document in the list cannot be cancelled, only deleted in the app, and receipts cannot be cancelled. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": 5104,
  "status": "cancelled",
  "cancel_reason": "Issued to the wrong client"
}
```

## How do I connect Fakturownia (InvoiceOcean) to Claude Code, Codex or Cursor?

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

1. **Create an account** Sign up and add Fakturownia (InvoiceOcean) in the console. Your API key is there too.

2. **Sign in to Fakturownia (InvoiceOcean) in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Fakturownia (InvoiceOcean) 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 Fakturownia (InvoiceOcean) tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Issue a VAT invoice in Fakturownia for Blue Fern Studio: 2 x Website retainer from my product list, payment due in 14 days. Find the client first and add it if it is missing. Show me the invoice before you save it.
```

### Call Fakturownia (InvoiceOcean) 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/fakturownia 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/fakturownia/clients/4817/invoices \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"vat","payment_to_kind":14,"positions":[{"product_id":2203,"quantity":2}]}'
```

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

```
{
  "id": 5120,
  "number": "14/10/2026/1",
  "kind": "vat",
  "status": "issued",
  "client_id": 4817,
  "price_net": "1000.00",
  "price_tax": "230.00",
  "price_gross": "1230.00",
  "currency": "PLN",
  "payment_to": "2026-10-28",
  "gov_status": null
}
```

## Why use Cotlet for Fakturownia (InvoiceOcean)?

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

## Is it safe to connect Fakturownia (InvoiceOcean) to Cotlet?

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

No, Cotlet is independent of Fakturownia (InvoiceOcean). Fakturownia (InvoiceOcean)'s own API is too limited for this work. Cotlet works through your own Fakturownia (InvoiceOcean) account, the way you use Fakturownia (InvoiceOcean) 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 Fakturownia (InvoiceOcean) in your console: your agents lose access at once and you stay signed in. Signing out of Fakturownia (InvoiceOcean) in the browser works too, and Reset browser deletes the whole profile.

## Is there a Fakturownia (InvoiceOcean) MCP server on GitHub?

Yes. Community Fakturownia MCP servers exist, usually maintained by one person. You install one on your own computer, give it your API token, and keep it running yourself; when the API changes, it stops working until you or the maintainer fix it. The official API is the other route: free to call, but you write and host the code. Cotlet hosts the same tools for you, with one key and one sign-in, and our team keeps them working.

|  | GitHub MCP server or the API | Cotlet |
|---|---|---|
| Setup | Create an API token in Settings, install the server or write the calls, add it to each MCP client | Sign up, sign in to Fakturownia once, add one MCP server or API key |
| When Fakturownia 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 Fakturownia access | An API token with account-wide rights, kept in a config 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; no token to paste |
| Several accounts | One token and one subdomain to track per account | Sign in to each account once; the agent picks it by name |
| 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 Fakturownia (InvoiceOcean) 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 Fakturownia (InvoiceOcean) API cost?

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

**Do I need to be technical?**

No. You sign in to Fakturownia (InvoiceOcean) 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 Fakturownia (InvoiceOcean) to Cotlet?**

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

Fakturownia (InvoiceOcean) 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 an API token or a paid plan?**

No token. Cotlet works from your own signed-in account, and sending to KSeF needs the owner, administrator or "Wysyłanie do KSeF" permission. InvoiceOcean lists API access on all four plans, including Free; Fakturownia.pl does not list API access by plan on its pages.

**Can my agent send an invoice to KSeF?**

Yes, if KSeF is already connected in your account. send_invoice_to_ksef sends one invoice after your OK, and get_ksef_status returns the KSeF number or the error. Fakturownia sends automatically only for the buyer groups chosen in its KSeF settings, so foreign companies still need a manual send.

**Can my agent post or send messages in Fakturownia (InvoiceOcean) without asking me?**

No. Every call to create_invoice, send_invoice_email, mark_invoice_paid, record_payment, send_invoice_to_ksef or cancel_invoice 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_client runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Fakturownia (InvoiceOcean) 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/fakturownia 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.