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

# Billetto API and MCP server

> Billetto has a public API (v3) for organisers and developers, but no official MCP server (checked 23 Oct 2026). It pulls events, attendees, orders and financials, pushes audiences and sends webhooks. It documents no endpoint to refund tickets, cancel them, resend a ticket or create an event.

Ticketing platform for event organisers: create events, sell tickets, scan them at the door and receive payouts, with attendee lists, access codes and campaigns.

## What is the Billetto API?

Cotlet's Billetto API exposes 14 endpoints for your own Billetto account: list events, get event, list ticket types, list orders, get order, list attendees, list campaigns, refund tickets, cancel free tickets, resend ticket, add order note, create access code, send guest report and clone event. The list_events endpoint returns your events with date, status and tickets sold. Each endpoint takes simple JSON inputs like event_id, order_id or cursor and works both as an operation of the billetto_read or billetto_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-20

Billetto has a public API (v3) for organisers and developers, but no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Billetto with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Billetto have an official API?

Billetto has a public API (v3) for organisers and developers, but no official MCP server (checked 23 Oct 2026). It pulls events, attendees, orders and financials, pushes audiences and sends webhooks. It documents no endpoint to refund tickets, cancel them, resend a ticket or create an event.

| Task | Billetto official | Cotlet |
|---|---|---|
| List events, orders and attendees | Yes: API v3 reads; you need an API key or OAuth and your own code | Yes |
| Read ticket types and campaigns | Yes: API v3 reads | Yes |
| Refund tickets | No | Yes |
| Cancel free tickets | No | Yes |
| Resend a ticket PDF | No | Yes |
| Add an order note | No | Yes |
| Create an access code | No: The API can push audiences; access codes are set in the app | Yes |
| Email a guest list or sales report | Partly: The API lists attendees; the report types are sent from Guest list & reports | Yes |

Sources: [Billetto API: endpoint reference](https://api.billetto.com/reference), [Billetto API: Getting started](https://api.billetto.com/docs/get-started), [Billetto Help: Billetto public API for your events and tickets](https://support.billetto.com/hc/articles/360020747740), [Billetto on Zapier MCP](https://zapier.com/mcp/billetto)

## Quick reference

```text
Billetto has a public API (v3) for organisers and developers, but no official MCP server (checked 23 Oct 2026). It pulls events, attendees, orders and financials, pushes audiences and sends webhooks. It documents no endpoint to refund tickets, cancel them, resend a ticket or create an event.
Cotlet provides a hosted MCP server and REST API for Billetto: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=billetto, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    billetto_read, billetto_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/billetto, each operation at its own route, e.g. POST /api/v1/billetto/orders/{order_id}/tickets/refund
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_events, get_event, list_ticket_types, list_orders, get_order, list_attendees, list_campaigns, refund_tickets, cancel_free_tickets, resend_ticket, add_order_note, create_access_code, send_guest_report, clone_event
Confirm      refund_tickets, cancel_free_tickets, resend_ticket, add_order_note, create_access_code, send_guest_report, clone_event (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/billetto-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=billetto, requests Billetto in the Cotlet console and creates an API key there.
2. The user signs in to Billetto once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Billetto 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 Billetto server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Billetto 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 Billetto 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 Billetto 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 Billetto's terms; Cotlet is not affiliated with Billetto.
```

## What can an AI agent do in Billetto?

Cotlet is best for Billetto organisers who are not developers and need refunds, ticket resends, guest lists and access codes handled by an AI agent without running or fixing a server.

- **[Refund tickets from a list of requests](https://cotlet.dev/integrations/billetto-api-mcp-server/refund-tickets-for-guests.md)**: "Refund the tickets for these buyers of Autumn Jazz Night: maria.jensen@example.com (two General admission, keep the Student ticket), tom.berg@example.com (whole order). Do not cover booking fees." → `list_orders`, `get_order`, `refund_tickets`
- **[Resend tickets to guests who did not get them](https://cotlet.dev/integrations/billetto-api-mcp-server/resend-tickets-to-guests.md)** (runs: daily): "Guests of Autumn Jazz Night wrote to say their ticket never arrived. For each email in this list, resend the ticket. If they say they mistyped their address, put them on a list for me instead." → `list_orders`, `get_order`, `resend_ticket`
- **[Email the guest list to the venue](https://cotlet.dev/integrations/billetto-api-mcp-server/email-guest-list-to-venue.md)** (runs: weekly): "Every Thursday, email the detailed guest list of each of my events from the weekend to door@example.com." → `list_events`, `send_guest_report`
- **Cancel free tickets on request**: "These guests cancelled their free RSVP for Pottery Workshop. Find their orders and cancel the free tickets. Leave paid tickets for me." → `list_orders`, `get_order`, `cancel_free_tickets`
- **Create access codes for partners**: "For the Partner offer ticket of Autumn Jazz Night, create one access code per partner on this list, each limited to 30 tickets." → `list_events`, `list_ticket_types`, `create_access_code`
- **Clone last week's event for the next date** (runs: weekly): "Clone Pottery Workshop for next week and keep the booking questions and scanner settings. Tell me what I still have to set." → `list_events`, `get_event`, `clone_event`

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

Yes. Cotlet does not replace your automation platform: it gives it a Billetto 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 resend tickets to guests who did not get them, 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/billetto/orders. | 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/billetto/orders with your API key. | cron or GitHub Actions. |

## Tools

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

### list_events

Your events with date, status and tickets sold. Access: read. REST: `GET /api/v1/billetto/events`. MCP: `billetto_read → list_events`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `include_past` | boolean | no | Also return events that have finished. Default false. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the events under My Billetto, newest first. By default it returns current events; include_past adds events that are over. Each row carries the event_id the other tools take, the start date and the tickets sold. Use get_event for the full record.

Example response:

```json
{
  "events": [
    {
      "event_id": "1204551",
      "name": "Autumn Jazz Night",
      "starts_at": "2026-11-14T19:30:00+01:00",
      "status": "published",
      "orders": 61,
      "tickets_sold": 132
    },
    {
      "event_id": "1204873",
      "name": "Pottery Workshop",
      "starts_at": "2026-11-21T10:00:00+01:00",
      "status": "published",
      "orders": 25,
      "tickets_sold": 57
    }
  ],
  "next_cursor": null
}
```

### get_event

One event with its venue, dates, ticket types and sales. Access: read. REST: `GET /api/v1/billetto/events/{event_id}`. MCP: `billetto_read → get_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |

Returns the event as shown in Manage: name, venue, start and end, publish state, tickets sold and the ticket types with price and quantity. Recurring events come back as the parent event with its time slots.

Example response:

```json
{
  "event_id": "1204551",
  "name": "Autumn Jazz Night",
  "venue": "Harbour Hall",
  "starts_at": "2026-11-14T19:30:00+01:00",
  "ends_at": "2026-11-14T23:00:00+01:00",
  "status": "published",
  "tickets_sold": 132,
  "ticket_types": [
    {
      "ticket_type_id": "77120",
      "name": "General admission",
      "price": 25,
      "quantity": 200
    },
    {
      "ticket_type_id": "77121",
      "name": "Student",
      "price": 15,
      "quantity": 40
    }
  ]
}
```

### list_ticket_types

Ticket types of an event with price, quantity and whether an access code is needed. Access: read. REST: `GET /api/v1/billetto/events/{event_id}/ticket-types`. MCP: `billetto_read → list_ticket_types`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |

Returns each ticket type of one event with its name, price, quantity and sales period. needs_access_code is true for a ticket type hidden unless a code is entered; that switch lives in the ticket's Advanced settings in the event editor. Pass ticket_type_id to create_access_code.

Example response:

```json
{
  "event_id": "1204551",
  "ticket_types": [
    {
      "ticket_type_id": "77120",
      "name": "General admission",
      "price": 25,
      "quantity": 200,
      "needs_access_code": false
    },
    {
      "ticket_type_id": "77121",
      "name": "Student",
      "price": 15,
      "quantity": 40,
      "needs_access_code": false
    },
    {
      "ticket_type_id": "77122",
      "name": "Partner offer",
      "price": 18,
      "quantity": 30,
      "needs_access_code": true
    }
  ]
}
```

### list_orders

Orders across all your events, searched by buyer email, name or order ID. Access: read. REST: `GET /api/v1/billetto/orders`. MCP: `billetto_read → list_orders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Buyer email address, buyer name or order ID. |
| `event_id` | string | no | Only orders of this event, from list_events. |
| `cursor` | string | no | Next page cursor from the previous call. |

Searches the account-level order list (Manage > Attendees), newest first. query matches the buyer's email address, name or order ID, the three ways Billetto looks an order up. event_id narrows the list to one event. Each row has the order_id, buyer, event and ticket count; get_order returns the tickets.

Example response:

```json
{
  "orders": [
    {
      "order_id": "9035127",
      "event_id": "1204551",
      "event": "Autumn Jazz Night",
      "buyer": "Maria Jensen",
      "email": "maria.jensen@example.com",
      "placed_at": "2026-10-19T18:42:10+02:00",
      "tickets": 3
    }
  ],
  "next_cursor": null
}
```

### get_order

One order with its tickets, prices and notes. Access: read. REST: `GET /api/v1/billetto/orders/{order_id}`. MCP: `billetto_read → get_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders. |

Returns the order's details page: buyer, event, each ticket with its type, price and state, and the order notes. The state of a ticket tells which tool applies: refund_tickets for paid tickets, cancel_free_tickets for free ones, resend_ticket for a guest who did not get the PDF. event_over is true once the event has finished, and then Billetto accepts no refund.

Example response:

```json
{
  "order_id": "9035127",
  "event_id": "1204551",
  "event": "Autumn Jazz Night",
  "event_over": false,
  "buyer": {
    "name": "Maria Jensen",
    "email": "maria.jensen@example.com"
  },
  "placed_at": "2026-10-19T18:42:10+02:00",
  "tickets": [
    {
      "ticket_id": "48210331",
      "ticket_type": "General admission",
      "price": 25,
      "state": "valid"
    },
    {
      "ticket_id": "48210332",
      "ticket_type": "General admission",
      "price": 25,
      "state": "valid"
    },
    {
      "ticket_id": "48210333",
      "ticket_type": "Student",
      "price": 15,
      "state": "valid"
    }
  ],
  "ticket_total": 65,
  "notes": []
}
```

### list_attendees

The guests of one event with ticket type and scan state. Access: read. REST: `GET /api/v1/billetto/events/{event_id}/attendees`. MCP: `billetto_read → list_attendees`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the tickets of one event as in Attendees > Manage Tickets: guest name, ticket type, order_id and whether the ticket was scanned at the door. Order is by purchase, newest first. Use it to answer "who is coming", and send_guest_report when the venue needs a file.

Example response:

```json
{
  "event_id": "1204551",
  "attendees": [
    {
      "ticket_id": "48210331",
      "name": "Maria Jensen",
      "ticket_type": "General admission",
      "order_id": "9035127",
      "scanned": false
    },
    {
      "ticket_id": "48210333",
      "name": "Maria Jensen",
      "ticket_type": "Student",
      "order_id": "9035127",
      "scanned": false
    }
  ],
  "next_cursor": null
}
```

### list_campaigns

Discount campaigns of an event or of the account, by status. Access: read. REST: `GET /api/v1/billetto/campaigns`. MCP: `billetto_read → list_campaigns`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | no | Only campaigns of this event. Omit for account-wide campaigns. |
| `status` | string | no | running, drafts, paused or completed. Omit for all. |

Returns the campaigns from Promotions & Offers with their name, status and what they do (a percentage discount, a set price per ticket type or an unlocked ticket type). Billetto groups campaigns as running, drafts, paused and completed. Leave event_id out for account-wide campaigns.

Example response:

```json
{
  "campaigns": [
    {
      "campaign_id": "30918",
      "name": "Early bird",
      "status": "running",
      "effect": "20% discount",
      "scope": "event"
    },
    {
      "campaign_id": "30650",
      "name": "Members week",
      "status": "paused",
      "effect": "30% discount",
      "scope": "account"
    }
  ]
}
```

### refund_tickets

Request a refund for a whole order or for chosen tickets. Access: write, asks the user first. REST: `POST /api/v1/billetto/orders/{order_id}/tickets/refund`. MCP: `billetto_write → refund_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders. |
| `ticket_ids` | array | no | Ticket IDs from get_order. Omit to refund the whole order. |
| `with_fees` | boolean | no | true: you also cover the booking fee and add-ons. Default false. |

Does what Request refund does on the order's details page: the whole order, or only the tickets in ticket_ids. By default the refund leaves out Billetto's booking fee and additional services. With with_fees true you cover the full price the buyer paid and Billetto sends you an invoice for your bookkeeping. Billetto refunds only current events, so a finished event returns an error. The money reaches the buyer's bank within 5 working days or, depending on the bank, up to 21. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "9035127",
  "status": "refund_requested",
  "refunded_tickets": [
    "48210331",
    "48210332"
  ],
  "with_fees": false,
  "refund_amount": 50
}
```

### cancel_free_tickets

Cancel a whole free order or chosen free tickets. Access: write, asks the user first. REST: `POST /api/v1/billetto/orders/{order_id}/free-tickets/cancel`. MCP: `billetto_write → cancel_free_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders. |
| `ticket_ids` | array | no | Ticket IDs from get_order. Omit to cancel the whole order. |

Does what Cancel all tickets and Cancel selected do on the order page: it cancels free tickets only, because paid tickets go through refund_tickets. Omit ticket_ids to cancel the whole order. Billetto's help article does not say whether the guest gets an email, so the agent tells the guest itself when you ask for that. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "9041660",
  "status": "cancelled",
  "cancelled_tickets": [
    "48377102"
  ]
}
```

### resend_ticket

Email a guest their ticket PDF again. Access: write, asks the user first. REST: `POST /api/v1/billetto/tickets/{ticket_id}/resend`. MCP: `billetto_write → resend_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | string | yes | Ticket ID from get_order or list_attendees. |

Does what Resend PDF does on a ticket in Attendees > Manage Tickets: Billetto emails the PDF again to the address on the order. The address cannot be changed here, and Billetto's help article describes no way to edit it; for a mistyped address the fix is Forward PDF from your own email client, which this tool does not do. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": "48210331",
  "order_id": "9035127",
  "sent_to": "maria.jensen@example.com",
  "status": "sent"
}
```

### add_order_note

Add a free-text note to an order. Access: write, asks the user first. REST: `POST /api/v1/billetto/orders/{order_id}/note`. MCP: `billetto_write → add_order_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders. |
| `note` | string | yes | The note text. |

Adds a note under Add Note on the order page, for things like accessibility needs or an instruction for your team. Billetto shows the note to anyone who opens the order and prints it in downloaded reports, and its help article does not say whether the buyer sees it, so write nothing you would not say to the buyer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "9035127",
  "notes": [
    {
      "note": "Needs step-free entrance",
      "added_at": "2026-10-23T10:12:44+02:00"
    }
  ]
}
```

### create_access_code

Create an access code for a ticket type, with an optional limit. Access: write, asks the user first. REST: `POST /api/v1/billetto/events/{event_id}/access-codes`. MCP: `billetto_write → create_access_code`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `ticket_type_id` | string | yes | Ticket type ID from list_ticket_types. |
| `code` | string | yes | The code buyers type in. |
| `limit` | integer | no | Most tickets that can be bought with this code in total. |

Does what Generate access code does under Promotions & Offers > Access Codes: it ties the code to one ticket type. The discount comes from that ticket type's own price, so use a ticket type that list_ticket_types shows with needs_access_code true. limit caps the tickets bought with the code in total, not the number of times the code is used. A code gives access to tickets that cost money, so each call needs your OK by default. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "1204551",
  "ticket_type_id": "77122",
  "code": "HARBOUR18",
  "limit": 30,
  "status": "created"
}
```

### send_guest_report

Email a guest list or sales report of an event. Access: write, asks the user first. REST: `POST /api/v1/billetto/events/{event_id}/guest-reports`. MCP: `billetto_write → send_guest_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `report` | string | yes | guest_list_simple, guest_list_detailed, email_list, newsletter_signup or sales_report. |
| `email` | string | yes | Recipient address. |
| `from` | date | no | First day of the date range. |
| `to` | date | no | Last day of the date range. |

Does what Guest list & reports > Send via email does. report is one of guest_list_simple (order ID, name, ticket ID), guest_list_detailed (name and email, order ID, number of tickets, answers to purchase questions, access codes), email_list, newsletter_signup (consent and email) or sales_report. The report goes to the address you give, so the guest data leaves Billetto. Events with more than 5,000 attendees may take longer. from and to are optional; without them all data is included. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "1204551",
  "report": "guest_list_detailed",
  "sent_to": "door@example.com",
  "status": "sent"
}
```

### clone_event

Copy an event, with the optional settings you choose to keep. Access: write, asks the user first. REST: `POST /api/v1/billetto/events/{event_id}/clone`. MCP: `billetto_write → clone_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `keep` | array | no | Optional items to copy: booking_questions, headliners, custom_email_text, capacity_settings, scanner_settings, ticket_banners. |

Does what More > Clone does on an event in Manage: description, image and ticket types are copied automatically. keep adds the optional items: booking_questions, headliners, custom_email_text, capacity_settings, scanner_settings and ticket_banners. For a recurring event only the parent event is copied, so its time slots are added by hand in Billetto. The copy still needs its date and a check before you publish it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "source_event_id": "1204551",
  "event_id": "1209330",
  "name": "Autumn Jazz Night",
  "copied": [
    "booking_questions",
    "scanner_settings"
  ]
}
```

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

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

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

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

```
Refund the tickets for these buyers of Autumn Jazz Night: maria.jensen@example.com (two General admission, keep the Student ticket), tom.berg@example.com (whole order). Do not cover booking fees.
```

### Call Billetto 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/billetto 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/billetto/orders/9035127/tickets/refund \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"ticket_ids":["48210331","48210332"],"with_fees":false}'
```

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

```
{
  "order_id": "9035127",
  "status": "refund_requested",
  "refunded_tickets": [
    "48210331",
    "48210332"
  ],
  "with_fees": false,
  "refund_amount": 50
}
```

## Why use Cotlet for Billetto?

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

## Is it safe to connect Billetto to Cotlet?

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

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

## Is there a Billetto MCP server on GitHub?

Billetto has a Zapier app with triggers for new attendees, orders and events, and find actions for attendees, events and orders. It fits notifications and syncs to other tools. It has no action that refunds, cancels or resends a ticket. Cotlet works the screens of your own account for those jobs, and n8n, Make and Zapier can call it too.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect your Billetto account in Zapier and build a Zap for each trigger | Sign up, sign in to Billetto once, add one MCP server or API key |
| What it does | Reacts to new attendees, orders and events; finds an attendee, event or order | Reads and changes: refund, cancel free tickets, resend, notes, access codes, reports |
| When Billetto changes | Zapier maintains the app; its actions stay find-only | Automatic checks run against it and our team fixes it when Billetto changes |
| Your Billetto session | A connection to your account stored in Zapier | In your own Cloud Browser in the EU, session encrypted (AES-256), never your password |
| When the session expires | You reconnect the account in Zapier | If Billetto logs you out, your agent gets a link to sign in again |
| Where it runs | Inside Zapier and its MCP server | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Depends on your Zapier plan | 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 Billetto 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 Billetto API cost?

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

**Do I need to be technical?**

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

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

Billetto offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Which Billetto account does my agent need?**

Your own organiser login. Refunds, cancellations, ticket resends and guest reports are organiser screens under My Billetto > Manage, so the account must be able to open them for the event. Cotlet does not use the Billetto API, which needs an API key or OAuth and follows Billetto's API Terms (checked 23 Oct 2026).

**Can my agent refund tickets after the event?**

No. Billetto processes refunds only for current events and not once an event is completed, so refund_tickets returns that error. Free tickets are cancelled with cancel_free_tickets instead.

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

No. Every call to refund_tickets, cancel_free_tickets, resend_ticket, add_order_note, create_access_code, send_guest_report or clone_event 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 Billetto 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/billetto 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.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](https://cotlet.dev/about.md)

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.