Unlock contact phone numbers
Submit personnel records for phone-number enrichment, optionally in an event context.
Use this endpoint after contact or personnel discovery when the integration needs phone numbers. Newly chargeable work consumes 150 credits per contact and returns status: accepted with a task identifier. event_id is optional; omitting it skips event membership validation. When there is no chargeable work, the endpoint can return status: success without a task.
Only poll the phone task endpoint when status is accepted and task_id is present. A 201 response does not guarantee that every phone number will be found. Inspect skipped details and item-level failures, and avoid duplicate submissions while a task is pending or processing.
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 Body
Batch phone enrichment request with optional event context.
Lensmor personnel identifiers selected for this batch operation.
1 - 2000 elementsOptional Lensmor event identifier returned as id or eventId. When omitted, event membership validation is skipped.
1 - 100"26855"
Response
Phone unlock submission accepted, or completed with no chargeable work
- Option 1
- Option 2
Email or phone unlock submission outcome, including accepted work and skipped records.
accepted when an asynchronous task was created; success when there was no chargeable work to enqueue.
accepted, success "accepted"TaskCenter identifier. Present when status is accepted.
^[0-9]+$"321"
Alias of task_id. Present when status is accepted.
^[0-9]+$"321"
Submitted personnel identifiers that did not create chargeable work.
Reasons submitted personnel records were skipped, grouped by condition.