Lensmor provides developer-facing access to event, exhibitor, attendee-source, registered Visitor, contact, and profile-matching data through the Lensmor API.
This repository hosts the public documentation site for developers integrating with Lensmor — an AI-native event intelligence platform for B2B teams.
Use the API to:
- Check credit balance before running credit-consuming workflows
- Browse and inspect event data
- Build attendee intelligence with Exhibitor, Social Signals, and registered Visitor source labels
- Search exhibitors using company context and optional event scope
- Retrieve exhibitor and personnel profiles
- Search contacts with company-based inputs and unlock contact emails
- Request profile-matching recommendations for discovery workflows
https://platform.lensmor.com
All documented paths are relative to this base URL. For example:
GET /external/events/listPOST /external/exhibitors/search
- Create an account at app.lensmor.com, upgrade to a paid subscription plan, then create a user API key from Settings → API Keys.
- Send requests to
https://platform.lensmor.com. - Include the authorization header on every request.
- Browse the full interactive docs at api.lensmor.com or use the reference files in this repository.
Authorization: Bearer sk_your_api_keycurl -X GET "https://platform.lensmor.com/external/events/list?page=1&pageSize=20" \
-H "Authorization: Bearer sk_your_api_key"| Start here | Purpose |
|---|---|
| Quickstart | Make your first authenticated request |
| Authentication | API key requirements and authorization format |
| Find and unlock an event | Move from event discovery to event access |
| Build attendee intelligence | Interpret Exhibitor, Social Signals, and Visitor sources |
| Credits and access | Understand preview access and credit-consuming actions |
| Production readiness | Prepare an integration for reliable operation |
| OpenAPI specification | Machine-readable endpoint definitions |
| API catalog | Discover the machine-readable API resources |
| llms.txt · llms-full.txt | Agent-readable documentation |
| Simplified Chinese guides | Core onboarding and access guidance in Chinese |
Use the interactive API reference to browse individual endpoints. The generated references are stored in openapi.json and its copies under api-reference/ and api-reference-backup/.
- Build event discovery and field-marketing workflows
- Segment accessible attendees by Exhibitor, Social Signals, and registered Visitor source
- Match target accounts and exhibiting companies to relevant events
- Prioritize selected attendees and enrich their contact data for sales engagement or CRM workflows
Found a confusing example, missing explanation, or broken documentation link? Open a documentation issue with the page URL, expected behavior, and a redacted example. For account or billing help, use the Lensmor Help Center.
After editing documentation, run the local checks before opening a pull request:
python3 -m unittest scripts/test_sync_public_assets.py
python3 scripts/sync-public-assets.py --checkGenerated public assets should be regenerated with python3 scripts/sync-public-assets.py when their source files change. The existing Docs Quality workflow checks the generated assets, OpenAPI, and Mintlify build on pull requests.
pnpm dlx mintlify devSee changelog.mdx for versioned documentation updates. The current documentation version is v0.27.0.
Built by Lensmor — AI-native event intelligence platform. Turn trade show data into qualified pipeline.