> 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/aparte/wallet-pass-content.md).

# Wallet pass content

### Why pass content matters

A wallet ticket should show the information needed at a glance. In most cases, that means the event, the venue, the date, the seat, and the barcode.

The Aparté connector exposes both simple wallet-friendly fields and richer ticket details. This makes it possible to start with a clean design and expand only when needed.

<details>

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

* **Concert ticket**: show the event name, date, gate, block, row, and seat.
* **Theatre ticket**: highlight venue, floor, designation, and rate category.
* **Multi-price event**: display both the main price and supporting pricing labels when relevant.

</details>

### Main information available on the pass

The connector can expose the most common ticketing data used on a wallet pass:

* ticket holder identity
* event and session details
* order reference
* seat and access information
* venue details
* barcode and ticket status

This is usually enough to build a clear event ticket without custom development.

### Common fields used in designs

The most commonly used fields include:

* `aparte.eventLabel`
* `aparte.eventSessionDateStart`
* `aparte.venueLabel`
* `aparte.categoryLabel`
* `aparte.rank`
* `aparte.seat`
* `aparte.doorLabel`
* `barcode`

These fields cover the majority of standard ticket layouts for Apple Wallet and Google Wallet.

### Additional details available

When a pass needs more context, the connector also exposes additional data such as order identifiers, pricing details, customer contact fields, venue address lines, and ticket status.

Examples include:

* `aparte.orderId`
* `aparte.orderItemId`
* `aparte.status`
* `aparte.amounts`
* `aparte.venueCity`

This extra information is useful for richer designs, support flows, or advanced segmentation.

### Keep the design simple

A wallet pass works best when the essential information is immediately visible. In many projects, the first version should focus on the event, seat, venue, and barcode, then add more fields only when they help operations or customer service.

When deeper customization is needed, the full Aparté ticket payload is also available under `debug.aparte.ticket`.

For routing and advanced customization strategy, see [Advanced customization](/connectors/ticketing/aparte/advanced-customization.md).

### FAQ

<details>

<summary><strong>Does every Aparté field need to appear on the wallet pass?</strong></summary>

No. Most passes only need a small set of key fields. The rest can stay available in the background for future use.

</details>

<details>

<summary><strong>Can the same connector support different ticket layouts?</strong></summary>

Yes. Different pass templates can be used when the ticketing program needs several visual designs or content variations.

</details>

<details>

<summary><strong>Is detailed pricing available?</strong></summary>

Yes. The connector can expose both overall pricing data and individual amount components when they exist in Aparté.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/connectors/ticketing/aparte/wallet-pass-content.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.