> 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/ticket-codes.md).

# Ticket codes

Reduce cars, use public transport, here's a free code!

Ticket codes give you the ability to add unique codes to tickets. A good example is discount codes for public transport.

Once you created the ticket code object you are able to add the unique codes. Per import you can add up to 3000 codes. The total number of codes is unlimited.

Per ticket code you have the option to attach a [filter](https://docs.eventication.com/event/general/filters.md) for [members](https://docs.eventication.com/event/planning/members.md), and one for [form visitors](https://docs.eventication.com/event/accreditation/lists/forms/attendees.md). This ensures only the required subset receives these codes.&#x20;

{% hint style="info" %}
If a person has already downloaded their ticket once, redownloads afterwards will still show the same ticket codes.
{% 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/accreditation/ticket-codes.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.
