Billetto automation
Refund Billetto tickets for guests with AI
Ten guests email that they cannot come to Friday's show. Each refund means finding the order, opening its details page and clicking through the refund popup.
Cotlet does it in your own Billetto account with list_orders, get_order and refund_tickets, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can Billetto do this on its own?
Billetto's public API v3 has no refund endpoint (checked 23 Oct 2026); its documented endpoints read orders and attendees. Billetto describes a separate guide for refunding every order when you cancel a whole event. Nothing in the help article refunds a list of buyers you name, and the Zapier app only finds orders.
How you do it in Billetto today
- Open My Billetto, choose the event, click Manage, then under Attendees in the left panel click Manage orders. From the account, Manage > Attendees reaches the same list for all events.
- Search or filter for the order by the buyer's email address, name or order ID, and click details on the right.
- To refund the whole order, choose Request refund at the top of the page and follow the steps in the popup. To refund some tickets, tick them and click Request Refund in the top right of the tickets section.
- On the account path you tick the tickets and pick Bulk refund or with fees. With fees, you cover the full price the buyer paid and receive an invoice for your bookkeeping.
- Every request repeats the same clicks, and the order is easy to refund by mistake in the wrong event when two events share a buyer.
How to refund Billetto tickets for guests with AI
Refund the tickets for these buyers of Autumn Jazz Night: maria.jensen@example.com (two General admission, keep the Student ticket), tom.berg@example.com (whole order). Do not cover booking fees.- 01
Find each order
The agent runs list_orders once per buyer on your list, with the email address as query, and narrows by event_id so a buyer with orders in two events is not refunded in the wrong one. A buyer with no match goes on a "not found" list.
- 02
Check what can be refunded
get_order shows each ticket and event_over. Billetto refunds only current events, so an order of a finished event is left alone and reported. A ticket that costs 0 is cancelled with cancel_free_tickets, not refunded, and the agent asks before it does that.
- 03
Choose the scope
The agent refunds the whole order unless you named tickets, as in "two General admission, keep the Student ticket". It matches the names to ticket_ids from get_order and stops when a name matches more tickets than you asked for.
- 04
Keep the fee rule
with_fees stays false unless you say you cover booking fees, because the with fees option makes you pay the full price the buyer paid.
- 05
Refund and report
refund_tickets runs once per order and asks for your OK on each call by default, because it moves money. The agent reports the amount per order and the orders it skipped.
What you get back
Requests on your list: 2
Refunded 2: Maria Jensen, 2 x General admission, 50.00; Tom Berg, whole order, 30.00
Skipped 0 (event still current)
Not found 0
Booking fees not covered, so buyers get the ticket price onlyOther ways to ask
- Refund every order of Pottery Workshop where the buyer wrote "cannot come" in a note, and cover the fees.
- Show me the orders on my list with what each refund would be, but refund nothing yet.
- Cancel the free tickets for these guests and refund the paid ones.
What Billetto allows, and what to know first
- Billetto does not process a refund once the event has been completed; refunds can only be requested for current events.
- By default a refund does not include the Billetto booking fee or any additional services; the with fees option covers the full price the buyer paid and brings you an invoice.
- The buyer gets the money back in their bank account, usually within 5 working days and in some banks up to 21.
- Billetto finds an order by the buyer's email address, name or order ID, which is how the agent looks each one up.
refund_tickets asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.
Sources: Billetto Help: How do I refund tickets for my guests? · Billetto Help: Search across all your events for orders and tickets · Billetto API: endpoint reference · Billetto on Zapier MCP
Call refund_tickets from a script
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}'{
"order_id": "9035127",
"status": "refund_requested",
"refunded_tickets": [
"48210331",
"48210332"
],
"with_fees": false,
"refund_amount": 50
}MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is billetto_write → refund_tickets. Example data.
Schedule it in n8n, Make, Zapier or cronBilletto tools this automation uses
| Tool | Parameters |
|---|---|
| list_orders | query, event_id, cursor |
| get_order | order_id |
| refund_tickets | order_id, ticket_ids, with_fees |
Frequently asked questions
Can it refund orders after the event?
No. Billetto does not process a refund once an event is completed, and the tool returns that error instead of trying.
Is it safe to connect Billetto to Cotlet?
Yes. You sign in to Billetto yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Billetto once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.
Give your agent access to Billetto.
Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Billetto.