Billetto MCP Server
จัดการคำขอคืนเงิน ส่งไฟล์ PDF อีกครั้ง ส่งรายชื่อผู้เข้าร่วม และจัดการคำสั่งซื้อใน Billetto
เซิร์ฟเวอร์ MCP แบบโฮสต์
npx add-mcp 'https://cotlet.dev/mcp/v1/billetto'ติดตั้งลง Claude Code, Codex, Cursor และอื่นๆ
เอกสาร
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Billetto API and MCP server: Let your AI agent handle your Billetto orders.
Billetto has a public API (v3, version 2026-02-10) that reads events, orders and attendees and sends webhooks, but no MCP server and no endpoint to refund, cancel or resend a ticket (checked 27 Oct 2026). Cotlet runs 14 Billetto tools hosted, over MCP for agents and REST for scripts.
Refund tickets, resend PDFs, send guest lists and manage orders in Billetto. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Billetto
- Page: https://cotlet.dev/integrations/billetto-api-mcp-server
What can you automate in Billetto?
- Refund tickets from a list of guests
- Resend ticket PDFs that never arrived
- Cancel free RSVPs on request
- Mail the guest list to the venue
- Create access codes for partners
- Clone last week's event
Does Billetto have an MCP server or an API?
- Zapier has 15 Billetto triggers, from Attendee Registered to Order Refunded, and 3 searches. Its MCP server exposes only the 3 searches.
- The API can create audience codes and email a business report per event. Access codes on a ticket type and the guest list reports are set in the app.
- n8n and Pipedream have no Billetto app (both pages answer 404). OAuth clients are registered by hand through support@billetto.com.
| What you need | Zapier | Billetto API v3 | Cotlet |
|---|---|---|---|
| Read events, orders and attendees | Find by event name | Yes | Yes |
| Refund or cancel tickets | No | No | Yes, after your OK |
| Resend a ticket PDF | No | No | Yes, after your OK |
| Guest list report by email | No | Business report only | All five report types |
| Access codes and cloned events | No | Audience codes only | Yes |
| Works without writing code | Yes | No | Yes |
Checked 27 Oct 2026. Sources: Billetto API: endpoint reference, Billetto API: Getting started, Zapier: Billetto triggers and actions, Billetto API: OAuth 2.0
How does Cotlet connect to Billetto?
- Sign in to Billetto. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Billetto password, and no refund, ticket or guest list goes out until you approve it.
Connect Billetto to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Enable Billetto for agents. Open a free Cotlet account, log in to Billetto in its Cloud Browser and press Enable for agents.
- Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as a new MCP server or connector in your agent.
- Sign the connection. Chat apps open a Cotlet sign-in page. Code editors, n8n and scripts use an API key from the console.
Billetto rides on https://cotlet.dev/mcp/v1 together with the other apps on your account. If you switch Billetto on after connecting, refresh the connector to load the ticket tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-billetto \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-billetto": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-billetto]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: billetto_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: billetto_write
How to use the Billetto REST API
Create your Cotlet API key
Create a Cotlet API key with access to Billetto and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Billetto in Cotlet and enable it for agents. Account access: Your own Billetto organiser account (it must open My Billetto > Manage for the events your agent works on).
Make your first Billetto API request
REST:
curl https://cotlet.dev/api/v1/billetto/events \
-H "Authorization: Bearer $COTLET_API_KEY"
Read events and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "billetto",
"tool": "list_events",
"result": {
"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
}
}
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.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Billetto workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Ticket types of an event with price, quantity and whether an access code is needed. Use list_ticket_types in your configured content report. |
| Make | HTTP > Make a request | Orders across all your events, searched by buyer email, name or order ID. Use list_orders in your configured content report. |
| Python or Node.js | REST API | The guests of one event with ticket type and scan state. Use list_attendees in your configured content report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Billetto; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Billetto API endpoints and MCP tools
Events, ticket types and campaigns
Current events by default, past ones on request. A recurring event comes back as its parent with the time slots.
- List events (
list_events, read): Your events with date, status and tickets sold. - Get event (
get_event, read): One event with its venue, dates, ticket types and sales. - List ticket types (
list_ticket_types, read): Ticket types of an event with price, quantity and whether an access code is needed. - List campaigns (
list_campaigns, read): Discount campaigns of an event or of the account, by status.
Orders and attendees
Orders are found by buyer email, name or order ID across all events, the same three keys Billetto searches by.
- List orders (
list_orders, read): Orders across all your events, searched by buyer email, name or order ID. - Get order (
get_order, read): One order with its tickets, prices and notes. - List attendees (
list_attendees, read): The guests of one event with ticket type and scan state. - Add order note (
add_order_note, write, asks first): Add a free-text note to an order.
Refunds, cancels and resends
Refunds work only while the event is current. Free tickets are cancelled, paid ones refunded, and a resend goes to the address on the order.
- Refund tickets (
refund_tickets, write, asks first): Request a refund for a whole order or for chosen tickets. - Cancel free tickets (
cancel_free_tickets, write, asks first): Cancel a whole free order or chosen free tickets. - Resend ticket (
resend_ticket, write, asks first): Email a guest their ticket PDF again.
Reports, codes and cloning
Reports go by email, so guest data leaves Billetto. A cloned event still needs its date before you publish it.
- Send guest report (
send_guest_report, write, asks first): Email a guest list or sales report of an event. - Create access code (
create_access_code, write, asks first): Create an access code for a ticket type, with an optional limit. - Clone event (
clone_event, write, asks first): Copy an event, with the optional settings you choose to keep.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/billetto-api-mcp-server#tools
Who can see my Billetto session, and how do I revoke it?
- What we store. Your logged-in Billetto profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 14 Billetto tools. Never the cookie or your payout details.
- What the session sees. What your login opens: events, buyers, emails, answers to booking questions.
- What no tool touches. Payouts, bank details, team members, publishing and deleting events.
- Use a sub-user if you like. Billetto lets you add sub-users with set permissions. Log in as one for the agent.
- How to cut access. Disable for agents, reset the browser or delete the API key.
Qualys SSL Labs, securityheaders.com and Mozilla Observatory grade our site A+ (live results). A SOC 2 report or third-party pentest does not exist yet.
Is it against Billetto's terms? Account safety
Users have no right to and agree not to use any Site Content for their own commercial purposes or to use any means to extract data from the Site(s).
Billetto's terms never mention robots, bots or AI agents. Section 11 targets the public listings, yet "any means to extract data" can be read to cover an agent that reads your own orders. Section 13 says the account rules "apply equally to any third parties to whom the User grants account access", and section 4.2 lets Billetto end access for misuse. We found no public case of an organiser closed for automation (checked 27 Oct 2026).
How we keep your account looking like you:
- Your own organiser login, typed in by you
- One Cloud Browser with its own IP and cookies
- Refunds, resends, codes and reports wait for your OK
- No tool publishes, deletes or pays out
- If Billetto objects, we pause the Billetto tools for everyone within 24 h
Billetto's own API asks for a one-minute pause after a rate limit. Spread a long refund list after a cancelled show over an hour, not a few seconds.
What happens when Billetto changes?
- 12 h between tests of the Billetto order and event reads
- 24 h between tests of refunds and emails guests would get
- $0 for a call to a Billetto tool paused for repair
When Billetto reworks the order page or the refund popup, the fix lands on our side. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Finds the right order. Buyer email plus event, so a second event of the same buyer stays untouched.
- Checks the event date. A finished event cannot be refunded; that order is reported, not tried.
- Waits for your OK. Order, tickets and amount show up in your Cotlet console.
- Reports the money. Amount per order, skipped orders and buyers not found.
| Action | Undo |
|---|---|
| Refund tickets | No, the money goes back to the buyer's bank |
| Cancel free tickets | No, the guest books again |
| Resend a ticket PDF | No, but a second copy harms nothing |
| Send a guest report | No, the email with guest data is out |
| Create an access code | Change it by hand under Access Codes |
| Clone an event | Fix or drop the copy before you publish it |
| Add an order note | By hand only; it already prints in reports |
All 7 writes ask first: refund_tickets, cancel_free_tickets, resend_ticket, add_order_note, create_access_code, send_guest_report, clone_event. They move money, email a guest or hand out tickets. The 7 reads run at once. Turn the wait off per tool once a nightly run has earned your trust.
A refund leaves Billetto's booking fee out by default. With fees, you pay the full price the buyer paid and Billetto invoices you.
MCP call:
{
"name": "refund_tickets",
"arguments": {
"order_id": "9035127",
"ticket_ids": [
"48210331",
"48210332"
],
"with_fees": false
}
}
REST:
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}'
Response:
{
"order_id": "9035127",
"status": "refund_requested",
"refunded_tickets": [
"48210331",
"48210332"
],
"with_fees": false,
"refund_amount": 50
}
A cron job or script reaches the same tools over REST at /api/v1/billetto, with the same key and price. A Billetto webhook or Zapier trigger such as Order Cancelled can start that script. A refund on a finished event fails and costs nothing. The tools table lists the REST path of each tool.
How much does the Billetto MCP server cost?
About $13 a month for a venue with 4 events a month, 2,250 credits. Billetto keeps charging its ticket fee as before.
| Job | Calls | Credits |
|---|---|---|
| Refund a guest who cannot come | 3 × 6 | 180 |
| Resend a ticket that never arrived | 3 × 8 | 240 |
| Cancel a free RSVP | 3 × 3 | 90 |
| Guest list to the door, weekly | 2 × 4 | 80 |
| Clone the event for next week | 3 × 4 | 120 |
| Access codes for three partners | 4 × 1 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,250 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Same price on Essential and Growth
The month is our example: 4 events of about 60 tickets, 6 refunds, 8 resends and 3 free cancels. Billetto has no monthly fee; the ticket buyer pays 3.99% plus 0.90 per ticket on Essential (27 Oct 2026). Dollars at the $29 pack rate.
Billetto MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| GitHub | No Billetto MCP server among 78 repos. Most are Rails job assignments; Brogede16/billetto-gpt-integration has a one-line README. | 0 stars each, last push of the GPT repo 10 May 2025. |
| Zapier MCP | Find an attendee, event or order from any MCP client. | Three searches, 2 Zapier tasks per call, no writes. |
| MindCloud | One MCP server over 3,100+ apps, Billetto included. | Built on the same API, so reads, webhooks and audiences only. |
| Your own script on API v3 | All reads, webhooks, audience codes and a business report by email. | Needs a developer, and no refund, cancel or resend endpoint exists. |
Pick Zapier to push new orders into a sheet or CRM. Pick the API if you have a developer and need reads at volume. Pick Cotlet when the agent should answer the guest emails: refund, cancel, resend and send the door list.
Who runs Cotlet
Take Group sp. z o.o. builds and runs Cotlet. The company is registered in Poland, EU (VAT PL6342984273), has worked since 2019 and was founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Billetto tools to contact@cotlet.dev.
Billetto API and MCP: questions
How do I get access?
Create a free account at https://cotlet.dev, pick Billetto under Integrations in the console and log in to Billetto in its Cloud Browser. Your trial starts at once and asks for no card.
How do I connect Billetto to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Billetto once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Billetto account through Cotlet, in their phone apps too.
What can ChatGPT do in Billetto?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Billetto: refund tickets from a list of requests; resend tickets to guests who did not get them; email the guest list to the venue. You ask in plain words, and anything that reaches other people waits for your OK first.
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.
Does Billetto have webhooks?
Yes. The API sends webhooks, set under Integrate > Developers, and Zapier has 15 instant triggers such as Order Cancelled. Use one to start your agent, then let the Cotlet tools do the refund or resend the webhook cannot.
Does it work on billetto.dk, .se and the other countries?
Yes. Billetto runs one platform on 14 country sites, from billetto.dk to billetto.pt. You log in on the site your organiser account uses, and the tools work there.
Can the agent publish or delete an event?
No. clone_event makes an unpublished copy, and you publish it yourself in Billetto. No tool deletes an event, an order or a guest.
Is the MCP server different from the REST API?
Only the entrance differs. Both carry the same 14 tools, inputs and answers, one API key and one price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with Billetto?
No. Cotlet is independent and not affiliated with Billetto ApS.
Can I use the Billetto API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.