Skip to main content
Make your first Lensmor API request and understand the core objects you will use in most integrations. The Lensmor API is designed around a typical event-intelligence workflow:
  1. Start with a company profile, buyer profile, keyword, or target market.
  2. Discover relevant trade shows and event records.
  3. Inspect exhibitors and people connected to those events, including their Exhibitor, Social Signals, and Visitor source labels.
  4. Unlock base event access, visitor access, full event access, or contact fields only when the data is actionable.

​
Before you begin

You need a valid user API key and an environment capable of sending HTTPS requests. Create an account at app.lensmor.com, upgrade to a paid subscription plan, then create an API key from Settings → API Keys.
Lensmor API keys use the sk_ prefix. Copy the full key value from Settings -> API Keys; the visible prefix alone is not enough for authentication.

​
1. Check your credit balance

Credit-aware workflows return clear billing semantics, but most integrations should still check balance before running unlock operations.
The response includes subscription credits, gift credits, the total balance, and the next reset timestamp when available. This is the same credit pool used by the Lensmor SaaS app.

​
Choose the right starting point

​
2. Search the event catalog

Use the events list endpoint when you need a broad catalog query.
The event list is paginated. Use the eventId field from responses when calling other endpoints:
  • id and eventId currently return the same value for all events.
  • Use eventId when passing to endpoints that accept event_id.
  • Many event-scoped endpoints accept either value.

​
3. Inspect a specific event

After selecting an event, fetch the event detail record.
Use the detail response to confirm event dates, venue, geography, source URL, and available count fields before deciding whether to explore exhibitors or personnel.

​
4. Fetch exhibitors or personnel

Event-scoped lists may return preview results if the event is locked.
Personnel items can include a multi-value sourceType array:
The values map to the product’s Exhibitor, Social Signals, and Visitor labels. A person can have multiple labels, and the API uses "visitors" for the product’s singular Visitor label. See Attendee source types. When the response contains semantics.accessMode: "preview", read semantics.counts.visibleTotal and semantics.unlock.requiredForMoreResults before calling an unlock endpoint. These fields describe base event access and tell you whether more base personnel coverage is available. Visitor is a separate registered-attendee data layer. For Visitor or combined full access, call POST /external/actions/precheck with unlock_event_visitors or unlock_event_full_access before execution. Precheck is read-only and returns current access state, Visitor availability, eligibility, and expected credits.

​
5. Handle errors and limits

Production integrations should handle these responses explicitly:
  • 401 Unauthorized means the API key is missing or invalid.
  • 402 Payment Required means the requested credit-consuming workflow cannot proceed with the current balance or access state.
  • 404 Not Found means the requested event, exhibitor, person, or task does not exist.
  • 429 Too Many Requests means your integration should back off and retry later.
See Error conventions, Credits and access, and Rate limits for shared behavior across endpoints.

​
Next steps

Build attendee intelligence

Segment Exhibitor, Social Signals, and Visitor records without losing multi-source context.

Find and unlock an event

Learn how preview, base event, visitor, and atomic full access work.

Unlock contact emails

Start an email unlock task and poll until the result is ready.