> For the complete documentation index, see [llms.txt](https://docs.indinite.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.indinite.co.uk/creating-your-event/tickets-and-pricing.md).

# Tickets & Pricing

<figure><img src="/files/QtjttqPQzhm93ZgdTEq2" alt=""><figcaption></figcaption></figure>

For each ticket type, set:

* **Name** → Early Bird, General, VIP, etc.
* **Price** → How much fun is worth.
* **Quantity** → How many you want to sell.
* **Min Order** → The minimum number of tickets that can be purchased in a single order.
* **Max Order** → The maximum number of tickets that can be purchased in a single order.
* **Sale Start Time** → When tickets start selling.
* **Sale End Time** → When tickets stop selling (auto-ends at event end time).
* **Enable sale** **Toggle** → To hide the tickets from event page
* **Force "Sold Out"** →  Manually Set as Sold Out

{% hint style="info" %}
Tickets will be marked as Sold Out once the total set quantity is reached. Sales will only begin at the specified Sale Start Time.
{% endhint %}

Pro tips:

* Use **Early Bird** tickets to create FOMO.
* Keep **VIP** limited — makes it feel exclusive.
* Double check your prices — nothing hurts more than selling VIP at £1 by mistake 😬.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.indinite.co.uk/creating-your-event/tickets-and-pricing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.