Skip to main content
Build event intelligence workflows with the Lensmor API. Use it to discover trade shows, evaluate event fit, inspect exhibitor and personnel data, 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.21.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:
Authorization: Bearer uak_your_api_key

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.

Unlock event-level coverage

Move from preview results to full exhibitor and personnel access for a selected event.

Enrich contacts

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

Which endpoint should I use?

If you have…Start withWhy
A keyword, geography, or date rangeEvents listBroad event catalog search.
A company website or buyer profileApply profile and get recommended eventsReturns ranked events from profile context.
A known event IDExhibitors list or Personnel listShows event-scoped companies and people, with preview/full access semantics.
A company name and you want companiesExhibitor company searchPrecision-first company lookup.
A company name and you want eventsExhibitor event searchFinds events associated with that company. This can consume credits.
Personnel IDs and you need emailsUnlock contact emailsStarts an async email unlock task.
1

Authenticate every request

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

Check credits before paid workflows

Call GET /external/credits/balance before event unlocks, email unlocks, or reverse event searches.
3

Discover the event or account context

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

Respect preview and rate-limit semantics

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

First request

curl "https://platform.lensmor.com/external/events/list?page=1&pageSize=20" \
  -H "Authorization: Bearer $LENSMOR_API_KEY"
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, and inspect event details.
  • Exhibitors — list exhibitors, search by company context, inspect profiles, and fetch related events.
  • Personnel — list people, 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.