Run a people search

Run a people search. The filter source is exactly one of: literal filters, a stored PEOPLE saved search (savedSearchId or savedSearchName), or a natural-language query (the product's smart search converts the prose into filters; criteria it could not map come back as unresolvedCriteria). Sending two sources is a 422. A saved search resolves to its filters and echoes ignoredFilterKeys for stored keys with no search field; a company saved search answers 422 SAVED_SEARCH_TYPE_MISMATCH.

The response always echoes the RESOLVED filters — reuse them verbatim to page, refine, or POST /prospects/search/save-to-list — plus the true match total and a scrollToken for the next page (send it back with the same filter source; it is null when there is no continuation).

Rows are the provider's person record in snake_case, so the fields present vary by person, plus Fuse's own keys: pdlId (the provider's person id; absent on the rare row the profile cache could not store), _id (our stable id for the cached person record, present unless that row could not be cached), savedProfile / savedBy (whether this person is already a contact of yours), and linkedinConnectedAccountIds / linkedinInvitationSentAccountIds (which of your connected LinkedIn accounts already reached them). Rows carry no email address or phone number — searching is discovery only. Contact details you have already enriched for some of these people are stripped too, so a row never depends on your enrichment history; use /prospects/search/save-to-list with enrich to obtain contact details.

Billing: 2 credits per requested profile are pre-checked and 2 credits per profile returned are debited. (Enforced by the public row transformer, which removes Fuse's enrichment overlay and the provider's own work_email, personal_emails, recommended_personal_email, mobile_phone and phone_numbers before the row is returned.)

Errors:

• 402 INSUFFICIENT_CREDITS — The balance does not cover the pre-check for this request; nothing was billed.
• 404 SAVED_SEARCH_NOT_FOUND — No saved search of yours has that id or exact title.
• 409 SAVED_SEARCH_NAME_AMBIGUOUS — Two of your saved searches share that title — reference it by savedSearchId instead.
• 422 VALIDATION_FAILED — The request failed the declared schema; param names the offending key and message quotes the rule it broke.
• 422 SAVED_SEARCH_TYPE_MISMATCH — The saved search exists but stores the other kind of filters; param is savedSearchId.
• 422 SAVED_SEARCH_INVALID — The STORED filters no longer form a runnable search — every value was retired, or the blob translates to nothing.
• 422 QUERY_FILTERS_INVALID — The natural-language query produced no usable filter; name concrete criteria.
• 422 SEARCH_FILTERS_INVALID — The provider rejected the assembled query as malformed — a filter value is the wrong shape for its field.
• 429 RATE_LIMITED — Per-token rate limit for this bucket exhausted; retry after the window in the RateLimit-Reset header.
• 500 UNEXPECTED_ERROR — The request failed inside the service; nothing was billed and the request_id identifies the failure.

Requires one of the following token scopes: search.