Skip to content

Start

Quickstart

Create a key, make your first call, register an attendee and verify a ticket in ten minutes.

  1. In your workspace open Settings → API keys and create a key with the scopes you need. Copy it once.
  2. Call /api/v1/me to confirm the key and see its organisation and limits.
  3. List your events and ticket types, then register an attendee against a ticket type.
  4. Point a webhook endpoint at your system to be told when orders complete and people arrive.
Who am Ibash
curl https://eventos.rewardland.sg/api/v1/me \
  -H "Authorization: Bearer eos_live_YOUR_KEY"
Responsejson
{
  "data": {
    "object": "api_key",
    "prefix": "eos_live_abcd",
    "scopes": ["events:read", "attendees:read"],
    "organisation": { "id": "…", "name": "Lion City Events", "slug": "lion-city-events", "plan": "pro" },
    "rate_limit_per_minute": 600
  }
}
List events and ticket typesbash
curl "https://eventos.rewardland.sg/api/v1/events?status=published" -H "Authorization: Bearer $EOS_KEY"
curl "https://eventos.rewardland.sg/api/v1/events/EVENT_ID/ticket-types" -H "Authorization: Bearer $EOS_KEY"
Register an attendee (needs attendees:write)bash
curl -X POST "https://eventos.rewardland.sg/api/v1/events/EVENT_ID/registrations" \
  -H "Authorization: Bearer $EOS_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: crm-contact-10492" \
  -d '{"ticket_type_id":"TICKET_TYPE_ID","name":"Mei Lin","email":"mei@example.com","company":"Orchid Health"}'

The response is the order with its attendees, each carrying an id you can store against your own record. The attendee receives the QR ticket by email unless you pass send_email: false.

Verify a ticket with your own scanner (needs checkin:write)bash
curl -X POST "https://eventos.rewardland.sg/api/v1/check-ins" \
  -H "Authorization: Bearer $EOS_KEY" -H "Content-Type: application/json" \
  -d '{"event_id":"EVENT_ID","code":"EOS-…scanned from the QR…"}'
Every request is authorised against the organisation and the key's scopes, then against the same row-level security rules the EventOS interface uses. A key can never read another organiser's data.
Quickstart · Developers · EventOS