Skip to main content
List events related to a single person. Use this endpoint when you want the event associations for one personnel profile in a paginated event-item response.

When to use this endpoint

Use GET /external/personnel/events when you already have a personnel_id and want to understand which events are associated with that person. If your starting point is a LinkedIn URL rather than a Lensmor personnel ID, use Personnel events by LinkedIn.

Endpoint

GET /external/personnel/events

Authentication

See Authentication

Success status code

200 OK

Query parameters

NameRequiredTypeNotes
personnel_idYesstringNumeric-string personnel identifier.
pageNointegerDefaults to 1.
pageSizeNointegerDefaults to 20; maximum 100.

Request example

curl "https://platform.lensmor.com/external/personnel/events?personnel_id=789&page=1&pageSize=20" \
  -H "Authorization: Bearer $LENSMOR_API_KEY"

Response example

{
  "items": [
    {
      "id": "123",
      "eventId": "139574",
      "name": "NRF 2026",
      "nickname": null,
      "description": "Retail industry event",
      "url": "https://example.com/events/nrf-2026",
      "dateStart": "2026-01-12",
      "dateEnd": "2026-01-15",
      "venue": "Javits Center",
      "city": "New York",
      "region": "NY",
      "country": "United States",
      "exhibitorCount": 950,
      "image": null,
      "dataSource": "database"
    }
  ],
  "total": 5,
  "page": 1,
  "pageSize": 20,
  "totalPages": 1,
  "hasMore": false
}

Response fields

FieldDescription
itemsEvents associated with the selected person.
id, eventIdEvent identifiers returned with each event.
name, nickname, description, urlEvent display and source fields.
dateStart, dateEndEvent date range.
venue, city, region, countryLocation metadata.
exhibitorCountKnown exhibitor count when available.
image, dataSourceMedia and source metadata.
total, page, pageSize, totalPages, hasMorePagination metadata.

Error responses

  • 400 Bad Request
  • 401 Unauthorized
  • 404 Not Found
  • 429 Too Many Requests

Notes

  • Event items reuse the standard event-item response shape.
  • Pagination behavior follows the shared Pagination conventions.