> 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/accreditation/lists/forms/ticket-integration.md).

# Ticket integration

A list of entry tickets

{% hint style="info" %}
If you have a [ticket integration](https://docs.eventication.com/event/general/integrations.md), this page title will be the name of the ticket service you have activated. For example [Paylogic](https://docs.eventication.com/event/general/integrations/paylogic.md).
{% endhint %}

This page shows you a list of tickets that have been added by moderators for this form to download. Tickets can be cancelled and destroyed if you need to. You can filter these tickets based on which product they belong to.

Click the <img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2Fgit-blob-5de07eebe72670821ca764c9583a69a6e3734703%2Fplus%20new.jpg?alt=media" alt="" data-size="line"> button to add more tickets this form responsible can download. A picker form will be presented where you can select the amount of tickets that need to be generated. Add an internal comment for archival reasons if you want. After placing the order, the platform will automatically generate all these tickets in the background.

{% hint style="info" %}
As we do not want to cross the limitations our ticket providers have set, only 1 ticket will be generated per second. So if you ordered many, give it some time. Refresh your page to see the updates.
{% endhint %}

## Emailing tickets

You can give tickets an email address. Every address then receives **one email** with a link to its own page, showing all of its tickets of this form: the product, a download button, and whether and when the ticket was last downloaded.

There are two ways to give tickets an address:

* Fill in the optional **Email address** field when you click the <img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2Fgit-blob-5de07eebe72670821ca764c9583a69a6e3734703%2Fplus%20new.jpg?alt=media" alt="" data-size="line"> button. Every ticket of that order gets this address.
* Select tickets in the list and choose **Change email address**. Use **Remove email address** to take it off again.

The contact person of the form can do the same on their own tickets page, once the tickets are available to them.

Some addresses are refused:

* The contact person's own address: they can download these tickets themselves.
* A blocked address: one that bounced or reported our emails as spam. If an address is blocked after it was added, the ticket shows a **blocked address** badge.

### When are the emails sent?

Emails are sent automatically, every 10 minutes, to addresses whose tickets haven't changed for 5 minutes. This way a typo that's corrected right away never gets an email. Only tickets that are not cancelled and have been processed by the ticket service are included.

The **Send emails now** button is optional: it sends the waiting emails right away, without waiting for the next round.

No emails are sent when:

* the event has ended or is cancelled
* the form still has to be approved
* the [**Tickets availability from**](https://docs.eventication.com/event/accreditation/lists/ticket-integration.md) date hasn't passed yet
* the contact person still has to sign mandatory documents before downloading tickets

{% hint style="warning" %}
Every address gets **one** email. The link in it always shows the current tickets, so tickets added or removed later show up there without a new email. Want to let them know? Press **Send emails now**: it sends an up-to-date email to every address whose tickets changed since its last email.
{% endhint %}

{% hint style="info" %}
To protect people from too many emails, a form can email at most as many different addresses per 24 hours as it has tickets. A held-back address that never got an email is sent automatically later. For an up-to-date email that was held back, press **Send emails now** again the next day.
{% endhint %}

### Statuses

Every address shows one badge. Hover it for more details.

* **waiting to be sent**: the email goes out with the next round. Hover to see why it's still waiting.
* **sending...**: the email is on its way.
* **sent**: hover to see when. If the tickets changed since, the hover says so.
* **blocked address**: this address can't receive emails anymore. Give the tickets another address.
* **contact person's own address**: not emailed, the contact person downloads these tickets themselves.
* **nothing to send**: none of the tickets of this address could be processed by the ticket service.

### Filters

Click the filter button to filter the tickets on their product or on their email status: no address, waiting to be sent, sent or blocked address.

### The recipient's page

The page behind the link in the email shows the tickets of that address only. If the tickets aren't theirs, the recipient clicks **These tickets aren't mine**: their address is removed from the tickets, the link stops working, and the tickets can be given to someone else.

When a recipient replies to the email, the reply goes to the contact email address of the list.


---

# 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/accreditation/lists/forms/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.
