Lists
Add Lead List Members
Add leads to a static list (already-present ones are skipped). 409 `segment_members` for a segment.
API key access
Needs the
leads:write scope with an API key (ro_pat_...). A signed-in session uses the caller's role.POST
/api/v1/lists/{list_id}/membersAuthorizationBearer <token>
Access token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Path Parameters
list_idstring
Format
uuidHeader Parameters
X-Workspace-Id?string | null
Id of the workspace to act on (must be a member).
lead_idsarray<string>
Items
1 <= items <= 1000Response Body
curl -X POST "http://localhost:8000/api/v1/lists/497f6eca-6276-4993-bfeb-53cbbbba6f08/members" \ -H "X-Workspace-Id: string" \ -H "Content-Type: application/json" \ -d '{ "lead_ids": [ "497f6eca-6276-4993-bfeb-53cbbbba6f08" ] }'{
"added": 0,
"removed": 0,
"member_count": 0
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}