Skip to main content
POST
Generate outreach messages

Authorizations

Authorization
string
header
required

Send the full Business API key from Settings -> API Keys, for example Authorization: Bearer sk_your_api_key.

Headers

x-call-source
enum<string>

Identify the caller as api or agent for usage attribution. Defaults to api when omitted.

Available options:
api,
agent

Body

application/json

Batch AI outreach generation request for selected channels and personnel.

personnel_ids
string[]
required

Lensmor personnel identifiers selected for this batch operation. The runtime accepts an empty array, but useful generation requires at least one identifier.

Maximum array length: 2000
Example:
channels
enum<string>[]
required

Output channels to generate: email, linkedin_message, or both. The runtime accepts an empty array, but an empty array creates no useful output.

Available options:
email,
linkedin_message
Example:
event_id
string

Optional internal Lensmor event row identifier from the event response id field. This endpoint currently converts the value directly to BigInt; unlike most event-scoped routes, it does not resolve public eventId. Omit it to skip membership validation and event context.

Pattern: ^[0-9]+$
Example:

"501"

linkedin_message_types
enum<string>[]

LinkedIn variants to generate: inmail, connection_note, and/or connected_message.

Available options:
inmail,
connection_note,
connected_message
Example:
outreach_purpose
string

Optional offer, call-to-action, or purpose context used to personalize the drafts.

Example:

"Invite the contact to a product demo"

Response

Outreach message generation accepted

Item-level outreach generation submissions and optional batch task identity.

items
object[]
required

Records returned on the current page or in the current batch.

taskCenterId
string | null

Numeric TaskCenter identifier returned when at least one outreach generation task was created.

Pattern: ^[0-9]+$
Example:

"321"