237tickets

Partner API

Use this API to list live events on your site or app, send buyers to 237tickets checkout, and receive a webhook when tickets are paid.

Base URL

https://237tickets.com/api/v1

Authentication

Every request needs an API key. Platform keys see the full live catalog. Organizers create an event-scoped key from the event page — that key only sees that event.

Authorization: Bearer 237k_live_…
# or
X-Api-Key: 237k_live_…

Endpoints

• GET /events — live events (limit, offset, locale=fr|en)
• GET /events/{slug} — ticket types and remaining stock
• POST /checkout-links — body { "event_slug": "cits26" } → hosted checkout URL
• GET /orders/{id} — order + tickets
• GET /me — this partner
• GET /tickets/verify — ticket lookup (event_id + ticket_reference). Organizer keys only see their event.
• GET /openapi — OpenAPI 3.1

cURL

curl https://237tickets.com/api/v1/events \
  -H "Authorization: Bearer 237k_live_YOUR_KEY"

curl "https://237tickets.com/api/v1/tickets/verify?event_id=EVENT_ID&ticket_reference=MB-XXXX" \
  -H "Authorization: Bearer 237k_live_YOUR_KEY"

Verify is read-only. A match returns ticket_reference, ticket_type, buyer_name, buyer_email, buyer_phone, purchase_timestamp. Unknown code or another event returns 200 {} — never another organizer’s data.

Webhooks

When a buyer pays through your checkout link (?partner=your-slug), we POST JSON to the webhook URL set by the event owner. Headers: X-237tickets-Event: order.paid and X-237tickets-Signature: sha256=<HMAC-SHA256 hex of the raw body> with the webhook secret generated on 237tickets (shown once). Event type: order.paid. Use data.order_id as idempotency key. Direct 237tickets.com purchases without your partner parameter are not sent.

← Accueil · GET /api/v1