Unlock event visitor access
Unlock the registered Visitor data layer for an event that already has base event access.
Use this endpoint when Visitor records are available and the caller needs that source in addition to base exhibitor and personnel coverage. Run action precheck with unlock_event_visitors first. A first successful Visitor unlock consumes 3,000 credits, requires an active subscription, and requires Visitor data to be available for the event.
The operation is idempotent for an already unlocked Visitor layer. It does not replace the base event unlock prerequisite. Handle 409 state conflicts and availability failures as workflow states rather than blindly retrying the paid request.
Authorizations
Send the full Business API key from Settings -> API Keys, for example Authorization: Bearer sk_your_api_key.
Headers
Identify the caller as api or agent for usage attribution. Defaults to api when omitted.
api, agent Path Parameters
Lensmor event identifier returned as id or eventId by event responses.
1 - 100Response
Business-error envelope when the caller has no active paid subscription
HTTP 200 business-error envelope returned when an active paid subscription is required.
Business code returned in an HTTP 200 response for this paid-feature guard.
Human-readable explanation suitable for logs or user-facing error handling.
Stable machine-readable error key for a feature unavailable to free users.
"USER_HAS_NO_FEATURE"Request trace identifier to include in support or incident reports.
Optional structured error details; normally omitted for this business guard.