> 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/developers-guides/integration-guides.md).

# Integration guides

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

<details>

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

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

</details>

### In this section

* [Getting started with the API](/developers-guides/integration-guides/getting-started-with-the-api.md)
* [Wallet](/developers-guides/integration-guides/wallet.md)
* [Webhooks](/developers-guides/integration-guides/webhooks.md)
* [Scan API](/developers-guides/integration-guides/scan-api.md)
* [Insights API](/developers-guides/integration-guides/insights-api.md)
* [Custom connectors](/developers-guides/integration-guides/custom-connectors.md)

### How to navigate this section

Start with [Getting started with the API](/developers-guides/integration-guides/getting-started-with-the-api.md) when passes already exist and the first goal is to validate authentication, tenant scope, and a basic management call.

Use [Wallet](/developers-guides/integration-guides/wallet.md) 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

<details>

<summary><strong>Where should most integrations start?</strong></summary>

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.

</details>

<details>

<summary><strong>Why is Wallet grouped under one page?</strong></summary>

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.

</details>

<details>

<summary><strong>When are the other API guides needed?</strong></summary>

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

</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/developers-guides/integration-guides.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.