Alegra MCP Server
Rechnungen, Kontakte und Zahlungen in Alegra.
Gehosteter MCP-Server
npx add-mcp 'https://cotlet.dev/mcp/v1/alegra'Installiert in Claude Code, Codex, Cursor und mehr
Dokumentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Alegra API and MCP server
Yes, Alegra has a REST API for invoices, contacts, payments and items (checked 14 Oct 2026). You call it with your account email and an API token, and Alegra Help says integrations need the Plus plan. Alegra also runs an official MCP server, but it is read-only: an agent can look up invoices and cannot create or send one.
Invoices, contacts and payments in Alegra. 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 Alegra. Alegra is a trademark of its owner. If Alegra's own integrations cover what you need, use them first.
Cloud accounting and invoicing software for small businesses and freelancers in Latin America, with sales invoices, contacts, products and services, payments and bank accounts in one account.
What is the Alegra API?
Cotlet's Alegra API exposes 10 endpoints for your own Alegra account: list invoices, get invoice, list contacts, list products and services, list bank accounts, list payments, create contact, create invoice, email invoice and record payment. The list_invoices endpoint returns sales invoices with number, client, dates, status, total and balance, filtered by status, client or due date. Each endpoint takes simple JSON inputs like cursor, limit or invoice_id and works both as an operation of the alegra_read or alegra_write MCP tool for agents and as a REST call for scripts.
- Category: Invoicing & freelance CRM
- Endpoints: 10 (6 read, 4 write)
- Updated: 2026-11-13
Yes, Alegra has a REST API for invoices, contacts, payments and items (checked 14 Oct 2026). Cotlet is a hosted MCP server and REST API for Alegra with 10 endpoints (6 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.
Does Alegra have an official API?
Yes, Alegra has a REST API for invoices, contacts, payments and items (checked 14 Oct 2026). You call it with your account email and an API token, and Alegra Help says integrations need the Plus plan. Alegra also runs an official MCP server, but it is read-only: an agent can look up invoices and cannot create or send one.
| Task | Alegra official | Cotlet |
|---|---|---|
| Create sales invoices | Yes: POST /invoices; Zapier has Create Invoice actions per country | Yes |
| Email an invoice to the client | Yes: POST /invoices/{id}/email takes the recipients and an optional subject | Yes |
| Record a payment on an invoice | Yes: POST /payments needs the date and the bank account ID | Yes |
| Create contacts | Yes: POST /contacts; Zapier also has Find or Create Contact | Yes |
| List unpaid invoices | Yes: GET /invoices filters by status and due date | Yes |
| List products and services | Yes: GET /items; the official MCP can read them too | Yes |
| Create and send invoices from an AI agent over MCP | No: The official MCP rejects any tool that is not get, list or search | Yes |
| Work without an API token or the Plus plan | No: The API and integrations need both | Yes |
Sources: Alegra Help: Alegra API, connect your account with other apps, Alegra developers: Authentication, Alegra developers: MCP server (read-only), Alegra triggers and actions on Zapier
Quick reference
Yes, Alegra has a REST API for invoices, contacts, payments and items (checked 14 Oct 2026). You call it with your account email and an API token, and Alegra Help says integrations need the Plus plan. Alegra also runs an official MCP server, but it is read-only: an agent can look up invoices and cannot create or send one.
Cotlet provides a hosted MCP server and REST API for Alegra: 10 tools (6 read, 4 write).
Access Sign up at https://cotlet.dev/app/signup?app=alegra 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 alegra_read, alegra_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base https://cotlet.dev/api/v1/alegra, each operation at its own route, e.g. POST /api/v1/alegra/contacts/{contact_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_contacts, list_items, list_bank_accounts, list_payments, create_contact, create_invoice, email_invoice, record_payment
Confirm create_contact, create_invoice, email_invoice, record_payment (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/alegra-api-mcp-server.md
How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=alegra and requests Alegra in the Cotlet console.
2. The user signs in to Alegra once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Alegra 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 Alegra 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 Alegra MCP server instead.
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 Alegra 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 Alegra 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 Alegra 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 Alegra's terms; Cotlet is not affiliated with Alegra.
What can an AI agent do in Alegra?
Cotlet is best for freelancers and small businesses on Alegra who want their AI agent to create and email invoices, record payments and chase unpaid ones without running or fixing a server.
- Create and email invoices from a job list (runs: weekly): "Here are this week's finished jobs with client, hours and rate. Create a draft sales invoice in Alegra for each client, due in 30 days, and show me the totals. After I say go, email each one to the contact on file." →
list_contacts,list_items,create_invoice,email_invoice - Chase unpaid invoices (runs: weekly): "List my open Alegra invoices that are past their due date. For each one, send the invoice again to the client's email with the subject "Reminder: invoice {number} is overdue" and send me a copy." →
list_invoices,get_invoice,email_invoice - Record bank payments on invoices (runs: daily): "Here are yesterday's incoming transfers from my bank statement. Match each one to an open Alegra invoice by client and amount, record the payment on the Bancolombia account, and list anything that does not match." →
list_invoices,list_bank_accounts,record_payment - Add new clients as contacts (runs: daily): "For each new customer in this list, check whether a contact with the same tax ID or email already exists in Alegra. Create the missing ones as clients and list the duplicates." →
list_contacts,create_contact - Weekly receivables summary (runs: weekly): "Every Monday, list open Alegra invoices grouped by client with the balance, and tell me which ones are past their due date." →
list_invoices,list_contacts
Can Alegra automations run on a schedule in n8n, Make or Zapier?
Yes. Cotlet does not replace your automation platform: it gives it a Alegra 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 email invoices from a job 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/alegra/contacts. | 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/alegra/contacts with your API key. | cron or GitHub Actions. |
Tools
For AI agents: Every endpoint and its schema is public. The 10 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 Alegra.
list_invoices
Sales invoices with number, client, dates, status, total and balance, filtered by status, client or due date. Access: read. REST: GET /api/v1/alegra/invoices. MCP: alegra_read → list_invoices.
| Parameter | Type | Required | Description |
|---|---|---|---|
status | enum | no | open, closed, draft or void. Several can be given, separated by commas. |
client_id | string | no | Only invoices of this contact. |
due_before | date | no | Only invoices due before this date, YYYY-MM-DD. |
date_from | date | no | Only invoices dated on or after this day, YYYY-MM-DD. |
date_to | date | no | Only invoices dated on or before this day, YYYY-MM-DD. |
limit | integer | no | Invoices per page. |
cursor | string | no | Next page cursor from the previous call. |
Lists sales invoices, newest page first as Alegra returns them. Status is one of open, closed, draft or void. Each item shows the total, the amount already paid and the balance, so overdue invoices can be told from paid ones. Pass next_cursor back as cursor for the next page.
Example response:
{
"invoices": [
{
"invoice_id": "1038",
"number": "FV-0038",
"client": {
"contact_id": "20",
"name": "Northwind Studio"
},
"date": "2026-09-15",
"due_date": "2026-09-30",
"status": "open",
"currency": "USD",
"total": 1130.5,
"total_paid": 0,
"balance": 1130.5
},
{
"invoice_id": "1035",
"number": "FV-0035",
"client": {
"contact_id": "27",
"name": "Lumen Dental"
},
"date": "2026-09-07",
"due_date": "2026-09-22",
"status": "open",
"currency": "USD",
"total": 571.2,
"total_paid": 0,
"balance": 571.2
}
],
"next_cursor": null
}
get_invoice
One invoice with its lines, taxes, payments and client details. Access: read. REST: GET /api/v1/alegra/invoices/{invoice_id}. MCP: alegra_read → get_invoice.
| Parameter | Type | Required | Description |
|---|---|---|---|
invoice_id | string | yes | Invoice ID from list_invoices. |
Returns one sales invoice with every line (item, quantity, price, tax), the totals, the payments already recorded and the client with the email Alegra holds. The numbering is shown as prefix and number. Fails with a not-found error when the invoice does not exist in your account.
Example response:
{
"invoice_id": "1038",
"number": "FV-0038",
"status": "open",
"date": "2026-09-15",
"due_date": "2026-09-30",
"currency": "USD",
"client": {
"contact_id": "20",
"name": "Northwind Studio",
"email": "accounts@northwind.example"
},
"items": [
{
"item_id": "12",
"name": "Landing page review",
"quantity": 2,
"price": 400,
"tax": "IVA 19%"
},
{
"item_id": "15",
"name": "Setup",
"quantity": 1,
"price": 150,
"tax": "IVA 19%"
}
],
"total": 1130.5,
"total_paid": 0,
"balance": 1130.5,
"payments": []
}
list_contacts
Clients and suppliers with name, tax ID, email and phone. Access: read. REST: GET /api/v1/alegra/contacts. MCP: alegra_read → list_contacts.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | no | Part of the name or the identification number. |
kind | enum | no | client or supplier. Default: both. |
limit | integer | no | Contacts per page. |
cursor | string | no | Next page cursor from the previous call. |
Lists contacts from the Contactos menu. Search matches the name or the identification number. A contact is a client, a supplier or both. Use contact_id from each item for create_invoice and list_invoices. Pass next_cursor back as cursor for the next page.
Example response:
{
"contacts": [
{
"contact_id": "20",
"name": "Northwind Studio",
"identification": "900123456",
"kind": "client",
"email": "accounts@northwind.example",
"mobile": "+57 300 555 0142",
"city": "Bogota"
}
],
"next_cursor": null
}
list_items
Products and services you can put on an invoice, with price and tax. Access: read. REST: GET /api/v1/alegra/items. MCP: alegra_read → list_items.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | no | Part of the name or the reference. |
limit | integer | no | Items per page. |
cursor | string | no | Next page cursor from the previous call. |
Lists your products and services with the default price and the tax each one carries. Use item_id as the item of an invoice line. A line may override the price, so the price here is the default only. Pass next_cursor back as cursor for the next page.
Example response:
{
"items": [
{
"item_id": "12",
"name": "Landing page review",
"reference": "LPR-01",
"price": 400,
"tax": {
"tax_id": "3",
"name": "IVA 19%"
}
},
{
"item_id": "15",
"name": "Setup",
"reference": "SET-01",
"price": 150,
"tax": {
"tax_id": "3",
"name": "IVA 19%"
}
}
],
"next_cursor": null
}
list_bank_accounts
Bank and cash accounts in Alegra with the ID needed to record a payment. Access: read. REST: GET /api/v1/alegra/bank-accounts. MCP: alegra_read → list_bank_accounts.
No parameters.
Returns the accounts a payment can be booked to, with name and type. Use bank_account_id from each item in record_payment. The list shows accounts only and no balances or transactions.
Example response:
{
"bank_accounts": [
{
"bank_account_id": "2",
"name": "Bancolombia",
"type": "bank"
},
{
"bank_account_id": "1",
"name": "Caja general",
"type": "cash"
}
]
}
list_payments
Payments received or made, with date, method, bank account and the invoices each one settled. Access: read. REST: GET /api/v1/alegra/payments. MCP: alegra_read → list_payments.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | enum | no | in (received) or out (paid out). |
client_id | string | no | Only payments of this contact. |
date_from | date | no | Only payments on or after this day, YYYY-MM-DD. |
date_to | date | no | Only payments on or before this day, YYYY-MM-DD. |
cursor | string | no | Next page cursor from the previous call. |
Lists payments as Alegra records them. Type in is money received from a client, type out is money paid out. Each item names the invoices it settled with the amount applied. Pass next_cursor back as cursor for the next page.
Example response:
{
"payments": [
{
"payment_id": "309",
"type": "in",
"date": "2026-10-13",
"payment_method": "transfer",
"bank_account": {
"bank_account_id": "2",
"name": "Bancolombia"
},
"client": "Lumen Dental",
"invoices": [
{
"invoice_id": "1033",
"number": "FV-0033",
"amount": 480
}
]
}
],
"next_cursor": null
}
create_contact
Add a client, a supplier or both to Contactos. Access: write, asks the user first. REST: POST /api/v1/alegra/contacts. MCP: alegra_write → create_contact.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | yes | Full name or company name. |
identification | string | no | Tax or identification number. |
kind | enum | no | client, supplier or both. Default: client. |
email | string | no | Address invoices are emailed to. |
mobile | string | no | Mobile number. |
city | string | no | City. |
address | string | no | Street address. |
Creates a contact the way + Nuevo Contacto does and returns its contact_id. It sends nothing to the person. Call list_contacts first: Alegra does not stop two contacts with the same name, and a duplicate has to be deleted by hand in Contactos. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"contact_id": "41",
"name": "Harbor Cafe",
"identification": "900765432",
"kind": "client",
"email": "billing@harborcafe.example",
"created": true
}
create_invoice
Create a sales invoice for a contact as a draft or an open invoice. Access: write, asks the user first. REST: POST /api/v1/alegra/contacts/{contact_id}/invoices. MCP: alegra_write → create_invoice.
| Parameter | Type | Required | Description |
|---|---|---|---|
contact_id | string | yes | Client contact ID from list_contacts. |
items | array | yes | Lines of the invoice. Each line has item_id from list_items, quantity and price, plus optional discount in percent without the % sign and tax_ids. |
date | date | yes | Invoice date, YYYY-MM-DD. |
due_date | date | yes | Due date, YYYY-MM-DD. |
status | enum | no | draft or open. Default: draft when nothing is paid. |
generate_stamp | boolean | no | true asks Alegra to stamp the invoice with your tax authority where your country requires it. Default: false. |
number_template_id | string | no | Numbering to use. Default: your preferred numbering. |
Creates a sales invoice with one or more lines and returns its ID, number, totals and status. With status draft nothing is issued and the invoice can still be edited in Alegra. With status open the invoice is saved as open, and with generate_stamp true Alegra also tries to stamp it with your tax authority; if stamping fails, the invoice stays a draft and the error is returned. The invoice is not emailed: use email_invoice for that. If you give no number_template_id, Alegra uses your preferred numbering. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"invoice_id": "1042",
"number": "FV-0042",
"status": "draft",
"date": "2026-10-20",
"due_date": "2026-11-19",
"currency": "USD",
"client": {
"contact_id": "20",
"name": "Northwind Studio"
},
"items": [
{
"item_id": "12",
"quantity": 2,
"price": 400,
"line_total": 800
},
{
"item_id": "15",
"quantity": 1,
"price": 150,
"line_total": 150
}
],
"subtotal": 950,
"tax_total": 180.5,
"total": 1130.5,
"balance": 1130.5
}
email_invoice
Send a sales invoice by email to one or more addresses. Access: write, asks the user first. REST: POST /api/v1/alegra/invoices/{invoice_id}/email. MCP: alegra_write → email_invoice.
| Parameter | Type | Required | Description |
|---|---|---|---|
invoice_id | string | yes | Invoice ID from list_invoices. |
emails | array | yes | Recipient addresses, even for one recipient. |
subject | string | no | Email subject. Default: the subject Alegra sets. |
send_copy_to_me | boolean | no | true also sends a copy to your own address. Default: false. |
as_copy | boolean | no | true sends the invoice marked as a copy. Default: false, the original. |
Sends the invoice through Alegra's invoice email, so the client receives the message of the template "Correo de envío de facturas de venta". Only the subject can be set per call; without one Alegra uses a default subject. The invoice goes out as the original unless as_copy is true. Fails with a not-found error when the invoice does not exist. Calling it twice sends two emails. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"invoice_id": "1038",
"sent_to": [
"accounts@northwind.example"
],
"subject": "Reminder: invoice FV-0038 is overdue",
"copy_sent_to_you": true,
"sent": true
}
record_payment
Record a payment received on one invoice, on a bank account, with date and method. Access: write, asks the user first. REST: POST /api/v1/alegra/invoices/{invoice_id}/payments. MCP: alegra_write → record_payment.
| Parameter | Type | Required | Description |
|---|---|---|---|
invoice_id | string | yes | Invoice ID from list_invoices. |
amount | number | yes | Amount received. |
date | date | yes | Payment date, YYYY-MM-DD. |
bank_account_id | string | yes | Account ID from list_bank_accounts. |
payment_method | enum | no | cash, check, transfer, deposit, credit-card or debit-card. |
Books a payment of amount against one invoice and returns the new total paid and balance. The method is cash, check, transfer, deposit, credit-card or debit-card, and Alegra needs the date and the bank account. A payment of the full balance leaves the invoice at zero. Alegra does not delete a payment that is wrong: it is voided and can be restored, and only a payment that is not reconciled can be deleted. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"payment_id": "311",
"invoice_id": "1042",
"number": "FV-0042",
"date": "2026-10-20",
"amount": 1130.5,
"payment_method": "transfer",
"bank_account": {
"bank_account_id": "2",
"name": "Bancolombia"
},
"total": 1130.5,
"total_paid": 1130.5,
"balance": 0
}
How do I connect Alegra to ChatGPT, Claude, Cursor or Codex?
Connecting Alegra takes three steps: sign up, sign in to Alegra 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 Alegra to your agent.
-
Create an account Sign up and add Alegra 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 Alegra in your Cloud Browser Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Alegra 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 Alegra 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 finished jobs with client, hours and rate. Create a draft sales invoice in Alegra for each client, due in 30 days, and show me the totals. After I say go, email each one to the contact on file.
Call Alegra 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/alegra 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/alegra/contacts/20/invoices \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"items":[{"item_id":"12","quantity":2,"price":400,"tax_ids":["3"]},{"item_id":"15","quantity":1,"price":150,"tax_ids":["3"]}],"date":"2026-10-20","due_date":"2026-11-19","status":"draft"}'
- Read the result You get plain JSON back, ready for your script. A failed call costs nothing.
{
"invoice_id": "1042",
"number": "FV-0042",
"status": "draft",
"date": "2026-10-20",
"due_date": "2026-11-19",
"currency": "USD",
"client": {
"contact_id": "20",
"name": "Northwind Studio"
},
"items": [
{
"item_id": "12",
"quantity": 2,
"price": 400,
"line_total": 800
},
{
"item_id": "15",
"quantity": 1,
"price": 150,
"line_total": 150
}
],
"subtotal": 950,
"tax_total": 180.5,
"total": 1130.5,
"balance": 1130.5
}
How to use the Alegra REST API
Create your Cotlet API key
Create a Cotlet API key with access to Alegra and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Alegra in Cotlet and enable it for agents. Account access: Your own Alegra account (a role that can use Ingresos and Contactos; no API token needed).
Make your first Alegra API request
REST:
curl "https://cotlet.dev/api/v1/alegra/invoices?limit=5" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read invoices 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": "alegra",
"tool": "list_invoices",
"result": {
"invoices": [
{
"invoice_id": "1038",
"number": "FV-0038",
"client": {
"contact_id": "20",
"name": "Northwind Studio"
},
"date": "2026-09-15",
"due_date": "2026-09-30",
"status": "open",
"currency": "USD",
"total": 1130.5,
"total_paid": 0,
"balance": 1130.5
},
{
"invoice_id": "1035",
"number": "FV-0035",
"client": {
"contact_id": "27",
"name": "Lumen Dental"
},
"date": "2026-09-07",
"due_date": "2026-09-22",
"status": "open",
"currency": "USD",
"total": 571.2,
"total_paid": 0,
"balance": 571.2
}
],
"next_cursor": null
}
}
Lists sales invoices, newest page first as Alegra returns them. Status is one of open, closed, draft or void.
Each item shows the total, the amount already paid and the balance, so overdue invoices can be told from paid ones. Pass next_cursor back as cursor for the next page.
limit: Invoices per page.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Alegra workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | One invoice with its lines, taxes, payments and client details. Use get_invoice in your configured operations sheet. |
| Make | HTTP > Make a request | Clients and suppliers with name, tax ID, email and phone. Use list_contacts in your configured operations sheet. |
| Python or Node.js | REST API | Payments received or made, with date, method, bank account and the invoices each one settled. Use list_payments 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 Alegra; 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 Alegra?
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 Alegra 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 Alegra changes, the tool pauses until we fix it.
- Failed calls cost nothing.
Is it safe to connect Alegra to Cotlet?
Yes. You sign in to Alegra yourself, in your own Cloud Browser, and we never save your password. Your agents only get Alegra 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 Alegra integration?
No, Cotlet is independent of Alegra. Alegra's own API comes only with a paid plan. Cotlet works through your own Alegra account, the way you use Alegra 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 Alegra in your console: your agents lose access at once and you stay signed in. Signing out of Alegra in the browser works too, and Reset browser deletes the whole profile.
Is there a Alegra MCP server on GitHub?
Yes. Open-source Alegra MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it your Alegra API token and keep it running yourself; when Alegra changes its API, you or the maintainer fix it. Alegra's own MCP server only reads. The official API route works too, but you write and host the code. Cotlet hosts a server with the same tools for you, adds a REST API, and our team keeps it working.
| GitHub MCP server | Cotlet | |
|---|---|---|
| Setup | Clone the repo, install it, create an Alegra API token, add the server to each MCP client | Sign up, sign in to Alegra once, add one MCP server or API key |
| Alegra plan | Needs a plan with integrations and an API token | Works in your own account, through the screens you already use |
| Your Alegra access | A token in a file or environment variable on your computer, with access to the whole account | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When Alegra changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| 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 Alegra 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 Alegra API cost?
Free 7-day trial with 2,000 credits, no card needed. After that, the Alegra 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 Alegra 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 Alegra 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 Alegra only after you enable it. When Alegra signs you out, your agent gives you a link to sign in again. Security
- Revoking access: Press Disable for agents next to Alegra, sign out of Alegra 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.
- Alegra's terms: You use your own Alegra account and stay responsible for following Alegra's terms. Cotlet is independent and not affiliated with Alegra. Terms
- Contact: Questions about the company, security or an app: contact@cotlet.dev
Alegra API and MCP: questions
How do I get access?
Sign up free, open Alegra in the console and press Activate. Then you create your API key and connect Alegra there.
Do I need to be technical?
No. You sign in to Alegra 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 Alegra to Cotlet?
Yes. You sign in to Alegra yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Alegra 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 Alegra 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 Alegra 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 Alegra's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Alegra 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 Alegra 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?
Alegra 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 Alegra to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Alegra 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 Alegra account through Cotlet, in their phone apps too.
What can ChatGPT do in Alegra?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Alegra: create and email invoices from a job list; chase unpaid invoices; record bank payments on invoices. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need the Plus plan or an API token for Cotlet?
No. Cotlet signs in to your own Alegra account and uses the screens you already use, so it needs neither the API token nor the Plus plan that Alegra Help requires for integrations. It can only do what your plan and your role allow on screen.
Does it work for invoices in my country?
Alegra's invoice form differs by country: Zapier lists separate create-invoice actions for Argentina, Chile, Colombia, Costa Rica, Mexico, Panama and Peru. Start with status draft, check the draft in Alegra, and only then open or stamp it. A stamped invoice is sent to your tax authority, which is why every invoice tool asks for your OK by default.
Can my agent post or send messages in Alegra without asking me?
No. Every call to create_contact, create_invoice, email_invoice or record_payment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.
Can I use the Alegra 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/alegra from the HTTP Request node.
Can I use the Alegra 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.