# Billetweb MCP server > Read events, seats, attendees, sales and payouts; check in tickets and create orders in Billetweb. A hosted remote MCP server by usefulapi.io, an independent service (not affiliated with Billetweb). - Server URL: https://billetweb.usefulapi.io/mcp - Transport: Streamable HTTP, OAuth sign-in - Status: live - Page: https://usefulapi.io/billetweb/ ## Connect - Claude (claude.ai, Desktop): Customize → Connectors → Add custom connector, name Billetweb, URL https://billetweb.usefulapi.io/mcp. Prefilled dialog: https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Billetweb&connectorUrl=https%3A%2F%2Fbilletweb.usefulapi.io%2Fmcp - Claude Code: `claude mcp add --transport http billetweb https://billetweb.usefulapi.io/mcp`, then run `/mcp` to log in. - Codex: `codex mcp add billetweb --url https://billetweb.usefulapi.io/mcp`, then `codex mcp login billetweb`. - ChatGPT: Plugins → Add custom MCP server, authentication OAuth. - Cursor, VS Code and other MCP clients: add the URL as a remote MCP server. Add only the URL. Do not add an `Authorization` header or an API key to the client config. The server signs you in with OAuth: the login page asks for your **Billetweb API user** and **Billetweb API key**. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401. ## Before you connect Create a key in the Billetweb back office on the [API page](https://www.billetweb.fr/bo/api.php): choose A third party and name it (for example the AI assistant you use), pick **read only** to browse or **read and write** to also check in tickets or create orders, and optionally restrict it to some events. The page then shows the **user** and the **key**. They are used only to call the Billetweb API on your behalf; they are never shown to anyone. ## Example requests - How many tickets are left for my next event? - Who has not checked in yet for Saturday's session? - How much did I sell last month and when is my next payout? - Which buyers are on the waiting list for my concert? ## Pricing - Free: $0, 50 tool calls / month - Pro: $9/mo · $90/yr per user, 10,000 tool calls / month - Pro+: $39/mo · $390/yr per user, 100,000 tool calls / month Each paid plan covers this Billetweb server only. ## Tools (22) ### Read only (14) - `billetweb_list_events`: 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. - `billetweb_get_availability`: 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'. - `billetweb_list_tickets`: List ticket types. 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. - `billetweb_list_sessions`: 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. - `billetweb_list_attendees`: List attendees of an event. 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 updated\_since to fetch only what is new. Billetweb allows 10 attendees calls per minute (shared with billetweb\_list\_all\_attendees), so prefer one filtered call. - `billetweb_list_all_attendees`: List attendees across all events. 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 per minute; use updated\_since for incremental reads. - `billetweb_list_waiting_list`: 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. - `billetweb_list_accounting`: List sales and refunds (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). Period at most 1 year, starting at most 1 year ago. - `billetweb_list_payouts`: 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. - `billetweb_get_payout`: Get payout detail. 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 that day. - `billetweb_list_crm_contacts`: 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. - `billetweb_list_crm_segments`: List CRM segments. The saved CRM segments (id, name, created, last sync). Use an id as the segment filter of billetweb\_list\_crm\_contacts. - `billetweb_list_lists`: List custom lists. The organiser's custom lists (id, name, key type), such as member or invitation lists used for access control and discounts. - `billetweb_get_list_data`: Get custom list content. The rows of one custom list (each row is an array of values, the first being the key). ### Changes data (4) - `billetweb_check_tickets`: Check tickets in or out. 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 same state again is harmless. Needs a read+write key. - `billetweb_mark_orders_paid`: Mark reservations as 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; default is no email. The order id is `order_id` in billetweb\_list\_attendees. Needs a read+write key. - `billetweb_send_payment_requests`: Send payment request emails. 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. - `billetweb_create_offline_orders`: 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 choice passes, packs or seat placement). With send\_tickets the BUYER GETS THE TICKETS BY EMAIL (default: no email). NOT idempotent: calling twice creates two orders, so pass request\_id and check billetweb\_list\_attendees before retrying. Needs a read+write key. ### Your usefulapi plan (4) - `billetweb_usage_status`: Usage status (free-tier meter). Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. - `billetweb_request_feature`: Request a missing feature. Tell usefulapi that the user needs something the Billetweb tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. - `billetweb_upgrade`: Upgrade to Pro or Pro+. Get a paid plan for Billetweb (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus\_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place: call without confirm first, as the reply states the exact charge for this account (the price difference for the rest of the period, or in a free Pro trial the full Pro+ price, as the trial ends); then call with confirm: true. Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter. - `billetweb_cancel_subscription`: Cancel the Pro subscription. Cancel the caller's Billetweb Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run billetweb\_upgrade later to undo the cancel before the period ends. Does not count against the meter. ## FAQ ### What can I do with Billetweb in Claude or ChatGPT? Check how many seats are left for an event. Find who has not checked in for a session. Check attendees in or out at the entrance. Review sales, refunds and payouts for a period. Send payment requests for unpaid reservations. Create offline orders for guests. See [what you can do](https://usefulapi.io/billetweb/#uses) for the details. ### Is this an official Billetweb product? No. usefulapi is an independent service. It is not affiliated with or endorsed by Billetweb. The server calls the Billetweb API with your own Billetweb access, so it sees only the data that your account can see. ### Can I connect Billetweb to Claude or ChatGPT? Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See [the setup steps](https://usefulapi.io/billetweb/#connect). ### What do I need to connect? The login page asks for your **Billetweb API user** and **Billetweb API key**. See [Before you connect](https://usefulapi.io/billetweb/#setup) for where to find them. ### Do I put my Billetweb key or an Authorization header in the client config? No. Add only the URL. Do not add an `Authorization` header or an API key to the client config. The server signs you in with OAuth: the login page asks for your **Billetweb API user** and **Billetweb API key**. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401. ### How do you keep my Billetweb credentials? The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Billetweb API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Billetweb. ### Can the AI change my Billetweb data? Yes, if you approve it. 4 of the 18 Billetweb tools can create or change data. The other 14 are marked read-only. Most MCP clients ask you to approve a tool call before it runs. ### What does it cost? The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Billetweb server only. Cancel any time: your paid plan then runs to the end of the paid period. Run `billetweb_usage_status` to see how many calls you used. ### How do I subscribe or cancel? Ask the AI to run `billetweb_upgrade` and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run `billetweb_cancel_subscription`. Your paid plan continues to the end of the paid period. ### What if a Billetweb tool that I need is missing? Tell the AI what you wanted to do. It can send the request with `billetweb_request_feature`. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day. ### Which AI clients can I use? Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others. ## Links - [Billetweb MCP server page](https://usefulapi.io/billetweb/) - [All servers](https://usefulapi.io/llms.txt) - [Terms of Service](https://usefulapi.io/terms/) - [Privacy Policy](https://usefulapi.io/privacy/) - Support: support@usefulapi.io