> 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/setup.md).

# Setup

### Why this setup matters

The setup connects The Wallet Crew to the Aparté WalletCrew API. Once configured, Aparté remains the source of truth for ticket data, while The Wallet Crew handles wallet pass creation and updates.

The goal is to make ticket delivery reliable from day one. A correct setup also avoids time, seat, or event mismatches on the pass.

<details>

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

* **Venue rollout**: connect one venue API and issue wallet tickets from the existing sales flow.
* **Pilot launch**: start with one event template, then expand to more events after validation.
* **Operational validation**: confirm that event time, seat, and barcode display correctly before go-live.

</details>

### Connector availability

{% hint style="info" %}
The Aparté connector must be enabled by The Wallet Crew before setup starts.
{% endhint %}

No connector settings can be saved before this enablement.

### Prerequisites

Prepare these values before configuration starts:

* **Base URL** of the Aparté WalletCrew API
* **Tenant** identifier
* **API key**

Keep all credentials environment-specific. Staging and production should use different secrets.

### Setup in 2 steps

The setup is usually quick. Most projects only need one connector, one default template, and one validation ticket.

{% stepper %}
{% step %}

#### Fill the connector settings

Open **Connectors → Aparté** and enter the connection details collected from Aparté.

<figure><img src="/files/3rqU6WcBAKhnvaIYaOCT" alt="Aparté connector configuration screen in The Wallet Crew admin, showing the API connection fields and default pass type settings."><figcaption><p>This screen shows where to enter the Aparté API credentials and define the default pass behavior.</p></figcaption></figure>

Then set these connector options:

* **Default pass type**
* **Invalid pass type**

The **Default pass type** is the fallback template. It can still be overridden in [Advanced customization](/connectors/ticketing/aparte/advanced-customization.md).
{% endstep %}

{% step %}

### Share The Wallet Crew API Key to Aparte

share a **The Wallet Crew API key** with Aparté when Aparté needs to call back into The Wallet Crew.

<figure><img src="/files/N0gt6YEZkXLwIO6z6QL2" alt="The Wallet Crew API key details screen used to copy the key that Aparté needs for callback access."><figcaption><p>Share this API key with Aparté when callback access to The Wallet Crew is required.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

### Test the setup

Set the wallet template **Ticket provider** to `aparte.ticket`.

Then test with one real ticket and confirm:

* the pass opens correctly
* the event time is correct
* the seat and barcode match the source ticket

If the event time is wrong, check the configured default timezone first.

### What each setting does

Only two connector settings matter for a first setup.

* **Default pass type** — fallback wallet template for valid tickets
* **Invalid pass type** — template used when a ticket can no longer be resolved

**Advanced settings**

These settings can be added when needed:

* **Default venue timezone** — fallback timezone used to display local event time
* **Default rate limiting** — API protection limit, set to **500 requests/min** by default

<figure><img src="/files/84MRGGX35Mzy3ldC3r1u" alt="Advanced connector settings showing the default venue timezone and default rate limiting fields."><figcaption><p>These optional settings control the fallback timezone and the default API request limit.</p></figcaption></figure>

This is enough for a first rollout. Advanced routing can come later if needed.

### FAQ

<details>

<summary><strong>Which Aparté access is required?</strong></summary>

The connector uses the Aparté WalletCrew API. The required inputs are usually a base URL, a tenant identifier, and an API key.

</details>

<details>

<summary><strong>When should The Wallet Crew support be contacted?</strong></summary>

Contact The Wallet Crew support before setup starts so the Aparté connector can be enabled on the tenant.

</details>

<details>

<summary><strong>Why does timezone configuration matter?</strong></summary>

Aparté event sessions are tied to local venue time. A wrong timezone can display the wrong event hour on the wallet pass.

</details>

<details>

<summary><strong>Is a specific pass template required?</strong></summary>

A wallet template is required, and it must use the Aparté ticket provider so the mapped ticket fields become available.

</details>

<details>

<summary><strong>Can the default pass type be overridden?</strong></summary>

Yes.

The connector uses the configured default pass type as its fallback, but advanced customization can still route some tickets to another template.

</details>

<details>

<summary><strong>What rate limiting is used by default?</strong></summary>

The default connector rate limit is **500 requests per minute**.

This value can be lowered or adjusted when the Aparté environment has a different quota policy.

</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/setup.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.