Registrations
A registration is one person signing up for one event.
Archived registrations are not returned. Archiving is how the Novex UI removes a
registration, so an archived row disappears from both GET /registrations and
GET /registrations/{id} — the detail route returns 404. There is no way to read an
archived registration through the API.
GET /registrations
curl -sS "https://nov3x.com/api/public/v1/registrations?eventId=clx1234567890" \
-H "Authorization: Bearer nvx_live_your_key_here"Scope: registration.read
Query parameters
| Parameter | Type | Notes |
|---|---|---|
limit | integer | Page size, 1–100. Defaults to 25. |
cursor | string | From the previous response’s meta.cursor. |
updatedSince | ISO 8601 | Only registrations updated at or after this instant. |
eventId | string | Restrict to one event. |
status | string | Filter by registration status. |
GET /registrations/{id}
Returns 404 if the registration is not in your workspace.
Fields
| Field | Type | Notes |
|---|---|---|
id | string | Stable identifier |
eventId | string | The event this registration belongs to |
status | string | e.g. CONFIRMED |
name | string | Attendee name |
email | string | Attendee email |
checkedIn | boolean | Whether they have been checked in |
checkedInAt | ISO 8601 or null | When, or null if not checked in |
createdAt | ISO 8601 | Created |
updatedAt | ISO 8601 | Last modified — use for sync |
Check-in
Check-in is state on the registration, not a separate resource: read
checkedIn and checkedInAt. There is no check-in collection to list.
Checking someone in over the API is not available in this release — it is planned for the next one. Today, check-in happens in the Novex app and the kiosk.
⚠️ Badge QR tokens are never returned by this API. A badge token is the entire credential for that badge — anyone holding it could present it and be checked in — so it is not part of any public payload, by design.
What is not included
Attendee phone, company, job title, country and city are stored in
Novex but are not returned by this API in v1. We expose the minimum that
makes the resource useful. If your integration genuinely needs more, tell us —
adding a field is a non-breaking change, so we can do it without a new version.