Billetto logo billetto.com

Live

Billetto API and MCP server

Billetto's API reads events, orders and attendees, but it has no way to refund, cancel or resend tickets. Sign in to Billetto once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Billetto.

Billetto's own API leaves this out. So we run one for you.

Billetto's own API, a GitHub MCP server and Cotlet compared
What you need Billetto's APIGitHub MCP serverCotlet
Refunds, ticket resends, cancellations No No Yes, 14 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Billetto changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 23, 2026. Sources: Billetto API: endpoint reference · Billetto API: Getting started · Billetto Help: Billetto public API for your events and tickets · Billetto on Zapier MCP

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Billetto in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Billetto to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Billetto and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    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"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/billetto with its own method and path, such as POST /api/v1/billetto/orders/{order_id}/tickets/refund, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Billetto API and MCP server do?

14 tools on your own Billetto account. Agents call them as operations of the MCP tools billetto_read and billetto_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Billetto tools in Cotlet's MCP server and REST API
Tool What it does Access
list_events Your events with date, status and tickets sold. read
get_event One event with its venue, dates, ticket types and sales. read
list_ticket_types Ticket types of an event with price, quantity and whether an access code is needed. read
list_orders Orders across all your events, searched by buyer email, name or order ID. read
get_order One order with its tickets, prices and notes. read
list_attendees The guests of one event with ticket type and scan state. read
list_campaigns Discount campaigns of an event or of the account, by status. read
refund_tickets Request a refund for a whole order or for chosen tickets. writeasks first
cancel_free_tickets Cancel a whole free order or chosen free tickets. writeasks first
resend_ticket Email a guest their ticket PDF again. writeasks first
add_order_note Add a free-text note to an order. writeasks first
create_access_code Create an access code for a ticket type, with an optional limit. writeasks first
send_guest_report Email a guest list or sales report of an event. writeasks first
clone_event Copy an event, with the optional settings you choose to keep. writeasks first

Scroll the table for all 14 tools.

Ask in plain words. Your agent does the rest.

All Billetto use cases

Is it safe to connect Billetto?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Billetto API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Each call uses 10 credits, and your Cloud Browser uses 50 credits a day while Billetto is enabled for agents, so 20 calls a day come to 250 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 10 credits each
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.

Questions

Does Billetto have an 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.

How do I get access?

Sign up free, open Billetto under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Billetto yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Billetto sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: refund_tickets, cancel_free_tickets, resend_ticket, add_order_note, create_access_code, send_guest_report, clone_event wait for your OK by default. You can switch that off per tool for scheduled runs.

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.

Should I use a Billetto MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Billetto changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

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 Cotlet affiliated with Billetto?

No. Cotlet is independent and not affiliated with Billetto.

Give your agent access to Billetto.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free