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

# MYOB API and MCP server

> Yes, MYOB has a full REST API, the MYOB Business API, for sales invoices, bills, customer and supplier payments and contacts (checked 14 Oct 2026), but it is not open by default: you request access through the API support form, register an app in my.MYOB for a key and secret, and every user grants OAuth consent per company file. MYOB also runs an official connector for Claude and ChatGPT, but it is read-only and in invite-only beta in Australia, so no official MCP server creates or sends an invoice.

Australian and New Zealand cloud accounting software for small businesses: sales invoices, bills, customer and supplier payments, bank feeds, GST and payroll in one company file.

## What is the MYOB API?

Cotlet's MYOB API exposes 12 endpoints for your own MYOB account: list customers, list invoices, get invoice, list bills, list bank accounts, create customer, create invoice, send invoice, record invoice payment, create bill, record bill payment and send customer statement. The list_customers endpoint returns customer cards with card ID, name, email and payment terms, filtered by name or email. Each endpoint takes simple JSON inputs like date, limit or cursor and works both as an operation of the myob_read or myob_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-22

Yes, MYOB has a full REST API, the MYOB Business API, for sales invoices, bills, customer and supplier payments and contacts (checked 14 Oct 2026), but it is not open by default: you request access through the API support form, register an app in my.MYOB for a key and secret, and every user grants OAuth consent per company file. Cotlet is a hosted MCP server and REST API for MYOB with 12 endpoints (5 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does MYOB have an official API?

Yes, MYOB has a full REST API, the MYOB Business API, for sales invoices, bills, customer and supplier payments and contacts (checked 14 Oct 2026), but it is not open by default: you request access through the API support form, register an app in my.MYOB for a key and secret, and every user grants OAuth consent per company file. MYOB also runs an official connector for Claude and ChatGPT, but it is read-only and in invite-only beta in Australia, so no official MCP server creates or sends an invoice.

| Task | MYOB official | Cotlet |
|---|---|---|
| Create sales invoices | Yes: Sale/Invoice accepts POST for Item, Service, Professional and Miscellaneous invoices | Yes |
| Email an invoice to the customer | Partly: The invoice has a delivery status field that marks it to be emailed; the API documentation shows no send action | Yes |
| Record customer payments on invoices | Yes: Sale/CustomerPayment applies an amount to one or more invoices | Yes |
| List overdue invoices | Yes: Sale/Invoice returns status, balance due and terms; you work out overdue yourself | Yes |
| Create supplier bills | Yes: Purchase/Bill accepts POST for Item, Service, Professional and Miscellaneous bills | Yes |
| Record supplier payments on bills | Yes: Purchase/SupplierPayment, from a bank account or by electronic payment | Yes |
| Add customers | Yes: Contact/Customer accepts POST | Yes |

Sources: [MYOB Developer Centre: MYOB APIs](https://developer.myob.com/api/), [MYOB Developer Centre: Getting started with the Business API](https://developer.myob.com/api/myob-business-api/api-overview/getting-started/), [MYOB Developer Centre: Granular data scopes](https://developer.myob.com/api/myob-business-api/api-overview/granular_data_scopes/), [MYOB Developer Centre: Sale/Invoice](https://developer.myob.com/api/myob-business-api/v2/sale/invoice/), [MYOB Community: MYOB Connector, ask Claude or ChatGPT about your business](https://community.myob.com/blog/communityblog/myob-connector-ask-claude-or-chatgpt-about-your-business/923230)

## For AI agents

```text
Yes, MYOB has a full REST API, the MYOB Business API, for sales invoices, bills, customer and supplier payments and contacts (checked 14 Oct 2026), but it is not open by default: you request access through the API support form, register an app in my.MYOB for a key and secret, and every user grants OAuth consent per company file. MYOB also runs an official connector for Claude and ChatGPT, but it is read-only and in invite-only beta in Australia, so no official MCP server creates or sends an invoice.
Cotlet provides a hosted MCP server and REST API for MYOB: 12 tools (5 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=myob, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    myob_read, myob_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/myob, each operation at its own route, e.g. POST /api/v1/myob/customers/{customer_id}/invoices
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_customers, list_invoices, get_invoice, list_bills, list_bank_accounts, create_customer, create_invoice, send_invoice, record_invoice_payment, create_bill, record_bill_payment, send_customer_statement
Confirm      create_invoice, send_invoice, record_invoice_payment, create_bill, record_bill_payment, send_customer_statement (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/myob-api-mcp-server.md

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

## What can an AI agent do in MYOB?

Cotlet is best for Australian and New Zealand small businesses and bookkeepers who want their AI agent to create invoices, record payments and enter bills in MYOB without registering an API app or running and fixing a server.

- **[Create and email invoices from a list](https://cotlet.dev/integrations/myob-api-mcp-server/create-and-email-invoices.md)**: "Here is this month's billing list. For each customer, create the invoice in MYOB with the description, amount and GST code I gave, then email it to the address on the customer card. Add customers that do not exist yet." → `list_customers`, `create_customer`, `create_invoice`, `send_invoice`
- **[Record customer payments on invoices](https://cotlet.dev/integrations/myob-api-mcp-server/record-invoice-payments.md)** (runs: daily): "Here are yesterday's incoming payments. Find the matching open invoice in MYOB by invoice number or by customer and exact amount, record the payment into the bank account I name, and list anything that does not match." → `list_bank_accounts`, `list_invoices`, `get_invoice`, `record_invoice_payment`
- **[Enter supplier bills and pay them](https://cotlet.dev/integrations/myob-api-mcp-server/enter-and-pay-supplier-bills.md)**: "Here are this week's supplier invoices. Create a bill in MYOB for each one with the supplier's invoice number and GST, skip any bill that is already entered, and show me the list before paying the ones due this week." → `list_bills`, `create_bill`, `record_bill_payment`
- **Weekly overdue invoices report** (runs: weekly): "Every Monday, list the overdue MYOB invoices grouped by customer with the days overdue and the balance, and tell me who to call first. Send a statement only to the customers I name." → `list_invoices`, `get_invoice`, `send_customer_statement`
- **Add new customers from a form or CRM** (runs: daily): "Take the new customers from this export, check they are not already in MYOB by name or email, and create the ones that are missing." → `list_customers`, `create_customer`

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

Yes. Cotlet does not replace your automation platform: it gives it a MYOB 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 record customer payments on 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/myob/bank-accounts. | 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/myob/bank-accounts 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 MYOB.

### list_customers

Customer cards with card ID, name, email and payment terms, filtered by name or email. Access: read. REST: `GET /api/v1/myob/customers`. MCP: `myob_read → list_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Customer name, card ID or email. |
| `include_inactive` | boolean | no | Include customers marked inactive. Default: false. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns customer cards in alphabetical order. Search matches the name, the card ID or the email. Active customers are returned unless include_inactive is true. Use customer_id from each item in create_invoice, record_invoice_payment and send_customer_statement. Pages hold up to 100 customers; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "customers": [
    {
      "customer_id": "CUS000012",
      "name": "Harbour Cafe Pty Ltd",
      "email": "accounts@harbourcafe.example",
      "terms": "In a given number of days: 14",
      "active": true
    }
  ],
  "next_cursor": null
}
```

### list_invoices

Sales invoices with customer, dates, total and balance due, filtered by status. Access: read. REST: `GET /api/v1/myob/invoices`. MCP: `myob_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | all, open, overdue, closed or credit. Default: all. |
| `customer_id` | string | no | Only invoices for this customer. |
| `due_before` | date | no | Only invoices with a due date before this date. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns sales invoices, newest first. Status open means unpaid, closed means paid, credit means a negative sale, and overdue returns the open invoices past their due date, the same list as Sales > Invoices > Overdue in MYOB. Each item carries the balance due and the days overdue, so a script can sort without a second call. Pages hold up to 100 invoices.

Example response:

```json
{
  "invoices": [
    {
      "invoice_number": "00000139",
      "customer_id": "CUS000014",
      "customer": "Coast Hardware",
      "date": "2026-09-02",
      "due_date": "2026-09-16",
      "total": 1320,
      "balance_due": 1320,
      "status": "open",
      "days_overdue": 28
    }
  ],
  "next_cursor": null
}
```

### get_invoice

One sales invoice with lines, tax, payments applied and activity history. Access: read. REST: `GET /api/v1/myob/invoices/{invoice_number}`. MCP: `myob_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | string | yes | Invoice number from list_invoices or create_invoice. |

Returns one invoice with every line, the tax, the balance due and the payments already applied. The activity history shows whether it was emailed and when the customer opened the email. Read it before record_invoice_payment so a short payment is not mistaken for a full one.

Example response:

```json
{
  "invoice_number": "00000139",
  "customer_id": "CUS000014",
  "customer": "Coast Hardware",
  "status": "open",
  "date": "2026-09-02",
  "due_date": "2026-09-16",
  "lines": [
    {
      "description": "Shopfront signage",
      "quantity": 1,
      "amount": 1200,
      "tax_code": "GST"
    }
  ],
  "subtotal": 1200,
  "tax": 120,
  "total": 1320,
  "payments_applied": [],
  "balance_due": 1320,
  "activity": [
    "Emailed 2026-09-02",
    "Viewed by customer 2026-09-03"
  ]
}
```

### list_bills

Supplier bills with supplier, dates, total and balance due, filtered by status. Access: read. REST: `GET /api/v1/myob/bills`. MCP: `myob_read → list_bills`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | all, open, closed or debit. Default: all. |
| `supplier_id` | string | no | Only bills from this supplier. |
| `due_before` | date | no | Only bills with a due date before this date. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns supplier bills, newest first. Status open means unpaid, closed means paid, and debit means a negative purchase. Each item carries the supplier's invoice number, so a script can check for a bill that was already entered. Pages hold up to 100 bills.

Example response:

```json
{
  "bills": [
    {
      "bill_number": "00000298",
      "supplier_id": "SUP000004",
      "supplier": "Bayside Property",
      "supplier_invoice_number": "INV-8802",
      "date": "2026-09-10",
      "due_date": "2026-10-10",
      "total": 2200,
      "balance_due": 0,
      "status": "closed"
    }
  ],
  "next_cursor": null
}
```

### list_bank_accounts

Bank accounts and credit cards you can record payments in or out of. Access: read. REST: `GET /api/v1/myob/bank-accounts`. MCP: `myob_read → list_bank_accounts`.

No parameters.

Returns the accounts MYOB offers in the Bank account field when you record a payment, with the account code to pass as bank_account. Use it so a payment is never recorded into a guessed account.

Example response:

```json
{
  "bank_accounts": [
    {
      "bank_account": "1-1110",
      "name": "Business Cheque Account",
      "type": "bank"
    },
    {
      "bank_account": "1-1120",
      "name": "Company Visa",
      "type": "credit_card"
    }
  ]
}
```

### create_customer

Add a customer card with name, email and payment terms. Access: write. REST: `POST /api/v1/myob/customers`. MCP: `myob_write → create_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `company_name` | string | no | Business name. Required unless first_name and last_name are given. |
| `first_name` | string | no | For an individual customer. |
| `last_name` | string | no | For an individual customer. |
| `email` | string | no | Email address used when an invoice is emailed. |
| `payment_days` | integer | no | Payment due in this number of days. Default: the terms set in MYOB. |

Creates a customer card and returns its card ID. Pass company_name for a business, or first_name and last_name for an individual. A card cannot change from customer to supplier later. It reaches no one and an unused card can be deleted in MYOB, so it does not ask for confirmation.

Example response:

```json
{
  "customer_id": "CUS000015",
  "name": "Bayside Physio",
  "email": "admin@baysidephysio.example",
  "terms": "In a given number of days: 14",
  "active": true
}
```

### create_invoice

Create a sales invoice for a customer with one or more lines. Access: write, asks the user first. REST: `POST /api/v1/myob/customers/{customer_id}/invoices`. MCP: `myob_write → create_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | yes | Customer card ID from list_customers, e.g. CUS000012. |
| `date` | date | no | Invoice date. Default: today. |
| `due_date` | date | no | Due date. Default: from the customer payment terms. |
| `layout` | enum | no | service, item or professional. Default: service. |
| `lines` | array | yes | Objects with description or item_code, quantity, unit_price and tax_code, e.g. GST. |
| `tax_inclusive` | boolean | no | true if unit prices include tax. Default: false. |
| `comment` | string | no | Text shown on the invoice. |

Creates an open sales invoice and returns its number, tax, total and balance due. Layout service takes free-text lines, item takes item codes from your Items List and professional also records the dates the work was done. Due date follows the customer terms unless you pass due_date. The invoice is not emailed until you call send_invoice. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_number": "00000142",
  "customer_id": "CUS000012",
  "customer": "Harbour Cafe Pty Ltd",
  "status": "open",
  "date": "2026-10-14",
  "due_date": "2026-10-28",
  "subtotal": 1000,
  "tax": 100,
  "total": 1100,
  "balance_due": 1100
}
```

### send_invoice

Email an invoice to the customer with the PDF attached. Access: write, asks the user first. REST: `POST /api/v1/myob/invoices/{invoice_number}`. MCP: `myob_write → send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | string | yes | Invoice number from list_invoices or create_invoice. |
| `to` | array | no | Email addresses. Default: the address on the customer card. |
| `cc` | array | no | Email addresses to copy. |
| `subject` | string | no | Subject line. Default: the MYOB email default. |
| `message` | string | no | Message text. Default: the MYOB email default. |
| `email_me_a_copy` | boolean | no | Send yourself a copy the customer cannot see. Default: false. |

Sends the invoice from the Share menu, Email invoice, to the address on the customer card unless you pass to. Attachments total up to 25MB. If the customer has no email address and you pass none, the call fails and sends nothing. The invoice then shows Emailed in its activity history. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_number": "00000142",
  "sent_to": [
    "accounts@harbourcafe.example"
  ],
  "cc": [],
  "attached_pdf": true,
  "status": "emailed",
  "sent_at": "2026-10-14T09:12:00+11:00"
}
```

### record_invoice_payment

Record money received from a customer against one or more open invoices. Access: write, asks the user first. REST: `POST /api/v1/myob/customers/{customer_id}/invoice-payments`. MCP: `myob_write → record_invoice_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | yes | Customer card ID from list_customers, e.g. CUS000012. |
| `bank_account` | string | yes | Account code from list_bank_accounts, the account the money came in to or goes out of. |
| `date` | date | no | Payment date. Default: today. |
| `reference` | string | no | Reference number. Default: the next number MYOB suggests. |
| `payments` | array | yes | Objects with invoice_number, amount and optional discount. |
| `description` | string | no | Description of transaction. |

Records the payment as Sales > Record invoice payment does and returns the amount applied to each invoice with its new balance and status. A payment that settles an invoice in full closes it; a smaller amount leaves it open. An amount above the open invoices makes MYOB create a customer credit, so check the balance with get_invoice first. Payments already reconciled cannot be changed later. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "payment_reference": "00000087",
  "customer_id": "CUS000012",
  "bank_account": "1-1110",
  "date": "2026-10-13",
  "amount_received": 1100,
  "applied": [
    {
      "invoice_number": "00000142",
      "amount": 1100,
      "balance_due": 0,
      "status": "closed"
    }
  ]
}
```

### create_bill

Enter a supplier invoice as a bill with its lines and tax. Access: write, asks the user first. REST: `POST /api/v1/myob/suppliers/{supplier_id}/bills`. MCP: `myob_write → create_bill`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `supplier_id` | string | yes | Supplier card ID, e.g. SUP000004. |
| `supplier_invoice_number` | string | no | The number on the supplier's own invoice. |
| `date` | date | no | Bill date. Default: today. |
| `due_date` | date | no | Due date. Default: from the supplier terms. |
| `layout` | enum | no | service or item. Default: service. |
| `lines` | array | yes | Objects with description or item_code, amount and tax_code, e.g. GST. |
| `tax_inclusive` | boolean | no | true if amounts include tax. Default: false. |

Creates an open bill and returns its number, tax, total and balance due. Pass the supplier's own invoice number so a later call to list_bills can spot a duplicate. Layout service takes free-text lines and item takes item codes. The bill changes your books and your payables, so it asks first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "bill_number": "00000311",
  "supplier_id": "SUP000004",
  "supplier": "Bayside Property",
  "supplier_invoice_number": "INV-8841",
  "status": "open",
  "date": "2026-10-10",
  "due_date": "2026-11-09",
  "subtotal": 2000,
  "tax": 200,
  "total": 2200,
  "balance_due": 2200
}
```

### record_bill_payment

Record a payment to a supplier against one or more open bills. Access: write, asks the user first. REST: `POST /api/v1/myob/suppliers/{supplier_id}/bill-payments`. MCP: `myob_write → record_bill_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `supplier_id` | string | yes | Supplier card ID, e.g. SUP000004. |
| `bank_account` | string | yes | Account code from list_bank_accounts, the account the money came in to or goes out of. |
| `date` | date | no | Payment date. Default: today. |
| `payments` | array | yes | Objects with bill_number, amount and optional discount. Start with the oldest bill. |
| `send_remittance` | boolean | no | Email a remittance advice now. Default: false. |

Records the payment as Purchases > Record supplier payment does and returns the amount applied to each bill with its new balance. It pays from a bank account and does not select Electronic payment, so MYOB sends no money to the supplier. Set send_remittance to email a remittance advice now. An amount above the open bills makes MYOB create a debit note. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "payment_reference": "00000044",
  "supplier_id": "SUP000004",
  "bank_account": "1-1110",
  "date": "2026-10-14",
  "amount_paid": 2200,
  "applied": [
    {
      "bill_number": "00000311",
      "amount": 2200,
      "balance_due": 0,
      "status": "closed"
    }
  ],
  "remittance_sent": false
}
```

### send_customer_statement

Email a customer statement as a PDF to one or more customers. Access: write, asks the user first. REST: `POST /api/v1/myob/customer-statements`. MCP: `myob_write → send_customer_statement`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `statement_type` | enum | yes | invoice or activity. |
| `statement_date` | date | no | For type invoice. Default: today. |
| `from` | date | no | For type activity: first day. |
| `to` | date | no | For type activity: last day. |
| `customer_ids` | array | yes | Customer IDs from list_customers. |
| `include_zero` | boolean | no | Include customers with a zero balance. Default: false. |
| `message` | string | no | Email text. Default: the MYOB email default. |

Sends statements the way Sales > Customer statements does. Type invoice lists unpaid invoices as at the statement date; type activity lists invoices and payments between two dates with a running balance. Customers with a zero balance are left out unless include_zero is true. The text is free text only, with no email variables. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "statement_type": "invoice",
  "statement_date": "2026-10-14",
  "sent": [
    {
      "customer_id": "CUS000014",
      "sent_to": "accounts@coasthardware.example",
      "balance": 1320
    }
  ],
  "skipped": []
}
```

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

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

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

2. **Sign in to MYOB in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to MYOB 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 MYOB 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 is this month's billing list. For each customer, create the invoice in MYOB with the description, amount and GST code I gave, then email it to the address on the customer card. Add customers that do not exist yet.
```

### Call MYOB 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/myob 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/myob/customers/CUS000012/invoices \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-10-14","layout":"service","lines":[{"description":"Bookkeeping, October","quantity":1,"unit_price":1000,"tax_code":"GST"}]}'
```

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

```
{
  "invoice_number": "00000142",
  "customer_id": "CUS000012",
  "customer": "Harbour Cafe Pty Ltd",
  "status": "open",
  "date": "2026-10-14",
  "due_date": "2026-10-28",
  "subtotal": 1000,
  "tax": 100,
  "total": 1100,
  "balance_due": 1100
}
```

## Why use Cotlet for MYOB?

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

## Is it safe to connect MYOB to Cotlet?

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

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

## Is there a MYOB MCP server on GitHub?

Yes. Community MYOB MCP servers exist on GitHub, usually maintained by one person, and some are read-only. You install one on your own computer, give it the key, secret and tokens from a MYOB app you registered, and keep it running yourself; when MYOB changes its scopes, it stops working until you or the maintainer fix it. The official API is the other route: you register an app and build the calls yourself. Cotlet hosts the same kind of server for you, signs in to your MYOB account in a browser, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Ask MYOB for API access, register an app, install the server, add its credentials to each MCP client | Sign up, sign in to MYOB once, add one MCP server or API key |
| When MYOB changes | It breaks until you or the maintainer fix it, as the retired CompanyFile scope showed | Our team tests it daily and fixes it for you; failed calls are free |
| Your MYOB access | API key, secret and a refresh token in a 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 |
| When access expires | Tools fail until you authorize again by hand | Your Cloud Browser keeps you signed in; if MYOB 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 | 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 MYOB 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 MYOB API cost?

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

**Do I need to be technical?**

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

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

MYOB 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 a MYOB developer key or API access?**

No. Cotlet signs in to your own MYOB account in a browser and does not use the Business API, which needs an access request, an app registered in my.MYOB and OAuth consent per company file. The tools run with the permissions your MYOB login already has.

**Which MYOB products do the tools cover?**

The tools follow the MYOB Business browser app: Sales > Invoices, Sales > Record invoice payment, Purchases > Bills and Purchases > Record supplier payment. A local AccountRight desktop file has no browser sign-in, so it is out of scope.

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

No. Every call to create_invoice, send_invoice, record_invoice_payment, create_bill, record_bill_payment or send_customer_statement waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_customer runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the MYOB 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/myob 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.