[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.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)

# Resend Billetto tickets to guests who did not get them

> Resend Billetto ticket PDFs to guests who say nothing arrived, one ticket at a time, and list the mistyped addresses for you instead of guessing.

Source: https://cotlet.dev/integrations/billetto-api-mcp-server/resend-tickets-to-guests

The day before an event, guests write that the ticket email never came. Each message means finding the ticket in Manage Tickets and pressing Resend PDF.

Cotlet does it in your own Billetto account with list\_orders, get\_order and resend\_ticket, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=billetto) [All Billetto tools](https://cotlet.dev/integrations/billetto-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Billetto do this on its own?

Billetto's public API v3 has no endpoint to resend a ticket (checked 23 Oct 2026), and its Zapier app has find actions for attendees, events and orders but none that sends a ticket. Resending is a button on the ticket in Manage Tickets.

## How you do it in Billetto today

1. Open My Billetto, choose the event and press Manage.
2. In the left-side panel open Attendees, then Manage Tickets, and click the ticket in question.
3. Three buttons appear: Download PDF, Resend PDF and Forward PDF.
4. Resend PDF is for a guest who entered the correct email address but did not receive the ticket. Forward PDF is for a wrong address: it opens your email client and you send the ticket to the new address yourself.
5. Orders with several tickets need one click per ticket, and the replies from guests pile up in your inbox until each one is handled.

## How to resend Billetto tickets to guests who did not get them

Prompt

```
Guests of Autumn Jazz Night wrote to say their ticket never arrived. For each email in this list, resend the ticket. If they say they mistyped their address, put them on a list for me instead.
```

1. 01  
### Find the guest's order  
list\_orders runs with the guest's email address as query and the event\_id you named. If two orders match, the agent takes the one placed first for that event and tells you about the other.
2. 02  
### Read the tickets  
get\_order lists each ticket of the order. Cancelled or refunded tickets are left out, so a guest whose ticket was refunded does not get a PDF that no longer works.
3. 03  
### Detect a wrong address  
If the guest's message names a different address than the one on the order, the agent does not resend. Billetto's answer for that is Forward PDF from your own email client, so the agent lists the guest and the new address for you.
4. 04  
### Resend each ticket  
resend\_ticket runs once per ticket and each call asks for your OK by default, because it sends an email to a guest.
5. 05  
### Report who is done  
The agent reports per guest which tickets were sent and to which address, and which guests still need Forward PDF.

### What you get back

Example data

```
Guests on your list: 3
Resent 4 tickets to 2 guests, e.g. Maria Jensen, 2 tickets to maria.jensen@example.com
For you: Lena Koch says she typed lena.k@exmaple.com, use Forward PDF
No order found: 0
```

### Other ways to ask

- Every morning, resend tickets to guests who wrote to tickets@ in the last day and list the ones with a wrong address.
- Resend all tickets for Pottery Workshop orders placed today, but only to guests who asked.
- Show me which guests have not been scanned yet, and resend nothing.

## What Billetto allows, and what to know first

- Resend PDF sends the ticket to the email address on the order, and Billetto's help article describes no way to edit that address.
- Forward PDF opens your own email client, and Download PDF gives you the ticket as a file to attach to your own message; neither runs from the agent.
- Billetto's article states no limit on how often a ticket can be resent, and does not say whether a resend invalidates the first PDF.
- Billetto finds an order by email address, name or order ID, which is what the guest's message usually contains.

resend\_ticket asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Billetto Help: How do I resend a ticket to one of my guests?](https://support.billetto.com/hc/articles/115002765705) · [Billetto Help: Search across all your events for orders and tickets](https://support.billetto.com/hc/articles/360018439279) · [Billetto API: endpoint reference](https://api.billetto.com/reference) · [Billetto on Zapier MCP](https://zapier.com/mcp/billetto)

## Call resend\_ticket from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/billetto/tickets/48210331/resend \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"ticket_id": "48210331",
"order_id": "9035127",
"sent_to": "maria.jensen@example.com",
"status": "sent"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is billetto\_write → resend\_ticket. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/billetto-api-mcp-server.md#automations)

## Billetto tools this automation uses

__Cotlet Billetto tools used to resend Billetto tickets to guests who did not get them__
| Tool | Parameters |
| -------------- | ------------------------ |
| list\_orders | query, event\_id, cursor |
| get\_order | order\_id |
| resend\_ticket | ticket\_id |

[All 14 Billetto tools with descriptions](https://cotlet.dev/integrations/billetto-api-mcp-server.md#tools)

## Frequently asked questions

### 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.

## More Billetto automations

- [Refund Billetto tickets for guests with AI](https://cotlet.dev/integrations/billetto-api-mcp-server/refund-tickets-for-guests.md)
- [Email the Billetto guest list to your venue](https://cotlet.dev/integrations/billetto-api-mcp-server/email-guest-list-to-venue.md)
- [Billetto API and MCP server: every tool](https://cotlet.dev/integrations/billetto-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## 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.

[Sign up free](https://cotlet.dev/app/signup?app=billetto)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.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.