> For the complete documentation index, see [llms.txt](https://docs.tokenproof.xyz/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tokenproof.xyz/documentation/tokenproof-apps/portal/events/creating-an-event/event-types/ticketed-event.md).

# Ticketed Event

Ticketed events allow organizers to control capacity by offering a limited supply of passes for entry. tokenproof offers various ticketing options:

**Token-gating**: Ticket claiming can be reserved for members of specific communities by using token gates. *Example: to attend Ape Fest, a user might have to own a Bored Ape first in order to be able to claim a ticket.*

**Open ticketing**: In other instances, organizers might choose to make the event open to everyone without needing to prove that they own a particular collectible.

**Tiered ticketing**: Events can include different types of tickets for holders of different communities, or for guests who don’t own any digital collectibles.

**Paid tickets**: tokenproof's Stripe integration allows organizers to price their tickets and ticket tiers.

**Invite list**: Organizers can import email or wallet addresses of guests who don't meet entry requirements but should still receive a ticket and be permitted into the event using the tokenproof app.

**Request-to-Attend ticketing:** Allows organizers to approve attendees after they request tickets. Once approved, tokenproof will send users a push notification and email letting them know they can attend the event. Attendees will find their tickets in the tokenproof App automatically or will receive an email with their ticket QR codes attached if Email Tickets are configured for your event.


---

# 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.tokenproof.xyz/documentation/tokenproof-apps/portal/events/creating-an-event/event-types/ticketed-event.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.