> 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/fr/ticketing/vivenu.md).

# Vivenu

Connectez la billetterie Vivenu à The Wallet Crew pour distribuer des billets d’événement numériques dans Apple Wallet et Google Wallet avec l’intégration de cartes Wallet.

Vivenu peut être connecté à The Wallet Crew pour distribuer des billets dans **Apple Wallet** et **Google Wallet**.

Cela permet d’ajouter une couche wallet au-dessus de Vivenu et de prendre en charge la distribution de billets mobiles avec des passes wallet à jour.

{% hint style="warning" %}

### Statut de la documentation

La documentation détaillée pour l’intégration Vivenu n’est pas encore disponible.

Pour plus d’informations, [contactez The Wallet Crew](https://www.thewalletcrew.io/contact) pour discuter du périmètre de l’intégration, de la configuration et de la disponibilité.
{% endhint %}


---

# 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/connectors/fr/ticketing/vivenu.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.