Setup

Connect Aparté to The Wallet Crew and validate the main configuration.

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.

Real-world examples

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

Connector availability

The Aparté connector must be enabled by The Wallet Crew before setup starts.

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.

1

Fill the connector settings

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

This screen shows where to enter the Aparté API credentials and define the default pass behavior.

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.

2

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.

Share this API key with Aparté when callback access to The Wallet Crew is required.

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

These optional settings control the fallback timezone and the default API request limit.

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

FAQ

Which Aparté access is required?

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

When should The Wallet Crew support be contacted?

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

Why does timezone configuration matter?

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

Is a specific pass template required?

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

Can the default pass type be overridden?

Yes.

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

What rate limiting is used by default?

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.