Labyrinth Events APIlabyrinthevents.com ↗
Access upcoming featured events from Labyrinth Events via API. Get titles, dates, venues, artists, ticket links, and sold-out status in structured JSON.
What is the Labyrinth Events API?
The Labyrinth Events API exposes 1 endpoint, get_featured_events, that returns all upcoming featured events listed on the Labyrinth Events platform. Each event object includes 10+ structured fields covering title, date and times, venue, location, performing artists, description, ticket purchase URL, info URL, cover image, and sold-out status. Only future events are returned, making the response immediately usable without client-side date filtering.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/cbc585bb-b94c-4811-9125-7a18c0b0ce9e/get_featured_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 labyrinthevents-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.
"""Walkthrough: Labyrinth Events SDK — list upcoming featured events."""
from parse_apis.labyrinthevents_com_api import LabyrinthEvents, ParseError
client = LabyrinthEvents()
# Fetch all upcoming featured events (capped at 10 items)
for event in client.events.list(limit=10):
artists = ", ".join(event.artists) if event.artists else "TBA"
print(f"{event.date} | {event.title} @ {event.venue}, {event.town}")
print(f" Artists: {artists}")
print(f" Time: {event.start_time}–{event.end_time}")
print(f" Sold out: {event.sold_out}")
print(f" Tickets: {event.ticket_url}")
print()
# Use .first() to grab a single event for detailed inspection
try:
event = client.events.list(limit=1).first()
except ParseError as e:
# Upstream structure changed or extraction failed
print(f"Parse error ({e.code}): {e}")
event = None
if event is not None:
print(f"Featured: {event.title}")
print(f" Description: {event.description[:120]}...")
print(f" Info: {event.info_url}")
print("exercised: events.list")
Returns all upcoming featured events listed on the Labyrinth Events homepage. Each event includes title, date, times, venue, location, artists, description, ticket URL, info URL, image, and sold-out status. Only future events are returned (filtered by today's date). Results are ordered by start date ascending. Makes two API calls: one for events with venue data, one for artist/guest names.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer count of events returned",
"events": "array of event objects with full structured detail"
},
"sample": {
"data": {
"total": 3,
"events": [
{
"date": "2026-09-19",
"town": "London",
"title": "Boris Brejcha Reflections tour",
"venue": "Alexandra Palace",
"genres": null,
"artists": [
"Boris Brejcha",
"Frieder & Jakob",
"Ann Clue"
],
"country": "United Kingdom",
"end_time": "22:45",
"info_url": "https://www.labyrinthevents.com/events/boris-brejcha-reflections-2026",
"sold_out": false,
"image_url": "https://qdfiahcfaujnyybepbke.supabase.co/storage/v1/object/public/images/631ce8ac-4194-4537-9e03-1ff0f16c2a4e.jpg",
"start_time": "18:30",
"ticket_url": "https://dice.fm/event/699865f73588140001556352",
"description": "The king of high tech minimal & man in the mask, Boris Brejcha makes his debut at the iconic Alexandra Palace on September 19th for his biggest ever UK show, as part of his 2026 Reflections Tour.",
"indoor_outdoor": null
}
]
},
"status": "success"
}
}About the Labyrinth Events API
What the API Returns
The get_featured_events endpoint returns a top-level total integer alongside an events array. Each object in the array carries the full detail surface Labyrinth Events exposes for a featured listing: title, date, start and end times, venue name, geographic location, an artists list, a free-text description, a direct ticket_url for purchasing, an info_url for the event detail page, a cover image URL, and a boolean sold_out flag.
Inputs and Filtering
The endpoint takes no input parameters — it returns the full set of currently featured upcoming events in a single call. Date filtering is applied server-side so every event in the response is guaranteed to be in the future relative to the current date. There is no pagination; all matching events are returned at once.
Practical Notes
The sold_out field lets you branch immediately in your UI or notification logic without a secondary lookup. The artists field is an array, so multi-artist events (festivals, multi-act nights) are handled naturally. ticket_url and info_url are distinct fields — the former goes directly to a purchase flow, the latter to the event's information page, which is useful when tickets are not yet on sale or the event is sold out.
The Labyrinth Events API is a managed, monitored endpoint for labyrinthevents.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when labyrinthevents.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 labyrinthevents.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?+
- Display a live calendar of upcoming Labyrinth Events on a music or nightlife discovery app using
date,venue, andartistsfields - Send automated sold-out alerts by polling the
sold_outflag and triggering notifications when status changes - Aggregate Labyrinth Events listings into a regional event guide alongside other sources, using
locationandvenuefields - Build a waitlist or resale lead-gen tool that surfaces events where
sold_outis true and links toticket_url - Populate artist profile pages with upcoming live dates by matching
artistsarray entries to your own artist database - Monitor event announcement freshness by tracking new entries in the
eventsarray across scheduled API calls - Drive email digest campaigns with event
title,description,image, andticket_urlfor subscriber segments
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Labyrinth Events have an official developer API?+
What does the `sold_out` field tell me, and can I filter events by it?+
sold_out field is a boolean on each event object indicating whether tickets are no longer available. The endpoint returns all upcoming featured events regardless of sold-out status, so filtering by that field is done client-side after receiving the full response.Does the API cover past events or events from individual artist or venue pages?+
get_featured_events returns only upcoming events surfaced on the Labyrinth Events homepage; past events and listings from individual artist or venue sub-pages are not included. You can fork this API on Parse and revise it to add an endpoint that targets those pages.How many events are typically returned, and is there pagination?+
total field in the response gives the exact count for each call. There is no pagination; all events are delivered in one response.Does the API return ticket pricing or event capacity details?+
ticket_url linking to the purchase flow where that information is available, and a sold_out boolean. You can fork this API on Parse and revise it to add an endpoint that retrieves pricing details from the linked ticket pages.