Skip to main content
Build event and attendee intelligence workflows with the Lensmor API. Use it to discover trade shows, evaluate event fit, inspect exhibitors and attendee source types, access registered Visitor data when available, and unlock contact details when your team is ready to act. Use this documentation to authenticate, make your first request, and integrate Lensmor event, exhibitor, personnel, contact, and recommendation resources into your own workflows. Current documentation version: v0.26.0

​
Base URL

https://platform.lensmor.com All endpoint paths in this documentation are relative to this base URL. For example, GET /external/events/list resolves to GET https://platform.lensmor.com/external/events/list.

​
Get an API key

Create an account at app.lensmor.com, upgrade to a paid subscription plan, then create a user API key from Settings → API Keys. Use the key with the API base URL above:

​
What you can build

Find the right events

Search, filter, and rank trade shows by geography, category, quality, and profile fit.

Evaluate exhibitor opportunities

Match target accounts or buyer profiles against exhibitor data and related event presence.

Understand attendee sources

Distinguish Exhibitor, Social Signals, and registered Visitor records while preserving people with multiple source labels.

Unlock event-level coverage

Move from preview results to base event coverage, registered Visitor access, or both in one atomic action.

Enrich contacts

Start asynchronous email unlock jobs and poll task status until contact data is ready.

​
Which endpoint should I use?

1

Authenticate every request

Create a user API key and send it as Authorization: Bearer sk_your_api_key.
2

Check credits before paid workflows

Call GET /external/credits/balance and the relevant action precheck before event, visitor, email, or reverse-search workflows.
3

Discover the event or account context

Use Events, Exhibitors, Personnel, Contacts, or Profile Matching endpoints depending on your workflow.
4

Preserve attendee source context

Treat sourceType as a multi-value array and keep event-scoped labels separate from source labels aggregated across a person’s related events.
5

Respect preview and rate-limit semantics

Read semantics metadata, handle 402 Payment Required, and back off on 429 Too Many Requests.

​
First request

If the request succeeds, continue with the Quickstart guide. If it fails, check Authentication and Error conventions.

​
Available resources

  • Credits — inspect the API key owner’s current credit balance.
  • Events — browse, score, rank, inspect event details, and unlock base or visitor access.
  • Exhibitors — list exhibitors, search by company context, inspect profiles, and fetch related events.
  • Personnel — list people, interpret attendee source labels, inspect profiles, and fetch related events.
  • Contacts — search contacts, unlock emails, and poll unlock tasks.
  • Profile Matching — apply profile inputs and retrieve recommended events or exhibitors.

​
Shared conventions

​
Stay current

Review the Changelog for newly documented endpoints, behavior clarifications, and machine-readable resource updates. If your integration needs a workflow that is not covered here, contact Lensmor support.