> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/tito.md).

# Tito

Create events and ticket releases, then inspect registrations in Tito.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Tito      | API key        |

### Tito

Connect to Tito to manage events, ticket releases, and registrations.

#### Set up in Tito

1. Prepare the Tito account or service that the workflow will access. Grant access to the required resources and operations.
2. **API key:** Create or copy an API key from your Tito account settings.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Tito**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                            |
| ------------- | -------- | -------------------------------------------------------------------------------------------------------- |
| API key       | Yes      | Create or copy an API key from your Tito account settings. [Provider instructions](https://id.tito.io/). |

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **Tito** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### Create event

Create a test-mode event in Tito.

#### Inputs

| Field         | Type            | Required | Description                                                                          |
| ------------- | --------------- | -------- | ------------------------------------------------------------------------------------ |
| Account       | select (string) | Yes      | The Tito account that will own the event. Options load from the selected connection. |
| Title         | string          | Yes      | The event title.                                                                     |
| Contact email | string          | Yes      | The event contact email address.                                                     |
| Description   | textarea        | No       | Optional event description.                                                          |

#### Outputs

| Field      | Type    | Description                             |
| ---------- | ------- | --------------------------------------- |
| Event      | object  | The created Tito event.                 |
| Event ID   | integer | The Tito event ID.                      |
| Event slug | string  | The event slug for downstream actions.  |
| Test mode  | boolean | Whether the event remains in test mode. |

### List registrations

List registrations for a Tito event.

#### Inputs

| Field            | Type            | Required | Description                                                                              |
| ---------------- | --------------- | -------- | ---------------------------------------------------------------------------------------- |
| Account          | select (string) | Yes      | The Tito account that owns the event. Options load from the selected connection.         |
| Event            | select (string) | Yes      | The event whose registrations will be listed. Options load from the selected connection. |
| Search           | string          | No       | Search registrations by attendee details.                                                |
| Page             | integer         | No       | The one-based page to start from. Minimum: 1. Default: 1.                                |
| Results per page | integer         | No       | Maximum registrations to return. Minimum: 1. Maximum: 100. Default: 25.                  |

#### Outputs

| Field         | Type          | Description                          |
| ------------- | ------------- | ------------------------------------ |
| Registrations | object\_array | The matching registrations.          |
| Next page     | integer       | Pass this value as Page to continue. |
| Total pages   | integer       | Total pages reported by Tito.        |

### Create ticket release

Create a ticket release for a Tito event.

#### Inputs

| Field        | Type            | Required | Description                                                                         |
| ------------ | --------------- | -------- | ----------------------------------------------------------------------------------- |
| Account      | select (string) | Yes      | The Tito account that owns the event. Options load from the selected connection.    |
| Event        | select (string) | Yes      | The event that will receive the release. Options load from the selected connection. |
| Title        | string          | Yes      | The ticket release title.                                                           |
| Quantity     | integer         | No       | Maximum tickets available in this release. Minimum: 1. Default: 50.                 |
| Pricing type | select (string) | No       | How Tito prices the release. Available values: Free, Paid, Donation. Default: free. |
| Price        | number          | No       | Ticket price for a paid release. Minimum: 0.                                        |

#### Outputs

| Field        | Type    | Description                       |
| ------------ | ------- | --------------------------------- |
| Release      | object  | The created Tito ticket release.  |
| Release ID   | integer | The Tito release ID.              |
| Release slug | string  | The new release slug.             |
| State        | string  | The release's current sale state. |

### Get registration details

Retrieve one Tito registration and its tickets.

#### Inputs

| Field        | Type            | Required | Description                                                                      |
| ------------ | --------------- | -------- | -------------------------------------------------------------------------------- |
| Account      | select (string) | Yes      | The Tito account that owns the event. Options load from the selected connection. |
| Event        | select (string) | Yes      | The event that owns the registration. Options load from the selected connection. |
| Registration | select (string) | Yes      | The registration to retrieve. Options load from the selected connection.         |

#### Outputs

| Field        | Type   | Description                       |
| ------------ | ------ | --------------------------------- |
| Registration | object | The registration and its tickets. |

### Check in registration

Check in one ticket from a Tito registration.

#### Inputs

| Field         | Type            | Required | Description                                                                       |
| ------------- | --------------- | -------- | --------------------------------------------------------------------------------- |
| Account       | select (string) | Yes      | The Tito account used to load events. Options load from the selected connection.  |
| Event         | select (string) | Yes      | The event used to load check-in lists. Options load from the selected connection. |
| Check-in list | select (string) | Yes      | The venue or door check-in list. Options load from the selected connection.       |
| Ticket ID     | integer         | Yes      | The numeric Tito ticket ID to check in. Minimum: 1.                               |

#### Outputs

| Field    | Type   | Description                           |
| -------- | ------ | ------------------------------------- |
| Check-in | object | The check-in record returned by Tito. |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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.stackai.com/integrations/catalog/tito.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.
