[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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 status Does Billetto have an API or MCP server?

> Billetto has a self-serve API that mostly reads and documented webhooks; no Billetto MCP server was found (checked 20 Nov 2026). Cotlet API & MCP access score: 3 out of 5. What exists instead, with sources.

Source: https://cotlet.dev/api-status/billetto

Billetto has a public API for event organizers as of 20 November 2026, with API keys an organizer creates in their own account. Billetto says it "gives your own code access to the same data that runs your box office: events, ticket types, orders, attendees, ledger entries, booking questions and target groups." The writes found in its docs are narrow: audience members and webhook subscriptions. Billetto documents webhooks and has a Zapier app with triggers and search steps. No Billetto MCP server, ChatGPT app or Claude connector was found on its sites or in the MCP Registry.

**Cotlet API & MCP access score: 3 out of 5.** A Billetto organizer can read events, orders and attendees from its own software, get webhooks for account events and run Zapier triggers. The writes found in the docs cover audiences and webhook subscriptions only.

Checked 20 Nov 2026 ·[How Cotlet scores](#how-cotlet-scores)·[Report an inaccuracy](mailto:contact@cotlet.dev?subject=Billetto%20API%20status)

Cotlet publishes this page as an independent assessment. Cotlet is not affiliated with, endorsed by or sponsored by Billetto. Billetto is a trademark of its owner. If Billetto's own tools cover what you need, use them first.

Billetto API & MCP report

3/5

Cotlet API & MCP access score 5/10 points

Public API

2/3

MCP server

0/3

Zapier · Make · n8n

1/2

Webhooks

1/1

Data export

1/1

Checked

20 Nov 2026

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=Billetto%20API%20status) [How we score](#how-cotlet-scores)

Public API

Mostly read

2 of 3

MCP server

None

0 of 3

Zapier · Make · n8n

Zapier

1 of 2

Webhooks

Yes

1 of 1

Data export

Ticket list

1 of 1

On this page

1. [01 At a glance](#at-a-glance)
2. [02 Public API](#public-api)
3. [03 MCP server](#mcp-server)
4. [04 Zapier, Make, n8n](#automation)
5. [05 Webhooks](#webhooks)
6. [06 Routes](#routes)
7. [07 How Cotlet scores](#how-cotlet-scores)
8. [08 Sources](#sources)

01 · At a glance

## Billetto API & MCP access at a glance

__Billetto API & MCP access on 20 Nov 2026 5 of 10 points__
| Check | Points | Finding | Source |
| ------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| Public API for businesses | 2 / 3 | Yes. Organizers create the API keys in their account; the docs cover reading events, orders and attendees, with narrow writes | [\[1\]](#source-1) |
| Official MCP server | 0 / 3 | No Billetto-made MCP server, ChatGPT app or Claude connector found on Billetto sites or in the MCP Registry (checked 20 Nov 2026) | [\[2\]](#source-2)[\[3\]](#source-3) |
| Zapier, Make, n8n | 1 / 2 | Zapier: triggers and search steps, no create or update actions found. No app found on Make or n8n | [\[4\]](#source-4)[\[6\]](#source-6) |
| Webhooks | 1 / 1 | Documented, signed, managed in the account or through the API | [\[7\]](#source-7) |
| Data export | 1 / 1 | Ticket lists export from each event and arrive by email | [\[8\]](#source-8) |

Two more facts that earn no points: Billetto's check-in tools scan tickets at the door from a phone or dedicated scanners ([Billetto: Check-in](https://go.billetto.com/manage/check-in)), and Billetto's own integrations page names Zapier ([Billetto: integrations](https://billetto.co.uk/l/integrations)).

02 · Public API

## Does Billetto have a public API?

Yes, mostly read

Billetto documents a public API on its developer hub as of 20 November 2026\. Billetto says it "gives your own code access to the same data that runs your box office: events, ticket types, orders, attendees, ledger entries, booking questions and target groups." An organizer creates the API key pair in their own Billetto account. The writes found in the docs cover audience members and webhook subscriptions; no way to create an event or refund a ticket was found there.

[ Source \[1\] · Billetto developer hub ](#source-1)

03 · MCP server

## Does Billetto have an MCP server?

None found

No Billetto MCP server, ChatGPT app or Claude connector was found on Billetto's developer hub or help center on 20 November 2026\. The official MCP Registry lists none from Billetto.

[ Source \[3\] · Official MCP Registry, search for "billetto", 20 Nov 2026 ](#source-3)

04 · Zapier, Make, n8n

## Does Billetto work with Zapier, Make or n8n?

Zapier

Billetto has a Zapier app, announced in 2022\. On 20 November 2026 its Zapier page lists triggers for attendees, events and orders and search steps to find them, and no create or update actions. No Billetto app was found on Make or n8n on 20 November 2026; the n8n page returns 404.

[ Source \[4\] · Zapier: Billetto integrations ](#source-4)

05 · Webhooks

## Does Billetto have webhooks?

Yes

Billetto documents webhooks: "Billetto uses webhooks to notify your application when an event happens in your account." An organizer manages them in the Billetto account or through the API, and each delivery is signed with a secret.

[ Source \[7\] · Billetto API docs: Webhook overview ](#source-7)

06 · Routes

## How can I connect Billetto to ChatGPT or Claude today?

A Billetto organizer has three routes today, and they do different jobs.

billetto.co.uk Your Billetto organizer account

1. Route 1  
### The Billetto API and webhooks  
For developers: read events, orders and attendees, and get account events as they happen.

  - Resend and refund tickets: not in the docs
  - Read orders and attendees: yes, with code
  - Ask in plain words: needs code
2. Route 2  
### Billetto on Zapier  
Triggers and search steps for attendees, events and orders.

  - Resend and refund tickets: no
  - Read orders and attendees: triggers and searches
  - Ask in plain words: no
3. Route 3  
### [A cloud browser](https://cotlet.dev/integrations/billetto-api-mcp-server.md)  
You sign in to your Billetto organizer account in a browser that runs in the cloud, and your AI agent works on the screens you use: events, attendees, guest lists and reports, finance, campaigns. Cotlet, which publishes this page, is a cloud browser of this kind.

  - Resend and refund tickets: with your login
  - Read orders and attendees: with your login
  - Ask in plain words: with your login

To connect your AI: [Billetto MCP server](https://cotlet.dev/integrations/billetto-api-mcp-server.md).

07 · How Cotlet scores

## How Cotlet scores API & MCP access

Cotlet scores one thing: how easily a business can connect its own software or AI agent to its own account. Five checks give up to 10 points, and the points give the Cotlet API & MCP access score, from 1 to 5.

Points to score

Billetto · 5 points
1. 1 0 or 1
2. 2 2 to 4
3. 3 5 or 6
4. 4 7 or 8
5. 5 9 or 10

Where the 10 points come from

1. API 2 of 3
2. MCP 0 of 3
3. Zapier, Make, n8n 1 of 2
4. Webhooks 1 of 1
5. Data export 1 of 1

__How Cotlet scores API & MCP access: the five checks__
| Check | Points | What earns them |
| ------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Official API for the business account | 0 to 3 | 3: public and self-serve, reads and writes. 2: public, but read only or on a higher plan. 1: by partner approval or as a paid add-on. 0: none |
| Official MCP server | 0 to 3 | 3: reads and writes the business account. 2: works on the business account, read only or limited. 1: exists, but not for the business account, such as an app in ChatGPT for clients. 0: none |
| Zapier, Make, n8n | 0 to 2 | 2: an app on two or more of them, with actions. 1: an app on one, or triggers only. 0: none |
| Webhooks | 0 or 1 | 1: documented webhooks for business events |
| Data export | 0 or 1 | 1: an official export, such as CSV, a report download or a data add-on |

__How Cotlet scores API & MCP access: points to score__
| Points | Score |
| ------- | ---------- |
| 9 or 10 | 5 out of 5 |
| 7 or 8 | 4 out of 5 |
| 5 or 6 | 3 out of 5 |
| 2 to 4 | 2 out of 5 |
| 0 or 1 | 1 out of 5 |

Every score rests on the sources listed on the page and carries the date it was checked. A score changes when the facts change. Cotlet sells a cloud browser that connects AI agents to web apps such as Billetto, and says so on every page of this catalog.

08 · Sources

## Sources

1. \[1\]  
[Billetto developer hub](https://go.billetto.com/resources/developers)  
go.billetto.com Checked 20 Nov 2026
2. \[2\]  
Billetto developer hub and help center, searched for MCP, ChatGPT and Claude, 20 Nov 2026  
go.billetto.com, support.billetto.com Checked 20 Nov 2026
3. \[3\]  
[Official MCP Registry, search for "billetto", 20 Nov 2026](https://registry.modelcontextprotocol.io/v0/servers?search=billetto)  
registry.modelcontextprotocol.io Checked 20 Nov 2026
4. \[4\]  
[Zapier: Billetto integrations](https://zapier.com/apps/billetto/integrations)  
zapier.com Checked 20 Nov 2026
5. \[5\]  
[Zapier blog: new integration, Billetto (2022)](https://zapier.com/blog/updates/2523/new-integration-billetto)  
zapier.com Checked 20 Nov 2026
6. \[6\]  
n8n.io/integrations/billetto returns 404; no Billetto app found on Make, 20 Nov 2026  
n8n.io, make.com Checked 20 Nov 2026
7. \[7\]  
[Billetto API docs: Webhook overview](https://api.billetto.com/docs/webhook-overview.md)  
api.billetto.com Checked 20 Nov 2026
8. \[8\]  
[Billetto Help Center: export or upload a ticket list](https://support.billetto.com/hc/articles/360001943453)  
support.billetto.com Checked 20 Nov 2026
9. \[9\]  
[Billetto: Check-in](https://go.billetto.com/manage/check-in)  
go.billetto.com Checked 20 Nov 2026
10. \[10\]  
[Billetto: integrations](https://billetto.co.uk/l/integrations)  
billetto.co.uk Checked 20 Nov 2026

## Something changed at Billetto?

Write to contact@cotlet.dev and we recheck this page.

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=Billetto%20API%20status) [Connect Billetto to your AI](https://cotlet.dev/integrations/billetto-api-mcp-server.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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.
