Colosseo 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.
What is the Colosseo 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.
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'
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 ticketing-colosseo-it-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.colosseo_ticketing_api import Colosseo, CategorySlug, Category, Ticket, TicketDetail, TimeSlot, Tariff
# Initialize the client
colosseo = Colosseo()
# Step 1: List all ticket categories
for category in colosseo.categories.list():
print(category.name, category.slug)
# Step 2: Browse tickets in the individual category using constructible Category
individual = colosseo.category(slug=CategorySlug.SINGOLI_1_8_PERSONE)
for ticket in individual.tickets.list():
print(ticket.name, ticket.price)
# Step 3: Get full detail (includes page_id for calendar lookups)
detail = ticket.details()
print(detail.title, detail.page_id)
# Step 4: Check availability for a specific month
for slot in detail.availability.list(year="2026", month="7"):
print(slot.start_date_time, slot.capacity, slot.calendar_group_label)
# Step 5: Get pricing tiers for a slot
for tariff in detail.tariffs.list(period_id=slot.period_id, start_time=slot.start_date_time):
print(tariff.label, tariff.amount, tariff.person_tariff)
break
break
Retrieves the homepage of the Colosseum ticketing system, returning current notices (closures, warnings) and the list of ticket categories available for purchase. Categories include individual tickets, group tickets, school tickets, and educational tours.
No input parameters required.
{
"type": "object",
"fields": {
"notices": "array of notice strings (closure announcements, warnings)",
"categories": "array of category objects each with name, slug, url, and description"
},
"sample": {
"data": {
"notices": [
"CHIUSURA ATTICO DEL COLOSSEO DAL 7 AL 14 MAGGIO E DAL 3 ALL’11 GIUGNO 2026"
],
"categories": [
{
"url": "https://ticketing.colosseo.it/categorie/percorsi-didattici/",
"name": "Percorsi Didattici",
"slug": "percorsi-didattici",
"description": "Biglietti 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": "Biglietti validi per:Singoli da 1 a 8 persone"
}
]
},
"status": "success"
}
}About the Colosseo API
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.
The Colosseo API is a managed, monitored endpoint for ticketing.colosseo.it — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ticketing.colosseo.it 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 ticketing.colosseo.it 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 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 | 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 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.