Tito
Tito (ti.to) is an event registration and ticketing platform from Team Tito in Dublin, Ireland, used to sell tickets, collect registrations, and check in attendees for conferences and events. Organizers can sell through Tito-hosted event pages or an embeddable widget. The Admin API is a REST/JSON interface at https://api.tito.io/v3 for managing accounts, events, releases (ticket types), tickets, registrations, discount codes, activities, check-in lists, and refunds, authenticated with a secret API token. Tito also emits outbound webhooks for ticket, registration, check-in, and interested-user events, and exposes a separate unauthenticated Check-in API.
Tito publishes 10 APIs on the APIs.io network, including Account API, Activities API, Check-in Lists API, and 7 more. Tagged areas include Event Ticketing, Events, Registration, Ticketing, and Conferences.
Tito’s developer surface includes authentication, documentation, engineering blog, and 8 more developer resources.
Kin Score
APIs 10
Individual APIs this provider publishes, each with its own machine-readable definition.
Tito Account API
Authentication check and account discovery.
Tito Activities API
Capacity-bound sessions releases can attach to.
Tito Check-in Lists API
Lists defining which tickets can be checked in.
Tito Discount Codes API
Percentage or fixed discounts applied at checkout.
Tito Events API
Events that tickets are sold for.
Tito Refunds API
Refund records against registrations.
Tito Registrations API
Orders that group one or more tickets.
Tito Releases API
Ticket types (releases) for an event.
Tito Tickets API
Individual tickets held by attendees.
Tito Webhook Endpoints API
Endpoints Tito POSTs event notifications to.
Scroll for all 10
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Tito Admin API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Tito Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Tito Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Tito Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API