PuntoTicket APIpuntoticket.com ↗
Access PuntoTicket.com event listings, category filters, keyword search, and ticket pricing by sector for events across Chile via a structured JSON API.
What is the PuntoTicket API?
The PuntoTicket API gives developers structured access to Chile's PuntoTicket.com ticketing platform across 5 endpoints. Use get_all_events to retrieve every active event's title, date, location, image, permalink, and tags, or drill into get_event_detail to fetch venue details, event description, and sector-level ticket pricing for a specific event slug.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/742a64a7-c7d7-429e-9f4d-3b4b32b4425e/get_all_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 puntoticket-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.puntoticket_api import PuntoTicket, Event, EventDetail, Price
client = PuntoTicket()
# List all active events
for event in client.events.list():
print(event.title, event.date, event.location)
# Search for events by keyword
for event in client.events.search(query="teatro"):
print(event.title, event.evento_id)
# Get event detail via sub-resource navigation
for event in client.events.list(limit=1):
detail = event.detail.get()
print(detail.title, detail.venue, detail.date)
for price in detail.prices:
print(price.sector, price.total_price)
Get a list of all active events on PuntoTicket.com. Returns event metadata including title, date, location, image, and permalink.
No input parameters required.
{
"type": "object",
"fields": {
"events": "array of event objects with permalink, image, title, date, location, eventoId, and tags"
},
"sample": {
"data": {
"events": [
{
"date": "Arica - Antofagasta - Coquimbo - Viña del Mar - Curicó - Talca - Chillán - Osorno",
"tags": [],
"image": "https://static.ptocdn.net/images/eventos/ptt008_ch.jpg",
"title": "Los Jaivas 2026 Gira 45 años alturas de Macchu Picchu",
"eventoId": "PTT008",
"location": "-",
"permalink": "/giramacchupicchu-losjaivas"
}
]
},
"status": "success"
}
}About the PuntoTicket API
Event Listings and Discovery
The get_all_events and get_featured_events endpoints both return an array of active event objects, each containing permalink, image, title, date, location, eventoId, and tags. Note that PuntoTicket does not expose a separate featured-only feed, so both endpoints return the same full set of active events. The eventoId field and permalink slug can be used to identify events for downstream lookups.
Filtering and Search
get_events_by_category accepts a category string (e.g., musica, deportes, teatro, familia, especiales) and filters events whose tags match the keyword. If no events match the provided category, the endpoint returns the full active event list rather than an empty response. search_events accepts a query string and performs case-insensitive substring matching against title, location, and permalink; it returns an empty array when no events match.
Event Detail and Ticket Pricing
get_event_detail takes a slug parameter — the path segment from a permalink field, such as museo-y-tour-monumental-2026 — and returns a full event record: title, url, image, description, venue, date, and a prices array of sector pricing objects. The prices array may be empty when pricing has not yet been published for a given event. Slugs are obtained from the permalink fields returned by the listing endpoints.
The PuntoTicket API is a managed, monitored endpoint for puntoticket.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when puntoticket.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 puntoticket.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?+
- Aggregate all upcoming Chilean events into a local events calendar using title, date, and location fields.
- Build a ticket price comparison tool by retrieving sector-level pricing via get_event_detail for multiple events.
- Filter concerts or theater events by tag using get_events_by_category with keywords like 'musica' or 'teatro'.
- Implement a venue-based event finder by running search_events queries against location field values.
- Track newly published events by polling get_all_events and comparing eventoId values over time.
- Display event imagery and metadata in a mobile app using the image, title, and permalink fields from listing endpoints.
| 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.