Skip to main content
Lensmor API responses expose string identifiers so clients can pass values safely across JavaScript, spreadsheets, CRMs, and workflow tools.

​
Event identifiers

Many event-scoped request parameters are named event_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.
id is the Lensmor database row identifier and eventId is the public event identifier. They are returned separately and can differ. Event-scoped resolvers accept either value where the endpoint documents event_id support.
Prefer eventId when storing or exchanging event identifiers with external systems.
POST /external/personnel/generate-outreach-message is a current code-level exception: when event_id is supplied, it must be the numeric internal event id. That endpoint converts the value directly to BigInt and does not resolve public eventId. The related GET /external/personnel/outreach lookup does accept either event identifier.

​
Entity identifiers

Use the identifier returned by the matching resource endpoint:

​
Naming conventions

  • Request parameters use the casing shown on each endpoint page.
  • Event responses include both id and eventId, while exhibitor event matches use matched_event_ids. Use the field names shown on each endpoint page.
  • Contact, phone, LinkedIn activity, and outreach task identifiers are decimal numeric strings. Do not add prefixes such as task_ or phone_.
  • 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.