Get Lead
Leads
Get Lead
Page through person and company Leads for the authenticated workspace.
GET
Get Lead
CLI:
Overview
Returns Leads for the effective user. Passid to fetch one Lead. Otherwise, use type, limit, and cursor to page through workspace Leads by person or company.
Use q for broad saved-Lead filtering across name, role/title, company, domain, industry, location, and work email fields. Use the narrower filters when you already know the field: name, title, role, company, domain, email, industry, or location.
Use this endpoint when you need Leads across the whole workspace. Lists group these same Leads; they do not own separate copies of Lead data.
AI agent notes
Use this endpoint when you need Lead records independent of any single List. If you are rendering a List screen, prefer the List view or List Leads endpoints because they include membership and view-field context.The response is paginated. Keep the returned cursor and stop when no next cursor is present.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Available options:
person, company Required range:
1 <= x <= 500Broad text filter across saved Lead name, role/title, company, domain, industry, location, and work email fields.
Required string length:
1 - 200Filter saved Leads by person or company name.
Required string length:
1 - 200Filter saved person Leads by title.
Required string length:
1 - 200Alias for title; filter saved person Leads by role.
Required string length:
1 - 200Filter saved Leads by company name.
Required string length:
1 - 200Filter saved Leads by company or Lead domain.
Required string length:
1 - 200Filter saved Leads by work email.
Required string length:
1 - 200Filter saved company Leads by industry.
Required string length:
1 - 200Filter saved Leads by city, state, country, or raw location.
Required string length:
1 - 200