Lead lists, or account lists with type=ACCOUNT. Needs a seat.
Your API key from the console (gw_live_…).
In: header
Query Parameters
The LinkedIn account (lg_…) to act as.
1 <= lengthLEAD for lead lists (the default), ACCOUNT for account (company) lists. Another value is 400.
"LEAD"Value in
- "LEAD"
- "ACCOUNT"
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/v1/linkedin/lists?account_id=lg_3f9c2a7b1d&type=ACCOUNT"{ "object": "LinkedinSalesListList", "items": [ { "object": "LinkedinSalesList", "id": "7012345678901234567", "name": "Q4 prospects", "list_type": "LEAD", "description": null, "total_count": 84, "shared": false, "created_at": "2026-10-01T09:00:00.000Z", "updated_at": "2026-10-31T09:30:00.000Z" } ]}Raw LinkedIn request POST
A raw LinkedIn passthrough: a `GET` of any linkedin.com path (Sales Navigator `/sales-api/` paths on the seat's session) answers LinkedIn's JSON as is (`{ data }` for text); a write is allowed only for follow (`followingStates` of a profile, counted as `follow`). Anything else is 422.
Save a Sales Navigator lead POST
An action on a member: Sales Navigator's `saveLead`, a write (`save` daily cap), on the account's seat. `user_id` is the lead's Sales Navigator id (`ACw…`) or its `urn:li:fs_salesProfile:(…)` from a Sales Navigator search; `list_id` (from `GET /linkedin/lists`) also adds it to that list. Recruiter's pipeline actions answer 422: no account here has a Recruiter seat.