Leads
Get Lead
API key access
Needs the
leads:read scope with an API key (ro_pat_...). A signed-in session uses the caller's role.GET
/api/v1/leads/{lead_id}AuthorizationBearer <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
lead_idstring
Format
uuidHeader Parameters
X-Workspace-Id?string | null
Id of the workspace to act on (must be a member).
Response Body
curl -X GET "http://localhost:8000/api/v1/leads/497f6eca-6276-4993-bfeb-53cbbbba6f08" \ -H "X-Workspace-Id: string"{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"workspace_id": "0967198e-ec7b-4c6b-b4d3-f71244cadbe9",
"first_name": "string",
"last_name": "string",
"title": "string",
"email": "string",
"phone": "string",
"phone_type": "mobile",
"linkedin_url": "string",
"timezone": "string",
"language": "string",
"status": "new",
"source": "string",
"custom_fields": {
"property1": null,
"property2": null
},
"company_id": "b2e6a1c3-1a5e-44ae-a8fd-81f76fd715cf",
"company": {},
"owner_id": "8826ee2e-7933-4665-aef2-2393f84a0d05",
"created_at": "2019-08-24T14:15:22Z",
"updated_at": "2019-08-24T14:15:22Z"
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}