reachboost leads has 13 commands. Each one lists its arguments, its flags and what it is allowed to change.
Every command also accepts the global flags.
leads events
Get lead events. Read-only. Returns a paginated list of leads enriched with their campaign events.Usage
Event types to filter by. Repeat the parameter or pass a comma-separated list. One of:
connection_request_sent, connection_request_accepted, connection_request_withdrawn, follow_up_sent, follow_up_replied, profile_visited, profile_followed, post_liked. Repeat the flag for several values.Example
leads get
Get lead by UUID. Read-only. Returns a lead by its UUID.Usage
Example
leads list
Get leads. Read-only. Returns all leads in your workspace. Supports filtering by field values.Usage
Examples
leads list-blacklisted
Get blacklisted leads. Read-only. Returns the leads on the workspace blacklist, newest first, with the same filters, paging and views asGET /leads. This is how the outcome of a blacklist or unblacklist request is seen.
Usage
leads add-custom-fields
Add or update custom fields on lead. Changes data. Merges the provided custom fields into the lead. Existing fields with the same name are overwritten.Usage
leads add-tags
Add tags to lead. Changes data. Adds tags to a lead by its UUID.Usage
Example
leads blacklist
Blacklist leads in bulk. Changes data. Puts up to 100 leads on the workspace blacklist. Nothing further is sent to a blacklisted lead, and the lead is skipped when added to a lead list or campaign. The same thing the Blacklist button in the app does.Usage
leads bulk
Create or update leads in bulk. Changes data. Accepts up to 100 leads in one request and processes them in the background. The same batch as the lead list and campaign bulk endpoints, with no destination: each lead is created if it does not exist (matched bylinkedin_profile_url) or updated if it does, and nothing else happens. No lead list and no campaign membership is written.
Usage
The leads to add. Each item has the same shape and rules as
CreateLeadRequest. As JSON, matching the documented shape.leads enrich
Enrich a lead. Destructive: needs —yes. Queues the enrichment of one lead: its LinkedIn profile data, email address, phone number, or any combination. Name the lead bylead_uuid, or by linkedin_profile_url; a URL that matches no lead in the workspace creates one first. Exactly one of the two must be given.
Usage
A LinkedIn profile URL. Normalised the same way as on lead creation; a URL that matches no lead creates one.
What to enrich. An unknown name refuses the request; a repeated one counts once. One of:
linkedin_profile, email, phone. Repeat the flag for several values.leads remove-custom-fields
Remove custom fields from lead. Destructive: needs —yes. Removes custom fields from a lead by its UUID.Usage
leads remove-tags
Remove tags from lead. Destructive: needs —yes. Removes tags from a lead by its UUID.Usage
leads unblacklist
Remove leads from the blacklist in bulk. Changes data. Takes up to 100 leads off the workspace blacklist. Only the block is lifted:blacklisted_at is cleared and campaign enrolments closed by the earlier blacklisting stay as they are, exactly like the Unblacklist button in the app.
Usage
leads update
Update lead. Changes data. Updates a lead by its UUID.Usage
Digits with an optional leading ”+” and common separators (spaces, dashes, dots, parentheses); must contain 6–15 digits.

