> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/ticketing.md).

# Ticketing

Connect ticketing systems such as Secutix, Aparté, Vivenu, Yurplan and Vivaticket to Apple Wallet and Google Wallet for ticket delivery and live updates.

Apple Wallet and Google Wallet provide a practical ticket delivery channel. An **Add to Wallet** option can complement PDFs and mobile app tickets in confirmation and account flows.

A ticketing solution that only generates a barcode misses most wallet value. Wallet turns the ticket into a live credential. It stays accurate, scannable, and useful throughout the event lifecycle.

## Why wallet tickets

Typical wallet capabilities that become critical at scale:

* **Offline-ready access at the gate.** The pass remains available without browsing email.
* **Always up to date.** Gate changes, start time changes, seat moves, and cancellations can sync.
* **Clear state.** Invalidated tickets can be visibly expired or disabled.
* **Lower support load.** Fewer “where is my ticket?” cases than PDFs and emails.
* **More secure distribution patterns.** Wallet providers offer sharing controls: Apple Wallet can prohibit sharing a pass, and Google Wallet can limit a pass to one user. Both are pass template settings.

<details>

<summary><strong>Real-world examples</strong></summary>

* **Last‑minute gate change:** update “Gate B” on the pass, then notify attendees.
* **Seat change after exchange:** refresh row/seat automatically, without re-downloading PDFs.
* **Event day operations:** add “Doors open” and “Bag policy” on the back of the pass.
* **On-site value:** attach drink vouchers or merchandise pickup instructions to the ticket.
* **VIP experience:** show lounge access rules and a fast-lane entry message.

</details>

## Wallet can support an event, and more than access control

The Wallet Crew works as a wallet layer across systems. Ticketing stays the source of truth for ticket state. Other systems can enrich the same wallet experience. A single program can connect several source systems: CRM and loyalty data can enrich fields, links, and entitlements.

Common sources connected around a ticketing program:

* **Ticketing system:** event, venue, seat, barcode/QR, ticket status, transfers.
* **CRM / customer data:** profile identifiers, segmentation, eligibility, service flags.
* **Loyalty / membership:** tier, benefits, entitlement rules, member-only access.
* **Marketing automation:** controlled messaging and operational notifications.
* **On-site tooling:** scanning and validation workflows.

Wallet becomes a support surface for the event, before and during arrival, and sometimes after. A ticket can contain more than access information, such as venue guidance, event policies, entry instructions, perks, or links to related experiences.

## Connectors

| Platform            | Type             | How changes arrive                                         | Status             | Page                                                                           |
| ------------------- | ---------------- | ---------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------ |
| Secutix             | Native connector | Webhook from Secutix                                       | Documented         | [Secutix](https://docs.thewalletcrew.io/connectors/ticketing/secutix.md)       |
| Yurplan             | Native connector | Webhook (order confirmed, ticket canceled, ticket checked) | Documented         | [Yurplan](https://docs.thewalletcrew.io/connectors/ticketing/yurplan.md)       |
| Aparté (Tick\&Live) | Native connector | Read from the Aparté API when a pass is refreshed          | Documented         | [Aparté](https://docs.thewalletcrew.io/connectors/ticketing/aparte.md)         |
| Vivenu              | —                | —                                                          | Not documented yet | [Vivenu](https://docs.thewalletcrew.io/connectors/ticketing/vivenu.md)         |
| Vivaticket          | —                | —                                                          | Not documented yet | [Vivaticket](https://docs.thewalletcrew.io/connectors/ticketing/vivaticket.md) |

## Ticketing platforms not listed

An unlisted ticketing platform can become a standard connector. The Wallet Crew and the ticketing-platform partner jointly scope that option when the integration can support multiple brands.

For proprietary platforms or tenant-specific requirements, use a [custom connector](https://docs.thewalletcrew.io/connectors/custom-connector.md). Tenant scripting can call APIs, map ticket data, and react to lifecycle signals.

This approach also supports event apps, customer portals, access-control systems, and CRM or loyalty platforms.

## What a ticketing solution should expose for a wallet integration

A wallet integration depends on data quality and lifecycle signals. The most important requirements are stability and change tracking.

A ticketing integration usually needs:

* A stable **ticket identifier** and a **barcode/QR value** used at entry.
* Event metadata like **name**, **date/time**, and **venue**.
* Seat or zone information when applicable.
* Ticket lifecycle states like **active**, **exchanged**, **cancelled**, or **refunded**.
* A way to detect changes, typically via **webhooks** or a scheduled sync.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/connectors/ticketing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
