Instantly · Outreach

API Explorer / List leads

This endpoint is a POST endpoint, instead of GET - a deviation from the REST APIs standards we’re following because of the complex arguments it accepts, which would be too hard to express through query parameters. Results are ordered by each lead's id field in ascending order (or by contact when distinctcontacts is true) so clients can paginate chronologically by reusing the cursor returned in nextstarting_after. Leads created on or after October 15, 2025 respect this chronological ordering; older records may appear out of sequence when sorted by ID. Requires one of the following scopes: leads:read, leads:all, all:read, all:all Every field is optional; an empty body lists all leads visible to the workspace.

Private Gateway connection

Data below comes from the configured private Gateway. Provider activation remains governed by its evidence and policy gates.

unverifiedRequest shape unavailableUnverified

Published API evidence

Public metadata only. Response bodies, credentials, and internal review notes are never displayed.

No verification date is claimed. No response capture is claimed.

Request parameters

campaign body · optional
Campaign ID to filter leads. Example: "01a0abd0-8b15-7c60-831e-17bdca89a00f"
contacts body · optional
Array of emails the leads needs to have
distinct_contacts body · optional
Whether to return distinct contacts. Example: true
enrichment_status body · optional
Enrichment status to filter leads. Example: 1
esg_code body · optional
ESG code to filter leads. Example: "1"
excluded_ids body · optional
Array of lead IDs to exclude
filter body · optional
Filter criteria for leads. For custom lead labels, use the `interest_status` field. Example: "FILTER_VAL_CONTACTED"
ids body · optional
Array of lead IDs to include
in_campaign body · optional
Whether the lead is in a campaign. Example: true
in_list body · optional
Whether the lead is in a list. Example: true
is_website_visitor body · optional
Whether the lead is a website visitor. Example: true
limit body · optional
The number of items to return. Example: 10
list_id body · optional
List ID to filter leads. Example: "01a0abd0-8b15-7c60-831e-17bee86815d1"
organization_user_ids body · optional
Array of organization user IDs to filter leads
queries body · optional
search body · optional
Search term matched against the lead's email and profile fields (first and last name, company, job title, and similar). Matches whole words, and the beginning of a field's value — "smith" finds "John Smith", "mith" does not. Provide `campaign` or `list_id` to also match inside values. Newly created or updated leads can take a few seconds to become searchable. Example: "John Doe"
smart_view_id body · optional
Smart view ID to filter leads. Example: "01a0abd0-9ab5-7c0d-b00a-f00ce0da6beb"
starting_after body · optional
Forward pagination cursor. When distinct_contacts is false, provide the `id` value from the last lead of the previous page; when true, provide the lead's email. Example: "01a0abd0-9ab5-7c0d-b00a-f00a1adddcc4"

Provider docs How to run it