Your account
API
Let external tools read and manage your account over Tito's own API.
What you can do here
You create the keys yourself. A key can do what its own capabilities allow, and you can only give it capabilities you already hold.
A key can create another key through the API for up to 30 days with a subset of its own capabilities. A connected AI agent cannot create a separate key. Revoking the original key also revokes its delegated key.
The API reference lists every endpoint with its parameters, a request you can copy, and an example answer using your own account's event. From there you can get a temporary read-only key and send requests to see what comes back. Your account’s copy of the reference opens only for people in your account, once they sign in to Tito.
The API changelog lists what changed in the API, newest first, with the changes that can affect a working integration marked Breaking. Follow its Atom feed to hear about each change as it ships.
You can set an event's venue map location through the API.
You can configure invitation questions through the API.
You can map ticket types to Swapcard groups through the API.
You can list, add and remove people on a waitlist through the API, offer them a place by hand and withdraw an offer, and set up how a ticket type’s waitlist offers places. You can also list the people waiting for a workshop, and switch a workshop's waitlist on or off.
Good to know
Endpoints and fields can change without a new version number, and a change can break an integration built before it.
Check it when a key has been failing. A failed request's status code is amber, or red when the error was on Tito’s side. You can search it by endpoint, filter it by status code, and page back through 90 days. For webhooks, connections, event integrations and terminal readers, it records the request outcome but omits the request and response bodies to keep credentials out of the log.
- Each key on the Keys tab shows how many permissions it has. Select that number to see each one in plain words, with the name the API uses for it underneath.
- A key is created and revoked. To change what one can do, revoke it and create another.
- Tito command line tool, further down the same page, lists the machines somebody has signed in from to work on your theme. See Sign in from your own machine. Revoking one signs that machine out of every account they belong to.
Connect an AI agent
An agent connects to an organizer’s account. People who bought tickets have nothing to connect to.
Your account’s agent address is https://go.tito.io/youraccount/api/mcp, with your own account slug in place of youraccount. Add it to your agent’s Model Context Protocol (MCP) settings:
- In claude.ai or the Claude app, go to Settings → Connectors → Add custom connector and paste the address.
- In Claude Code, run
claude mcp add --transport http tito https://go.tito.io/youraccount/api/mcp.
Sign in through your browser, check the agent, account, permissions, and return address, then authorize the connection. If the agent doesn't ask for particular permissions, you choose between read-only and everything your role can do, the same choice as for an API key. Read-only is chosen to start with. The page also says whether Tito has verified the agent. An agent Tito has verified can stay connected until you disconnect it, if you choose. If it then goes 13 months without being used, it is disconnected. Whoever connected it gets an email three weeks before, and using it once keeps it connected. Every six months, the account’s owners get an email listing every agent connected to the account. Any other agent is connected for 30 days. Either way it only ever has your current permissions. Tito tells a connected agent which actions can’t be undone, such as refunds, cancellations and emails to people, and asks it to check with you before taking one. Revoke it under Settings → API → Connected agents. The account’s owners see every agent connected to it there, with who connected it and when it was last used, and can revoke any of them. Removing someone from the team disconnects the agents they connected. On each event, an agent has the roles you have on that event. Members limited to particular events or series can use connected agents within that access. Account-wide operations still require account-wide access. MCP returns JSON only, so it has no binary upload or download tools and doesn't provide full UI coverage.
Install the Tito skill and its helper for a local agent, then follow the helper’s browser authorization link. Hosted agents need an MCP connection configured in their settings.
Register an app
If you build an app that other Tito accounts connect to, register it under Settings → API → Your apps. Give it a name, its website, the addresses it returns people to after they connect it, and what it can ask for. Tito gives it a client ID and a secret. The secret is shown once, so copy it straight away. How your app connects an account and calls the API, step by step, is in the API reference.
Anybody on any account can then connect the app, and they can only give it what you said it can ask for. Until Tito verifies an app, it shows as not verified and each connection lasts 30 days. To have it verified, open the app and ask Tito to review it. If Tito doesn't approve it, the app's page says why. Once it is verified, other accounts see the details Tito reviewed, and whoever connects it can keep it connected until they disconnect it. If you edit a verified app, other accounts keep seeing the version Tito approved until Tito reviews your changes.
Make a new secret whenever you need one: the old one keeps working for 24 hours. If a secret has leaked, replace it now instead, and the old one stops at once. Deleting the app stops every connection to it on every account. Only the account's owners can register and manage apps.
Download an account copy
An API key with export.pii can download your account data as a SQLite database. The copy leaves out webhook signing secrets, terminal-reader credentials, API-key hashes, preview keys, staff review links and stored API request bodies. The account itself keeps them. Buyer order and ticket links remain in the copy, so treat the download as private data.
Connect a provider
Use POST /connections/{service}/credentials to store a pasted key, or POST /connections/{service}/authorize to get a browser authorization URL. Both require payment.manage. Finish browser consent at the provider. Connection bodies are omitted from request logs.
Event credentials use /events/{slug}/connections/{service}/credentials and require settings.manage. GET /events/{slug}/connections lists their status. Removing an event connection requires POST /events/{slug}/connections/{service}/disconnect with {"confirmed":true}. This deletes Tito's copy of the key. Replace the key at the provider to stop it working elsewhere.