> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/planning/members/ticket-integration.md).

# Ticket integration

A list of entry tickets

{% hint style="info" %}
If you have a [ticket integration](/event/general/integrations.md), this page title will be the name of the ticket service you have activated. For example [See Tickets](/event/general/integrations/see-tickets.md).
{% endhint %}

On this page you see a list of tickets this person has chosen via given [ticket rewards](/event/general/rewards/ticket-rewards.md). You can filter based on the product type or search using the order ID. There are badges to show you if a moderator or the member has downloaded these tickets.

If you need to, you can cancel these tickets. This means the tickets will not work when entering the event. After cancelling you can even destroy these tickets.

{% hint style="warning" %}
When destroying a cancelled ticket, that slot opens up again for the member to select a new ticket using their given reward. Best to leave them cancelled.
{% 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.eventication.com/event/planning/members/ticket-integration.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.