Events & Productions
In Peppered terminology:
- Production = a "show" (main event in VoordeMensen) - e.g. "Hamlet" running for a season.
- Event = a specific performance (sub-event in VoordeMensen) - e.g. "Hamlet, 12 May 20:30".
Three endpoints:
| Method | Path | Purpose |
|---|---|---|
GET | /peppered/event | List all events (with optional date filter) |
GET | /peppered/event/{eventId} | Get a specific event |
GET | /peppered/production/{productionId} | Get a production and its events |
List all events
GET /v1/:client_name/peppered/event
Query parameters
| Name | Type | Description |
|---|---|---|
startDate | date (YYYY-MM-DD) | Optional - only return events on or after this date |
endDate | date (YYYY-MM-DD) | Optional - only return events on or before this date |
Response
200 OK - array of Event.
[
{
"eventId": 95,
"eventExternalId": null,
"productionId": 94,
"eventName": "VoordeMensen Demo Event",
"eventType": null,
"eventTags": null,
"start": "2026-04-01T20:30:00+02:00",
"end": "2026-04-01T22:30:00+02:00",
"hallId": 1,
"prices": [
{ "rankId": 42, "amount": 24.5 }
]
}
]
Get specific event
GET /v1/:client_name/peppered/event/{eventId}
Returns a single event, including its availability data.
Response
200 OK - Event with:
prices- full pricing breakdown (all available ticket types / ranks).availability- seat-level availability per rank (if loaded).blockAvailability- counts of blocked seats by category (capacity, press, technical, …).
blockAvailability types
When present, each item describes a seat-status count:
blockType | blockName (Dutch) | Meaning |
|---|---|---|
block | Capaciteit | General capacity block |
perf | Bespeler | Held for performer |
ext | Externe verkoop | Sold externally |
group | Genodigden | Reserved for guests |
press | Pers | Press seats |
wheel | Rolstoel | Wheelchair-accessible |
tech | Techniek | Technical (sound, camera) |
theat | Theater | Theatre hold |
sight | Zichtlijnen | Obstructed view |
Get production
GET /v1/:client_name/peppered/production/{productionId}
Returns a production (main event) with all its child events.
Response
200 OK - Production:
{
"productionId": 94,
"artist": null,
"title": "VoordeMensen Demo Event"
}
Event fields
| Field | Type | Description |
|---|---|---|
eventId | integer | Unique event (sub-event) ID |
eventExternalId | string | null | ID of the event in a linked external system (for example a DIP performance number). null when the event is not linked |
productionId | integer | Parent production (main event) ID |
eventName | string | Event name |
eventType | string | null | event, passepartout, voucher, combi, horeca, product |
eventTags | string | null | Comma-separated keywords |
start | ISO 8601 datetime | null | Event start (date + start time). null for events without a date - see Events without a date |
end | ISO 8601 datetime | null | Event end. null when no end is known, and for events without a date |
hallId | integer | Hall / location ID |
prices | array | Price entries - { rankId, amount } or { priceId, priceName, rankName, amount } |
availability | array | Seat-level availability (only if relation is loaded) |
blockAvailability | array | Block-type counts (only if relation is loaded) |
Events without a date
Some products have no performance date, such as memberships and vouchers. For these, start and end are null - also when the stored date is an empty placeholder. Treat null as "no date" in your integration and do not rely on start being present for every event. Regular events with a date are unaffected.
Production fields
| Field | Type | Description |
|---|---|---|
productionId | integer | Unique production ID |
title | string | Production title |
artist | string | null | Artist / company name |
See also: Cart · Seating & Halls · Public events endpoint