ticketing.colosseo.it APIticketing.colosseo.it ↗
Access Colosseum ticket categories, real-time availability calendars, and pricing tiers via the ticketing.colosseo.it API. 5 endpoints covering the Parco Archeologico del Colosseo.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/924d7e24-d7ef-4bd0-a4b6-93106e3f31e1/get_homepage' \ -H 'X-API-Key: $PARSE_API_KEY'
Get homepage notices and ticket categories.
No input parameters required.
{
"type": "object",
"fields": {
"notices": "array of strings",
"categories": "array of category objects with name, slug, url, description"
},
"sample": {
"data": {
"notices": [
"CHIUSURA AREA FORI IMPERIALI DAL 6 FEBBRAIO 2026 Il Parco archeologico del Colosseo resta interamente visitabile fino alla Curia Iulia compresa. Non sarà possibile accedere alla zona compresa dalla Curia Iulia verso via dei Fori Imperiali. Per la verifica della stabilità dei pini di via dei Fori imperiali, a seguito del provvedimento di chiusura della viabilità di via dei Fori Imperiali (DDT Polizia Roma Capitale RI/4030 del 3 febbraio 2026), Roma Capitale ha disposto la chiusura dell’area dei Fori Imperiali a partire dalla passerella di collegamento con l’area del Parco archeologico del Colosseo."
],
"categories": [
{
"url": "https://ticketing.colosseo.it/categorie/percorsi-didattici/",
"name": "Percorsi Didattici",
"slug": "percorsi-didattici",
"description": "Percorsi DidatticiBiglietti validi per:Percorsi di visita guidata in italiano e inglese"
},
{
"url": "https://ticketing.colosseo.it/categorie/singoli-1-8-persone/",
"name": "Singoli",
"slug": "singoli-1-8-persone",
"description": "SingoliBiglietti validi per:Singoli da 1 a 8 persone non accompagnateSingoli da 1 a 8 persone con accompagnatore"
},
{
"url": "https://ticketing.colosseo.it/categorie/gruppi-9-25/",
"name": "Gruppi",
"slug": "gruppi-9-25",
"description": "GruppiBiglietti validi per:Gruppi da 9 a 25 persone con accompagnatore e radioguide obbligatori"
},
{
"url": "https://ticketing.colosseo.it/categorie/scuole-9-25/",
"name": "Scuole",
"slug": "scuole-9-25",
"description": "ScuoleBiglietti validi perGruppi scolastici da 9 a 30 studenti con relativi accompagnatori e radioguide obbligatori"
}
]
},
"status": "success"
}
}About the ticketing.colosseo.it API
This API exposes 5 endpoints covering ticket categories, availability calendars, and pricing tiers for the Parco Archeologico del Colosseo — including the Colosseum, Roman Forum, and Palatine Hill. Starting with get_homepage to retrieve current notices and category listings, you can drill down through ticket details, month-by-month availability slots, and per-slot tariff breakdowns, giving you everything needed to surface real-time visit scheduling data programmatically.
Ticket Categories and Detail
The get_homepage endpoint returns an array of current site notices alongside ticket categories, each with a name, slug, url, and description. Four known category slugs are available for use with list_tickets_by_category: singoli-1-8-persone (individuals and small groups), gruppi-9-25 (groups), scuole-9-25 (schools), and percorsi-didattici (educational itineraries). Each category request returns an array of ticket objects alongside the category name. To retrieve full ticket metadata — including the page_id field required for calendar lookups — call get_ticket_detail with a ticket_slug such as 24h-colosseo-foro-romano-palatino. That response also includes title, conditions, and description fields.
Availability Calendars
get_ticket_availability_calendar accepts year, month, and page_id as required parameters and returns a data array of time slot objects for that month, along with a success boolean. The page_id must come from a prior get_ticket_detail call. Each time slot in the response includes a period_id, which is the key input for the next step in the lookup chain.
Pricing Tiers
get_ticket_price_tiers takes a period_id and start_time (both sourced from the availability calendar response) and returns a data array of tariff objects covering the different price categories for that specific slot. The optional ticket_slug parameter provides additional context for the request. This endpoint is where per-ticket-type pricing differentials — such as reduced fares for children or groups — become visible at the slot level rather than as a flat site-wide rate.
- Build a visit-planning tool that shows available time slots for the Colosseum across a given month using the availability calendar endpoint.
- Compare pricing tiers across ticket categories (individual vs. group vs. school) to surface the best-value options for a specific date.
- Monitor availability changes over time by polling
get_ticket_availability_calendarfor a givenpage_idand month. - Aggregate current site notices from
get_homepageto flag closures or special conditions before recommending a visit date. - Enumerate all tickets within the
percorsi-didatticicategory to help educational trip planners identify relevant guided itinerary options. - Feed ticket
conditionsanddescriptionfields fromget_ticket_detailinto a travel itinerary app to give users booking context.
| 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 | 250 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 ticketing.colosseo.it provide an official developer API?+
What does `get_ticket_price_tiers` actually return, and how granular is the pricing data?+
get_ticket_price_tiers returns a data array of tariff objects for the specific time slot identified by period_id and start_time. Pricing is slot-level, meaning different time windows on the same day can have different tariff structures. The tariff objects reflect the fare categories the site distinguishes — such as full-price, reduced, and group rates — rather than a single flat admission price.Is there a way to look up a ticket's `page_id` without already knowing the ticket slug?+
list_tickets_by_category with a known category slug to retrieve ticket objects, then call get_ticket_detail with the relevant ticket_slug from that list. The page_id is returned in the get_ticket_detail response and is required for all calendar lookups. There is no shortcut endpoint that maps slugs to page_id values directly.Does the API support booking or purchasing tickets, or checking seat/slot counts?+
Are all ticket categories reliably available, and does the API handle off-season or temporary closures?+
singoli-1-8-persone, gruppi-9-25, scuole-9-25, percorsi-didattici) reflect the current structure of the site. The get_homepage notices array is the primary signal for closures or scheduling changes — those are returned as plain strings and are not parsed into structured fields. Calendar responses for months with no availability will reflect that in the returned data array.