Peppered API endpoints
The Peppered endpoints are authenticated endpoints originally built for the Peppered backoffice-integration. They expose more detail than the public API — customer records, full cart state, bulk exports, seating plans — and are useful for any vendor integration that needs to sync VoordeMensen data.
Authentication required. All Peppered endpoints need an API key. Ask support to issue one for your client. Pass it in the
Authorizationheader.
Base URL
https://api.voordemensen.nl/v1/:client_name/peppered/
Replace :client_name with your short client identifier (e.g. demo).
Authentication
Pass your API key in the Authorization header — as the raw value, no Bearer or other prefix:
Authorization: <your-api-key>
Basic auth is also supported if you prefer — pass the key as the username with an empty password:
Authorization: Basic <base64(your-api-key:)>
Both formats map to the same authentication path in our middleware. Use whichever your HTTP client handles more cleanly.
Endpoint groups
| Group | Resources | Doc |
|---|---|---|
| Customers | Create, find, get, update, manage client-types | Customers |
| Events & Productions | List events, productions, with availability | Events |
| Cart | Full cart lifecycle: create, add, get, checkout | Cart |
| Orders | List and inspect individual orders | Orders |
| Seating & Halls | Hall metadata and seat placement plans | Seating & Halls |
| Exports | Bulk exports for BI / CRM sync | Exports |
| Payment methods | Available payment methods per client | Payment methods |
Naming convention
Peppered endpoints use camelCase field names (e.g. customerId, eventName) — different from the public API, which uses snake_case (e.g. user_email, event_name). This is for compatibility with the original Peppered system.
Typical use cases
- CRM sync — pull customers + orders nightly into your CRM.
- Reporting — daily/weekly export of orders, waiting list, customer types.
- Custom checkout — build your own multi-step checkout with customer identification, cart management, and payment.
- Mobile backoffice — partner apps that manage tickets on the operator side.
See also: Public endpoints · API keys (Dashboard)