clorian.com APIclorian.com ↗
Access ticket listings, real-time availability, time slots, and venue data from Clorian-powered ticketing portals like Museo Reina Sofia via 8 endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/7848bdbd-c82d-4cfd-940c-18dd0f675eb6/get_ticket_listing' \ -H 'X-API-Key: $PARSE_API_KEY'
List available individual ticket types for a Clorian venue. Returns all general admission tickets with pricing and descriptions.
No input parameters required.
{
"type": "object",
"fields": {
"data": "array of ticket product objects with productId, name, shortName, slug, price, description, shortDescription, image, and status",
"status": "string indicating success or failure"
},
"sample": {
"data": [
{
"name": "General ticket",
"slug": "general-ticket",
"image": "https://entradas.museoreinasofia.es/cdn/img/clients/MuseoReinaSofia/productos/nouvel_entrada.jpg",
"price": 12,
"status": "enabled",
"productId": 470,
"shortName": "ENTRADA GENERAL",
"description": "<p>Before proceeding with your purchase...</p>",
"shortDescription": "<p><strong>Includes a visit to the Collection...</strong></p>"
}
],
"status": "success"
}
}About the clorian.com API
The Clorian API exposes 8 endpoints covering ticket listings, availability calendars, event data, and venue configuration across cultural institutions using the Clorian ticketing platform. Starting with get_ticket_listing, you can retrieve individual admission products with fields like productId, price, slug, and status, then drill into real-time date and time-slot availability with get_ticket_availability — making it straightforward to build booking flows or monitor capacity for museums and galleries.
Ticket Listings and Detail
get_ticket_listing returns an array of general admission ticket objects, each carrying productId, name, shortName, slug, price, description, shortDescription, image, and status. For group visits or school programs, get_groups_ticket_listing exposes a parallel set of products that also includes a salesGroupId field, which you can then pass as the optional sales_group_id parameter in downstream endpoints. To get the full picture of a single ticket — including opening hours, visitor rules, and configuration entries — call get_ticket_detail with the required product_id; the response returns a nested data object containing product, infos (an array of structured informational blocks), and configurations.
Availability and Time Slots
get_ticket_availability accepts a required product_id and optional date, year, month, venue_id, and sales_group_id parameters. The response includes a calendar field — a date-keyed map of availability statuses for the requested month — and a slots array for a specific date, where each slot object contains eventId, startDatetime, endDatetime, and capacity information. If no date is supplied, the API returns slots for the first available date in the calendar automatically.
Events, Activities, and Platform Metadata
get_events_and_activities returns non-admission products such as film screenings, workshops, and courses, using the same core fields (productId, name, slug, price, image, status) as the ticket listing endpoints. For platform-level discovery, get_clorian_clients lists all venues using the Clorian platform — each entry has a name, url, and tags — and get_clorian_services describes available ticketing and hardware services with title and description fields. The venue_id values returned by get_clorian_clients can be fed directly into get_ticket_availability to scope availability queries to a specific portal.
Configuration and Purchase Initiation
initiate_ticket_purchase accepts a product_id and returns the product's configuration entries, including fields like productConfigurationId, email subjects, and PDF names. This is primarily relevant for group or education products; passing an individual ticket ID will return an empty configuration array. This endpoint is most useful when building pre-booking flows that need to customize confirmation messaging or document output per product.
- Display real-time admission availability calendars for museum booking widgets using
get_ticket_availabilitycalendar and slots data. - Aggregate ticket prices and descriptions across all Clorian-powered venues discovered via
get_clorian_clients. - Build a group booking tool that pulls group ticket options and their
salesGroupIdvalues fromget_groups_ticket_listing. - Surface film screenings and workshops alongside standard admission by combining
get_events_and_activitieswithget_ticket_listingresults. - Automate capacity monitoring by polling
get_ticket_availabilityslot objects for specificeventIdentries and their capacity fields. - Pre-populate booking confirmation templates with configuration data from
initiate_ticket_purchasefor group and education products. - Discover which cultural venues use the Clorian platform and map them by tag category using
get_clorian_clientsresponse fields.
| 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 Clorian provide an official public developer API?+
What does `get_ticket_availability` return beyond a simple yes/no for a date?+
calendar object mapping each date in the requested month to an availability status, and a slots array for a specific date (or the first available date if none is specified). Each slot includes eventId, startDatetime, endDatetime, and capacity details, giving you enough to present timed-entry options to users.Does the API support completing a ticket purchase or payment processing?+
Are all Clorian venues accessible through the ticket listing and availability endpoints, or is coverage limited?+
get_clorian_clients endpoint lists known venues with their url and venue_id values. Ticket listing and availability endpoints are scoped to specific venues via the venue_id parameter, so coverage depends on which venues are discoverable through that endpoint. Venues not yet indexed in the clients list would not be reachable without adding them. You can fork the API on Parse and revise to extend venue coverage.What is the difference between `get_ticket_listing` and `get_groups_ticket_listing`?+
get_ticket_listing returns individual general admission products. get_groups_ticket_listing returns products under group and educational sales categories and includes a salesGroupId field in each result. That salesGroupId value is what you pass as the optional sales_group_id parameter when calling get_ticket_detail or get_ticket_availability to get group-specific pricing and slot data.