Assign leads to a campaign
Assign leads to a campaign — from a saved segment (segment_id) OR an explicit list of lead IDs (lead_ids); provide exactly one of the two. Leads without a campaign are moved into this campaign directly; leads that belong to ANOTHER campaign are copied (the original lead is left untouched — campaigns never share lead rows); leads already in this campaign, or currently being called, are skipped.
Required scope: leads:write (campaigns:write and the legacy calls:write scope are also accepted; keys without scope restrictions have full access).
Authorizations
API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access.
Path Parameters
Campaign ID.
Body
Response
Assignment result counts.