Event identifiers
Many event-scoped request parameters are namedevent_id.
In event-scoped requests, event_id accepts either:
eventId— the event identifier returned in event responses.id— the Lensmor event identifier returned as a string in event responses.
In the current API version,
id and eventId return the same value for all events. You can safely use either one when calling event-scoped endpoints. If they diverge in a future version, eventId is the preferred stable reference for external systems.eventId when storing or exchanging event identifiers with external systems.
Entity identifiers
Use the identifier returned by the matching resource endpoint:| Parameter | Source field | Notes |
|---|---|---|
event_id | event.eventId or event.id | Prefer eventId. |
exhibitor_id | exhibitor.id | Numeric string. |
personnel_id | personnel.id or contact id | Numeric string. |
taskId | task_id from contact unlock response | Used for unlock task polling. |
Naming conventions
- Request parameters use the casing shown on each endpoint page.
- Event responses include both
idandeventId, while exhibitor event matches usematched_event_ids. Use the field names shown on each endpoint page. - Array parameters are route-specific. Some body fields accept arrays directly; some query filters use repeated query parameters. Follow the endpoint page for each route.