Boletia APIboletia.com ↗
Access events, ticket types, venues, and organizer listings from Boletia.com via 8 structured endpoints covering Mexico's event ticketing platform.
What is the Boletia API?
The Boletia API gives developers structured access to Mexico's Boletia.com ticketing platform across 8 endpoints, covering event search, category filtering, venue and organizer listings, and individual ticket pricing details. The get_event_details endpoint alone returns over 10 response fields including geolocation coordinates, organizer contact, sponsors, and event status — data that would otherwise require navigating individual event pages.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/59184974-f081-4784-8476-384826e64ac3/get_homepage_events' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace boletia-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.boletia_api import Boletia, Event, Billboard, EventNotFound
boletia = Boletia()
# Search for concert events
for event in boletia.events.search(query="concierto"):
print(event.name, event.slug, event.category, event.start_date)
# Get homepage featured events
for event in boletia.events.homepage():
print(event.name, event.url)
# Get CDMX music events
for event in boletia.events.cdmx_music():
print(event.name, event.start_date)
# Get events by category
for event in boletia.events.by_category(category="Teatro"):
print(event.name, event.category)
# Get full event details via constructible navigation
event = boletia.event("trail-series-rutas-magicas-2026")
detail = event.details()
print(detail.event_type_subtype, detail.is_saturated)
# Get ticket options for an event
ticket_info = event.ticket_options()
print(ticket_info.event_name, ticket_info.event_slug)
# Get billboard/venue events
billboard = boletia.billboards.get(slug="palcco")
print(billboard.billboard_name, billboard.total_events)
for group in billboard.events_information:
print(group.name, group.date)
# Get organizer events from billboard
org_billboard = billboard.organizer_events()
print(org_billboard.billboard_name, org_billboard.billboard_description)
Get upcoming events currently listed on Boletia, sorted by relevance and start date. Returns up to 20 events with basic information including name, location, tickets, and dates. No parameters required.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer total number of matching events",
"events": "array of event objects with id, name, slug, about, banner, category, start_date, end_date, locations, tickets, and url"
},
"sample": {
"data": {
"total": 937,
"events": [
{
"id": "267652",
"url": "https://trail-series-rutas-magicas-2026.boletia.com/",
"name": "Trail Series Rutas Magicas 2026",
"slug": "trail-series-rutas-magicas-2026",
"about": "TRAIL RUN MEXICO PRESENTA...",
"banner": "IMG6517.jpeg",
"tickets": [
{
"name": "BOLETO A",
"price": "999.00",
"currency": "MXN"
}
],
"category": "Trail",
"end_date": "2026-09-20T07:00:00.000Z",
"locations": [
{
"city": "Estado de México",
"venue": "Estado de México",
"address": "Estado de México, México",
"latitude": 19.4968732,
"longitude": -99.7232673
}
],
"start_date": "2026-04-19T07:00:00.000Z"
}
]
},
"status": "success"
}
}About the Boletia API
Event Discovery and Search
The search_events endpoint accepts a query string and supports full-text matching across event names, venues, and keywords, returning paginated results via limit and offset parameters. Each event object includes id, name, slug, about, banner, category, start_date, end_date, locations, tickets, and url. The get_events_by_category endpoint filters the same result shape by category name — accepted values include 'Conciertos', 'Teatro', 'Trail', 'Conceptual', 'Stand up', and 'Artes Escénicas'. get_homepage_events requires no parameters and returns up to 20 events currently featured on the Boletia homepage.
Event Details and Ticket Types
get_event_details takes an event slug (the subdomain portion of the event URL) and returns the most complete record available: full about text, capacity, status, banner, plus nested objects for contact (email, phone, facebook, instagram, tiktok), location (venue, address, city, state, latitude, longitude), sponsors, preferences (currency, fee settings), and event_type_subtype. get_event_ticket_options uses the same slug input and returns an array of ticket_types with pricing and availability details; note that some events may return an empty array if tickets are not yet published.
Venue, Organizer, and City-Specific Listings
get_venue_events and get_organizer_events both accept a slug and return billboard metadata — billboard_name, billboard_banner, billboard_description — along with events_information: an array of event groups organized by date, each containing event-level detail with pricing ranges. The two endpoints share the same underlying data shape. For geography-specific needs, get_cdmx_music_events requires no input and returns up to 20 live music events filtered to Ciudad de México, using the same event object structure as search and category endpoints.
The Boletia API is a managed, monitored endpoint for boletia.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when boletia.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official boletia.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a Mexico City concert calendar using
get_cdmx_music_eventsfor real-time music event listings. - Display ticket pricing tiers for a specific event by calling
get_event_ticket_optionswith the event slug. - Power a venue page by fetching all upcoming shows at a location via
get_venue_events. - Filter events by genre or type (e.g. 'Teatro', 'Stand up') using
get_events_by_categoryfor a curated discovery feed. - Enrich event records with organizer social links, geolocation, and sponsor data from
get_event_details. - Paginate through search results for 'concierto' using
search_eventswithlimitandoffsetfor a large event index. - List all events under a specific promoter or organizer using
get_organizer_eventswith their billboard slug.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Boletia have an official public developer API?+
What does `get_event_details` return that the search endpoints do not?+
get_event_details returns several fields absent from search results: a contact object with the organizer's email, phone, and social handles (facebook, instagram, tiktok); a location object including latitude and longitude; a sponsors array with logo URLs and websites; a preferences object covering currency and fee configuration; and event_type_subtype for category classification. Search endpoints return a flatter event object intended for listing use cases.Does the API cover past or archived events, or only upcoming ones?+
get_homepage_events, search_events, get_events_by_category, and get_venue_events all sort by start date and return active listings. Historical or past-event data is not currently exposed. You can fork this API on Parse and revise it to add an endpoint targeting past events if Boletia surfaces that data.How does pagination work across endpoints that support it?+
search_events and get_events_by_category both accept limit (max results to return) and offset (number of results to skip) as optional integer parameters. The total field in the response indicates the full count of matching events, which you can use to calculate how many pages exist. get_homepage_events and get_cdmx_music_events return up to 20 events with no pagination parameters.Does the API include sold-out status or remaining ticket inventory per ticket type?+
get_event_ticket_options returns an array of ticket_types with pricing and availability details, but granular real-time inventory counts (e.g. exact seats remaining) are not currently broken out as a dedicated field. You can fork this API on Parse and revise the ticket options endpoint to surface any additional availability fields if needed.