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

# Odoo API and MCP server

> Yes, Odoo has an external API, but on Odoo Online it is only available on the Custom plan, not on One App Free or Standard (checked 14 Oct 2026). It is a full read and write API (JSON-2 since Odoo 19, XML-RPC and JSON-RPC deprecated), authenticated with an API key per user. Odoo's documentation also describes a built-in MCP server in its development version; its tool list has generic Create Records and Update Records and no tool that posts, sends or pays an invoice.

Open-source business suite with Accounting, Invoicing, Sales and CRM apps in one database; each company works in its own Odoo instance, hosted by Odoo Online, Odoo.sh or on its own server.

## What is the Odoo API?

Cotlet's Odoo API exposes 12 endpoints for your own Odoo account: list customer invoices, get an invoice, list contacts, list payment journals, list quotations and sales orders, create a contact, create a draft invoice, confirm (post) an invoice, send an invoice, register a payment, create a credit note and create a quotation. The list_invoices endpoint returns list customer invoices with status, amount due and due date, with filters. Each endpoint takes simple JSON inputs like invoice_id, contact_id or limit and works both as an operation of the odoo_read or odoo_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:** 12 (5 read, 7 write)
- **Updated:** 2026-10-18

Yes, Odoo has an external API, but on Odoo Online it is only available on the Custom plan, not on One App Free or Standard (checked 14 Oct 2026). Cotlet is a hosted MCP server and REST API for Odoo with 12 endpoints (5 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Odoo have an official API?

Yes, Odoo has an external API, but on Odoo Online it is only available on the Custom plan, not on One App Free or Standard (checked 14 Oct 2026). It is a full read and write API (JSON-2 since Odoo 19, XML-RPC and JSON-RPC deprecated), authenticated with an API key per user. Odoo's documentation also describes a built-in MCP server in its development version; its tool list has generic Create Records and Update Records and no tool that posts, sends or pays an invoice.

| Task | Odoo official | Cotlet |
|---|---|---|
| List invoices and filter unpaid ones | Yes: Custom plan; read any model through the API | Yes |
| Create a draft customer invoice | Yes: Custom plan; create on the invoice model | Yes |
| Confirm (post) an invoice | Partly: Needs the right model method called by name; the MCP tool list has no posting tool | Yes |
| Send an invoice by email | Partly: Same: a model method you call yourself, not an MCP tool | Yes |
| Register a payment on an invoice | Partly: Custom plan; done through the payment wizard methods, not a single call | Yes |
| Create a contact | Yes: Custom plan; create on the contact model | Yes |
| Create a quotation or sales order | Yes: Custom plan; create on the sales order model | Yes |
| Issue a credit note | Partly: Custom plan; reversal methods called by name | Yes |

Sources: [Odoo documentation: External API](https://www.odoo.com/documentation/18.0/developer/reference/external_api.html), [Odoo documentation: External RPC API (RPC endpoints deprecated since 19.0)](https://www.odoo.com/documentation/20.0/developer/reference/external_rpc_api.html), [Odoo documentation: AI MCP server, available MCP tools](https://www.odoo.com/documentation/master/applications/productivity/ai/mcp_server/mcp_tools.html), [Odoo pricing plans](https://www.odoo.com/pricing-plan)

## For AI agents

```text
Yes, Odoo has an external API, but on Odoo Online it is only available on the Custom plan, not on One App Free or Standard (checked 14 Oct 2026). It is a full read and write API (JSON-2 since Odoo 19, XML-RPC and JSON-RPC deprecated), authenticated with an API key per user. Odoo's documentation also describes a built-in MCP server in its development version; its tool list has generic Create Records and Update Records and no tool that posts, sends or pays an invoice.
Cotlet provides a hosted MCP server and REST API for Odoo: 12 tools (5 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=odoo, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    odoo_read, odoo_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/odoo, each operation at its own route, e.g. POST /api/v1/odoo/invoices/{invoice_id}/payments
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_payment_journals, list_sales_orders, create_contact, create_draft_invoice, post_invoice, send_invoice, register_payment, create_credit_note, create_sales_order
Confirm      post_invoice, send_invoice, register_payment, create_credit_note (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/odoo-api-mcp-server.md

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

## What can an AI agent do in Odoo?

Cotlet is best for small finance teams and freelancers on Odoo who want an agent to create, send and settle customer invoices without running or fixing a server.

- **[Chase overdue customer invoices](https://cotlet.dev/integrations/odoo-api-mcp-server/chase-overdue-invoices.md)** (runs: weekly): "List the customer invoices in Odoo that are posted, unpaid and past their due date. For each one older than 14 days, resend the invoice by email and give me a list of what you sent, sorted by amount." → `list_invoices`, `get_invoice`, `send_invoice`
- **[Record customer payments against invoices](https://cotlet.dev/integrations/odoo-api-mcp-server/register-invoice-payments.md)** (runs: daily): "Here are today's bank receipts: Northwind Studio 3,200.00 EUR for INV/2026/00412 and Harbor Print 2,150.00 EUR for INV/2026/00398. Find each invoice in Odoo and register the payment on my Bank journal, dated today." → `get_invoice`, `list_payment_journals`, `register_payment`
- **[Create monthly customer invoices from a list](https://cotlet.dev/integrations/odoo-api-mcp-server/create-invoices-from-a-list.md)** (runs: monthly): "Create a draft customer invoice in Odoo for each client in this list with the retainer amount next to their name. Add missing clients as contacts first. Show me the drafts, and post and send them only after I say so." → `list_contacts`, `create_contact`, `create_draft_invoice`, `post_invoice`, `send_invoice`
- **Add new customers as contacts**: "For each new customer in this list, check whether Odoo already has a contact with that email. If not, create the contact with name, email, phone and company." → `list_contacts`, `create_contact`
- **Turn an accepted quote into a draft quotation**: "Create a quotation in Odoo for Harbor Print with 10 hours of consulting at 120.00 each, and show me the total before anything is sent." → `list_contacts`, `create_sales_order`, `list_sales_orders`

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

Yes. Cotlet does not replace your automation platform: it gives it a Odoo 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 chase overdue customer invoices, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/odoo/invoices. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/odoo/invoices with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Odoo.

### list_invoices

List customer invoices with status, amount due and due date, with filters. Access: read. REST: `GET /api/v1/odoo/invoices`. MCP: `odoo_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | draft, posted or cancel. Default: all. |
| `payment_status` | enum | no | not_paid, in_payment or paid. Default: all. |
| `overdue` | boolean | no | true: only invoices whose due date is before today. |
| `contact_id` | integer | no | Only invoices of this contact. |
| `invoice_date_from` | date | no | Only invoices dated on or after this date. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `offset` | integer | no | Number of records to skip, for the next page. Default: 0. |

Returns customer invoices, newest first, with the invoice number, contact, dates, total and amount still due. Drafts have no number yet. Pages hold up to 100 invoices; pass offset to read on. You see the invoices your Odoo user can see, in the company you are signed in to.

Example response:

```json
{
  "items": [
    {
      "invoice_id": 4182,
      "number": "INV/2026/00412",
      "contact": "Northwind Studio",
      "status": "posted",
      "payment_status": "not_paid",
      "invoice_date": "2026-09-13",
      "due_date": "2026-09-27",
      "amount_total": 3200,
      "amount_due": 3200,
      "currency": "EUR"
    },
    {
      "invoice_id": 4151,
      "number": "INV/2026/00398",
      "contact": "Harbor Print",
      "status": "posted",
      "payment_status": "not_paid",
      "invoice_date": "2026-09-22",
      "due_date": "2026-10-06",
      "amount_total": 2150,
      "amount_due": 2150,
      "currency": "EUR"
    }
  ],
  "total": 2
}
```

### get_invoice

Read one customer invoice with its lines, contact email and status. Access: read. REST: `GET /api/v1/odoo/invoice`. MCP: `odoo_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | no | Invoice ID from list_invoices. |
| `number` | string | no | Invoice number such as INV/2026/00412, instead of invoice_id. |

Returns the invoice header, every line with quantity, unit price and subtotal, the contact's email address and the payment status. Pass either invoice_id or number. A draft has no number. The call fails with a not-found error if your Odoo user cannot see the invoice.

Example response:

```json
{
  "invoice_id": 4182,
  "number": "INV/2026/00412",
  "contact": {
    "contact_id": 931,
    "name": "Northwind Studio",
    "email": "billing@northwind.example"
  },
  "status": "posted",
  "payment_status": "not_paid",
  "invoice_date": "2026-09-13",
  "due_date": "2026-09-27",
  "lines": [
    {
      "description": "Monthly retainer, September",
      "quantity": 1,
      "unit_price": 3200,
      "subtotal": 3200
    }
  ],
  "amount_untaxed": 3200,
  "amount_tax": 0,
  "amount_total": 3200,
  "amount_due": 3200,
  "currency": "EUR"
}
```

### list_contacts

Search contacts (customers and vendors) by name, email or company. Access: read. REST: `GET /api/v1/odoo/contacts`. MCP: `odoo_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Text to match against name or email. |
| `is_company` | boolean | no | true: only companies; false: only people. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `offset` | integer | no | Number of records to skip, for the next page. Default: 0. |

Returns contacts with their ID, name, email, phone and company. Use contact_id from each item for create_draft_invoice and create_sales_order. An empty result means no contact matches, which is the cue to call create_contact.

Example response:

```json
{
  "items": [
    {
      "contact_id": 931,
      "name": "Northwind Studio",
      "email": "billing@northwind.example",
      "phone": "+49 30 555 0142",
      "is_company": true
    }
  ],
  "total": 1
}
```

### list_payment_journals

List the bank and cash journals you can register payments on. Access: read. REST: `GET /api/v1/odoo/payment-journals`. MCP: `odoo_read → list_payment_journals`.

No parameters.

Returns the bank and cash journals of the company you are signed in to, with the name Odoo shows. Pass the name to register_payment as journal. Journals your Odoo user cannot use are left out.

Example response:

```json
{
  "items": [
    {
      "journal_id": 7,
      "name": "Bank",
      "type": "bank",
      "currency": "EUR"
    },
    {
      "journal_id": 8,
      "name": "Cash",
      "type": "cash",
      "currency": "EUR"
    }
  ]
}
```

### list_sales_orders

List quotations and sales orders with customer, status and total. Access: read. REST: `GET /api/v1/odoo/sales-orders`. MCP: `odoo_read → list_sales_orders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | quotation, sent, sale or cancel. Default: all. |
| `contact_id` | integer | no | Only orders of this contact. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `offset` | integer | no | Number of records to skip, for the next page. Default: 0. |

Returns quotations and sales orders, newest first, with the order number, customer, status and untaxed and total amounts. A quotation becomes a sales order when it is confirmed in Odoo. Pages hold up to 100 orders.

Example response:

```json
{
  "items": [
    {
      "order_id": 2210,
      "number": "S00087",
      "contact": "Harbor Print",
      "status": "quotation",
      "amount_untaxed": 1200,
      "amount_total": 1200,
      "currency": "EUR"
    }
  ],
  "total": 1
}
```

### create_contact

Add a customer contact, a person or a company. Access: write. REST: `POST /api/v1/odoo/contacts`. MCP: `odoo_write → create_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Contact name. |
| `email` | string | no | Email address, used when you send an invoice. |
| `phone` | string | no | Phone number. |
| `is_company` | boolean | no | true: a company. Default: false. |

Creates one contact and returns its ID. It reaches nobody and sends no email, and you can archive the contact in Odoo with one click, so it does not wait for your OK. Check list_contacts first: this call does not stop you from creating a duplicate.

Example response:

```json
{
  "contact_id": 944,
  "name": "Harbor Print",
  "email": "accounts@harborprint.example",
  "is_company": true
}
```

### create_draft_invoice

Create a customer invoice in Draft status. Access: write. REST: `POST /api/v1/odoo/contacts/{contact_id}/draft-invoices`. MCP: `odoo_write → create_draft_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | integer | yes | Contact ID from list_contacts or create_contact. |
| `lines` | array | yes | Invoice lines: description (string), quantity (number), unit_price (number). |
| `invoice_date` | date | no | Invoice date. Default: today. |
| `due_date` | date | no | Due date. Default: from the contact's payment terms. |
| `reference` | string | no | Customer reference shown on the invoice. |

Creates the invoice in Draft status and returns its ID and totals. A draft has no accounting impact and no number until it is confirmed, so it reaches nobody and does not wait for your OK. Confirm it with post_invoice.

Example response:

```json
{
  "invoice_id": 4201,
  "number": null,
  "contact": "Northwind Studio",
  "status": "draft",
  "payment_status": "not_paid",
  "invoice_date": "2026-10-31",
  "due_date": "2026-11-14",
  "lines": [
    {
      "description": "Monthly retainer, October",
      "quantity": 1,
      "unit_price": 2400,
      "subtotal": 2400
    }
  ],
  "amount_untaxed": 2400,
  "amount_tax": 0,
  "amount_total": 2400,
  "currency": "EUR"
}
```

### post_invoice

Confirm a draft invoice so it becomes Posted and gets its number. Access: write, asks the user first. REST: `POST /api/v1/odoo/invoices/{invoice_id}`. MCP: `odoo_write → post_invoice`.

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

Clicks Confirm on a draft invoice. The status changes to Posted, Odoo assigns the invoice number and creates the journal entry, and the invoice can no longer be edited. The call fails if the invoice is not a draft. To change a posted invoice, Odoo has Reset to draft. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": 4201,
  "number": "INV/2026/00431",
  "status": "posted",
  "payment_status": "not_paid",
  "amount_total": 2400,
  "amount_due": 2400,
  "currency": "EUR"
}
```

### send_invoice

Send a posted invoice to the customer by email, or get it as a download. Access: write, asks the user first. REST: `POST /api/v1/odoo/invoices/{invoice_id}/send-invoice`. MCP: `odoo_write → send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | yes | Invoice ID from list_invoices or create_draft_invoice. |
| `method` | enum | no | email or download. Default: the contact's preferred sending method. |

Uses the Send window of the invoice. With email the invoice goes to the contact's email address; with download Cotlet returns the file and nothing is sent. Only posted invoices can be sent. The call fails with a clear error if the contact has no email address. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": 4182,
  "number": "INV/2026/00412",
  "method": "email",
  "sent_to": "billing@northwind.example",
  "status": "posted"
}
```

### register_payment

Register a payment on a posted invoice through the Pay window. Access: write, asks the user first. REST: `POST /api/v1/odoo/invoices/{invoice_id}/payments`. MCP: `odoo_write → register_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | yes | Invoice ID from list_invoices or create_draft_invoice. |
| `journal` | string | yes | Journal name from list_payment_journals, e.g. Bank. |
| `amount` | number | no | Amount paid. Default: the amount Odoo proposes (the full amount, or the current installment with payment terms). |
| `payment_date` | date | no | Payment date. Default: today. |
| `memo` | string | no | Reference, e.g. a check number. |

Fills the Pay window and clicks Create Payment. The invoice shows In payment afterwards and becomes Paid once the payment is reconciled with a bank transaction. The call fails if the invoice is a draft or already Paid. Only invoicing users can register payments. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "payment_id": 5120,
  "invoice_id": 4182,
  "number": "INV/2026/00412",
  "journal": "Bank",
  "amount": 3200,
  "payment_date": "2026-10-14",
  "memo": "Bank transfer Northwind",
  "payment_status": "in_payment"
}
```

### create_credit_note

Reverse a posted invoice with a credit note. Access: write, asks the user first. REST: `POST /api/v1/odoo/invoices/{invoice_id}/credit-notes`. MCP: `odoo_write → create_credit_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | integer | yes | Invoice ID from list_invoices or create_draft_invoice. |
| `reason` | string | yes | Reason shown on the credit note. |
| `mode` | enum | no | reverse: a draft credit note you can adjust; reverse_and_new: a validated credit note plus a new draft invoice. Default: reverse. |

Uses the Credit Note window of the invoice. In reverse mode the credit note is a draft prefilled from the original invoice. In reverse_and_new mode it is validated, reconciled with the original and a new draft invoice is opened. If money goes back to the customer, register that payment afterwards. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "credit_note_id": 4230,
  "reverses": "INV/2026/00398",
  "mode": "reverse",
  "status": "draft",
  "reason": "Wrong quantity",
  "amount_total": 2150,
  "currency": "EUR"
}
```

### create_sales_order

Create a quotation for a customer in the Sales app. Access: write. REST: `POST /api/v1/odoo/contacts/{contact_id}/sales-orders`. MCP: `odoo_write → create_sales_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | integer | yes | Contact ID from list_contacts or create_contact. |
| `lines` | array | yes | Order lines: description (string), quantity (number), unit_price (number). |
| `reference` | string | no | Customer reference. |

Creates a quotation and returns its ID and totals. It stays a quotation: it is not sent and not confirmed, so it reaches nobody and does not wait for your OK. Confirming and invoicing it happen in Odoo.

Example response:

```json
{
  "order_id": 2231,
  "number": "S00094",
  "contact": "Harbor Print",
  "status": "quotation",
  "lines": [
    {
      "description": "Consulting, hours",
      "quantity": 10,
      "unit_price": 120,
      "subtotal": 1200
    }
  ],
  "amount_untaxed": 1200,
  "amount_total": 1200,
  "currency": "EUR"
}
```

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

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

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

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

```
List the customer invoices in Odoo that are posted, unpaid and past their due date. For each one older than 14 days, resend the invoice by email and give me a list of what you sent, sorted by amount.
```

### Call Odoo 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/odoo 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/odoo/invoices/4182/payments \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"journal":"Bank","amount":3200,"payment_date":"2026-10-14","memo":"Bank transfer Northwind"}'
```

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

```
{
  "payment_id": 5120,
  "invoice_id": 4182,
  "number": "INV/2026/00412",
  "journal": "Bank",
  "amount": 3200,
  "payment_date": "2026-10-14",
  "memo": "Bank transfer Northwind",
  "payment_status": "in_payment"
}
```

## Why use Cotlet for Odoo?

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

## Is it safe to connect Odoo to Cotlet?

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

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

## Is there a Odoo MCP server on GitHub?

Yes. Open-source Odoo MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, point it at your instance with an API key, and keep it running yourself; most of them call the same external API, so they need the Custom plan on Odoo Online and break when Odoo changes it. Cotlet hosts the same kind of server for you, signs in as you with one browser login, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, create an API key, set the instance URL and database, add it to each MCP client | Sign up, sign in to your Odoo once, add one MCP server or API key |
| When Odoo changes | It breaks until you or the maintainer fix it (the RPC endpoints are deprecated since Odoo 19) | Our team tests it daily and fixes it for you; failed calls are free |
| Your Odoo session | An API key in a file or environment variable 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; we never save your password |
| When the session expires | Calls fail until you issue a new key or sign in again by hand | Your Cloud Browser keeps you signed in; if Odoo logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time; the API itself needs the Custom plan on Odoo Online | 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 Odoo 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 Odoo API cost?

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

**Do I need to be technical?**

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

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

Odoo 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 the Custom plan to use Cotlet with Odoo?**

No. Cotlet signs in to Odoo in the browser as you, so it works on the plans where the external API is not available. Odoo lists the external API as Custom-plan only on Odoo Online (checked 14 Oct 2026), which matters only if you call the API yourself.

**Which Odoo user rights does my agent get?**

The same as the user you sign in with. Odoo's API keys also carry the rights of their user, so a user without invoicing rights cannot confirm invoices or register payments through Cotlet either.

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

No. Every call to post_invoice, send_invoice, register_payment or create_credit_note 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_contact, create_draft_invoice, create_sales_order runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Odoo 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/odoo 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.