Integration guides

Follow the main integration paths for wallet issuance, updates, events, scans, insights, and custom runtime logic.

Integration guides

This section covers the main integration patterns available in The Wallet Crew. Use it to create passes through enrolment or connector flows, update pass data, validate scans, receive events, query usage data, and configure template or runtime behavior.

Real-world examples

• A brand starts with pass issuance, then adds API-driven updates and webhooks later.
• A ticketing integration creates passes from order events, then validates entries through scans.
• A CRM integration updates loyalty balances and exports lifecycle events to analytics tools.

In this section

• Getting started with the API
• Wallet
• Webhooks
• Scan API
• Insights API
• Custom connectors

How to navigate this section

Start with Getting started with the API when passes already exist and the first goal is to validate authentication, tenant scope, and a basic management call.

Use Wallet for the full pass lifecycle. That section groups pass creation, update flows, and template behavior in one place.

Use the other guides when the integration needs a specific capability such as event delivery, scan ingestion, reporting, or tenant-side runtime logic.

FAQ

Where should most integrations start?

Start with the API guide if passes already exist. Start with the Wallet section if the project still needs to define how passes are created and updated.

Why is Wallet grouped under one page?

The Wallet lifecycle spans creation, updates, and template rendering. Grouping those pages keeps the main guide tree shorter and makes the flow easier to scan.

When are the other API guides needed?

Webhooks, scans, insights, and custom connectors solve narrower integration needs. They usually come after the core Wallet flow is defined.