Skip to main content
Use this guide when your integration needs to move from discovery to full event-level coverage. Event unlocks are intentionally explicit. Lensmor lets you preview available exhibitor and personnel data first, then spend credits only when the event is worth deeper analysis.
1

Find candidate events

Search the event catalog, rank events, or apply profile matching to identify a shortlist.
2

Inspect the event

Fetch the event detail and confirm the event identity, date, venue, source URL, and available data counts.
3

Preview exhibitors or personnel

Call event-scoped list endpoints. If the event is locked, read the semantics object to understand preview limits.
4

Unlock only when needed

Call POST /external/events/:id/unlock when semantics.unlock indicates more records are available and the event is actionable.

​
1. Search events

curl "https://platform.lensmor.com/external/events/list?keyword=retail&page=1&pageSize=20" \
  -H "Authorization: Bearer $LENSMOR_API_KEY"
For fit-based discovery, use Get event fit score, Rank events, or Apply recommended events.

​
2. Fetch event detail

curl "https://platform.lensmor.com/external/events/139574" \
  -H "Authorization: Bearer $LENSMOR_API_KEY"
Confirm that the event is the one your team expects before unlocking. For example, check name, dateStart, dateEnd, venue, country, url, and any count fields returned by the API.

​
3. Preview event-scoped data

curl "https://platform.lensmor.com/external/personnel/list?event_id=139574&page=1&pageSize=20" \
  -H "Authorization: Bearer $LENSMOR_API_KEY"
Locked events can return a response like this: 
{
  "items": [
    {
      "id": "789",
      "fullName": "Jane Doe",
      "title": "VP of Partnerships",
      "companyName": "Example Retail Co",
      "email": null,
      "contactUnlockStatus": "locked"
    }
  ],
  "total": 120,
  "page": 1,
  "pageSize": 20,
  "hasMore": true,
  "semantics": {
    "accessMode": "preview",
    "previewLimit": 50,
    "counts": {
      "actualTotal": 120,
      "visibleTotal": 20,
      "remainingLockedCount": 100
    },
    "pageState": {
      "requestedPage": 1,
      "accessible": true,
      "maxAccessiblePage": 1
    },
    "unlock": {
      "requiredForMoreResults": true,
      "actionType": "unlock_event_personnel",
      "credits": 2000
    },
    "guidance": {
      "code": "preview_results_truncated",
      "message": "This event is locked. Unlock the event to access the remaining matching results."
    }
  }
}
Use semantics to decide whether to unlock. Do not infer full access from pagination alone.

​
4. Unlock the event

curl -X POST "https://platform.lensmor.com/external/events/139574/unlock" \
  -H "Authorization: Bearer $LENSMOR_API_KEY" \
  -H "x-call-source: api"
The response tells you whether credits were used: 
{
  "success": true,
  "alreadyUnlocked": false,
  "creditsUsed": 2000,
  "balanceAfter": {
    "subscriptionBalance": 0,
    "permanentBalance": 451021,
    "totalBalance": 451021,
    "unlimited": false
  },
  "event": {
    "id": "26855",
    "eventId": "26855",
    "name": "CES 2025"
  }
}
If alreadyUnlocked is true, the event was already available and creditsUsed is 0.

​
Common mistakes

  • Unlocking before checking preview results. Preview first to verify the event has relevant records.
  • Using only the event name as your local key. Store id or eventId so follow-up calls are deterministic.
  • Treating 402 Payment Required as a generic failure. It usually means your integration needs to pause, notify the user, or ask them to add credits.
  • Ignoring semantics. It tells you whether a list is in preview mode or has full access.

List events

Browse events with filters and pagination.

Unlock event

Spend credits to access full event-scoped coverage.

List event exhibitors

Fetch exhibitors for a selected event.

List event personnel

Fetch people associated with a selected event.