> 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

Follow the main integration paths with The Wallet Crew API: wallet pass issuance and updates, webhooks, scan events, insights and custom runtime logic.

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 write custom connector scripts.

<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

| Goal                                                     | Page                                                                                                                               |
| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Make a first authenticated call                          | [Getting started with the API](https://docs.thewalletcrew.io/developers-guides/integration-guides/getting-started-with-the-api.md) |
| Create, update, and track passes                         | [Wallet passes](https://docs.thewalletcrew.io/developers-guides/integration-guides/wallet.md)                                      |
| Receive events in your backend                           | [Webhooks](https://docs.thewalletcrew.io/developers-guides/integration-guides/webhooks.md)                                         |
| Record barcode and QR scans                              | [Scan API](https://docs.thewalletcrew.io/developers-guides/integration-guides/scan-api.md)                                         |
| Query usage events and metrics                           | [Insights API](https://docs.thewalletcrew.io/developers-guides/integration-guides/insights-api.md)                                 |
| Run custom logic for a system without a native connector | [Scripting](https://docs.thewalletcrew.io/developers-guides/scripting.md)                                                          |


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/developers-guides/integration-guides.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
