Org APIwigmore-hall.org.uk ↗
Access upcoming Wigmore Hall concert listings via API. Returns event titles, dates, prices, images, and booking priority flags for up to 180 days ahead.
What is the Org API?
The Wigmore Hall API exposes 1 endpoint — list_events — returning up to 180 days of upcoming concert and event listings from one of the UK's leading chamber music venues. Each event object includes 8 fields: id, title, date, group_date, url, subtitle, prices, is_priority_booking, and image_url. Results are paginated at 12 events per page, with total_items and total_pages included in every response.
curl -X GET 'https://api.parse.bot/scraper/a32fa068-a901-4eb3-a28f-cc4e5299ba61/list_events?page=1' \ -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 wigmore-hall-org-uk-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: Wigmore Hall Events API — browse upcoming concerts."""
from parse_apis.wigmore_hall_org_uk_api import WigmoreHall, InputFormatInvalid
client = WigmoreHall()
# List upcoming events, capped to 10 total items
for event in client.events.list(limit=10):
print(event.title, "|", event.date, "|", event.prices)
# Grab the first upcoming event for detail inspection
try:
first_event = client.events.list(limit=1).first()
except InputFormatInvalid as e:
print(f"Invalid request: {e.message}")
first_event = None
if first_event is not None:
print(f"\nNext concert: {first_event.title}")
print(f" Date: {first_event.date}")
print(f" Subtitle: {first_event.subtitle}")
print(f" Prices: {first_event.prices}")
print(f" Priority booking: {first_event.is_priority_booking}")
print(f" Link: {first_event.url}")
print("\nexercised: events.list")
List upcoming events at Wigmore Hall. Returns paginated results of concerts and events from today onward (up to 180 days), ordered chronologically. Each page contains up to 12 events. Use the page parameter to paginate through all results; total_pages and total_items in the response indicate the full result set size.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. Each page returns up to 12 events. |
{
"type": "object",
"fields": {
"page": "current page number",
"events": "array of event objects with id, title, date, group_date, url, subtitle, prices, is_priority_booking, and image_url",
"total_items": "total number of events in the listing",
"total_pages": "total number of pages available"
},
"sample": {
"data": {
"page": 1,
"events": [
{
"id": "61227",
"url": "https://www.wigmore-hall.org.uk/whats-on/202609081930",
"date": "2026-09-08T19:30:00+01:00",
"title": "Nadine Sierra (soprano); Bryan Wagorn (piano)",
"prices": "£60 £53 £43 £33 £18 +£4 booking fee per transaction",
"subtitle": "Gala Season Opening Concert",
"image_url": "https://admin.wigmore-hall.org.uk/images/3Yfq_i3sdeOcSf2klbml9MSPrTY=/6304/format-webp%7Cwidth-400/.phpref52961sizewebextjpgpage1alternative-1watermarkedknoattachtruevaccess_k_7825ZaF",
"group_date": "2026-09-08",
"is_priority_booking": false
}
],
"total_items": 214,
"total_pages": 18
},
"status": "success"
}
}About the Org API
What the API Returns
The list_events endpoint returns a chronologically ordered list of upcoming events at Wigmore Hall, starting from today and covering up to 180 days forward. Each response includes a page field indicating the current page, an events array, and total_items and total_pages counts so you can determine how many requests are needed to retrieve the full listing.
Event Object Fields
Each item in the events array carries a unique id, a title (the concert or performance name), a machine-readable date, and a group_date that reflects the display-friendly date grouping used on the venue's own listings. The subtitle field typically names the performers or ensemble. prices gives ticket pricing information, is_priority_booking is a boolean flag indicating whether the event is in a priority booking window, and image_url points to the event's associated artwork or promotional image. A direct url to the event detail page on wigmore-hall.org.uk is also included.
Pagination
The list_events endpoint accepts a single optional page integer parameter. Each page returns up to 12 events. To retrieve all upcoming events, increment the page parameter from 1 through the value returned in total_pages. The total_items field reflects the full count across all pages, useful for building progress indicators or determining whether new events have been added between polling intervals.
The Org API is a managed, monitored endpoint for wigmore-hall.org.uk — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when wigmore-hall.org.uk 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 wigmore-hall.org.uk 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 upcoming-events feed for a classical music blog or newsletter using
title,date, andurlfields - Alert subscribers when
is_priority_bookingis true for newly listed events - Aggregate Wigmore Hall concerts into a multi-venue London classical music calendar using
dateandgroup_date - Pull
pricesandsubtitledata to compare ticket costs across upcoming performances - Monitor
total_itemsover time to detect when new events are added to the schedule - Build a widget displaying the next 5 Wigmore Hall concerts using paginated results from
list_events - Collect
image_urlassets to pre-populate a visually rich event listing in a mobile app
| 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 Wigmore Hall provide an official developer API?+
What does `is_priority_booking` indicate in the response?+
How far ahead does the `list_events` endpoint look?+
Does the API return individual event detail pages, such as full programme notes or performer biographies?+
list_events endpoint returns summary-level fields: title, subtitle, date, prices, and a URL to the full event page. Detailed programme content is not included. You can fork this API on Parse and revise it to add an endpoint that retrieves full event detail from each event's URL.Are past or archived events available through the API?+
list_events. You can fork this API on Parse and revise it to add an endpoint targeting Wigmore Hall's past events archive if that data is accessible.