Billetweb MCP by usefulapi
io.usefulapi/billetweb · v1.1.0 · MCP 2025-11-25
Read events, seats, attendees, sales and payouts; check in tickets and create orders in Billetweb.
Reachability
reachable
checked 2026-11-21 05:30 UTC
Registry status active
Tools pinned 18
01a6721fff3d
Tools last changed
unchanged since first capture 2026-11-21
Repo last push 2026-11-21
as of 2026-11-21
GitHub stars 1
as of 2026-11-21
Provenance
Registry namespace io.usefulapi
(domain verified by the official registry)
Repository
github.com/m190/usefulapi-mcp
Website
https://usefulapi.io/billetweb/
Remote endpoints
https://billetweb.usefulapi.io/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-11-21 05:30 | first capture | 18 tools pinned |
Pinned tool definitions (18)
| Tool | Description |
|---|---|
| billetweb_list_events | List the organiser's events with id, name, start/end, place, shop URL, online state, tax rate, tags and contact. Past events are left out unless include_past is set. GET /events. |
| billetweb_get_availability | Remaining places of an event: per session, per category and per ticket type, with avail (-1 = unlimited), quota and sales. Use it to answer 'how many seats are left'. GET /event/{id}/avail. |
| billetweb_list_tickets | The ticket types (tarifs) of an event in display order: id, name, price, category, quota, visibility (0 visible, 1 web, 2 box office, 3 secret link, 4 hidden), sales window, tax and commission. GET /event/{id}/tickets. |
| billetweb_list_sessions | The sessions (séances, dates) of a multi-session event: id, start/end, name, place, quota, total_sales, state (0 open, 1 hidden, 2 box office only, 3 web only, 4 link only, 5 cancelled) and the ticket ids sold in it. GET /event/{id}/dates. |
| billetweb_list_attendees | The attendees (one row per ticket) of one event: name, email, ticket type, price, check-in state (used), session, order id and payment, custom form answers. Filter by session, ticket, buyer, check-in state or when the order changed; use... |
| billetweb_list_all_attendees | The attendees of ALL events, newest changes included, with the same fields as billetweb_list_attendees. Filter by event tag, only unfinished events, buyer, ticket, check-in state or order change time. Billetweb allows 10 attendees calls... |
| billetweb_list_waiting_list | People on the waiting list of an event: name, email, phone, ticket/session wanted, places asked for and whether they were notified. GET /event/{id}/waiting. |
| billetweb_list_accounting | The accounting history: one row per ticket and per money movement, type product_pay (sale) or product_refund (negative price), with price incl. tax, Billetweb fees, tax, payment type, transaction id and payout id (0 = not paid out yet).... |
| billetweb_list_payouts | The bank transfers Billetweb made to the organiser (type out) or took back (type in, negative amount): id, date, net amount, account holder. The IBAN is masked to its last 4 characters. GET /payouts. |
| billetweb_get_payout | The line-by-line detail of one payout: each sale, refund or transfer with ticket reference, order, event, price, fees and tax. Net transferred = sum of price minus sum of fees. Pass a payout id, or a date (yyyy-mm-dd) for all payouts of... |
| billetweb_list_crm_contacts | The organiser's buyer contacts: name, email, first/last purchase, number of orders and tickets, total spent and average ticket price. Filter by email, CRM segment or last change. GET /crm/contacts. |
| billetweb_list_crm_segments | The saved CRM segments (id, name, created, last sync). Use an id as the segment filter of billetweb_list_crm_contacts. GET /crm/segments. |
| billetweb_list_lists | The organiser's custom lists (id, name, key type), such as member or invitation lists used for access control and discounts. GET /lists. |
| billetweb_get_list_data | The rows of one custom list (each row is an array of values, the first being the key). GET /list/{id}/data. |
| billetweb_check_tickets | WRITE: set the check-in state of tickets (composter): 1 = checked in, 2 = checked out, 0 = back to not checked in. Tickets are identified by the ticket id from billetweb_list_attendees (the `id` field, not the order id). Setting the... |
| billetweb_mark_orders_paid | WRITE: confirm the payment of reservation orders (unpaid orders taken as a reservation) with the payment type you were given (card, cash, check, reservation, other). With send_confirmation the BUYER GETS AN EMAIL with the tickets;... |
| billetweb_send_payment_requests | WRITE: SENDS AN EMAIL to each buyer asking them to pay their unpaid reservation. Customers receive it immediately; it cannot be recalled. The order id is `order_id` in billetweb_list_attendees. Needs a read+write key. POST... |
| billetweb_create_offline_orders | WRITE: CREATE new orders (tickets) in an event as if sold off-line: each order takes places from the quota and is recorded as paid with the given payment type (card, cash, check, invitation, reservation, other). Only basic tickets (no... |
Get alerted when this changes.
Email the moment io.usefulapi/billetweb drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/io.usefulapi/billetweb)
Maintain this server? Add the badge to your README. It links your users to this live status page.