List prospects
Returns prospects in your workspace, newest first, with cursor pagination. Pass listId to return only the prospects in one list — the way to pull everyone in a list from your own server or script. Get list ids from GET /lists. Pass field and fieldValue to keep only the prospects whose job title, company, country, city or one of your own CSV columns contains a value — the same "Filter by field" as the Prospects page.
Required scope: prospects:read.
Returns a cursor-paginated list — pass cursor from the previous page to continue.
To export a whole list, keep requesting with cursor set to the previous next_cursor until has_more is false.
listId and filter combine: listId narrows to the list, then each filter must also match.
field + fieldValue combines with listId and filter, and is applied before paging, so it never shortens a page. Example: listId=<your list>&field=custom:language&fieldValue=German returns everyone in that list whose Language column contains German.
Every page holds limit rows unless it is the last one. The one exception: with a very selective filter, if 20,000 prospects are checked before the page fills, the page comes back with fewer rows (possibly none) and has_more true. Pass next_cursor back to continue.
Request
- Base URL: https://warmysender.com/api/v1
- URL: https://warmysender.com/api/v1/prospects
- Auth: HTTP bearer
Query parameters
Results per page (1–100).
next_cursor from the previous page.
Only return prospects in this list (a list id from GET /lists). Pass unassigned to return only the prospects that are not in any list. Leave it out to return every prospect.
Keep only prospects whose field contains fieldValue (not case-sensitive). One of: role (job title), company, country, city, or custom:<name> for one of your own fields — a CSV column named Language is stored as custom:language. Requires fieldValue.
Text to look for in field, e.g. German or Head of Sales (up to 200 characters). Requires field.
contains (default) or not_contains. not_contains leaves out the prospects whose field contains fieldValue — for example field=role&fieldValue=assistant&fieldMatch=not_contains keeps everyone whose job title does not contain "assistant". Prospects with that field empty are kept.
Repeatable metadata filter, formatted field:op:value (e.g. company:eq:Acme, custom:region:eq:US, email:exists). Fields: email, firstName, lastName, company, role, country, city, industry, globalStatus, tags, or custom:<key>. Ops: eq, neq, contains, exists. Unknown/invalid filters are ignored and echoed back in filters_ignored.
Response
Success
Changes
No recorded changes to this operation across all 1 revision of this API.