Create a saved search

Store a search under a name. type picks the kind — people (the default) or company — and decides which language filters must speak: people filters are the keys POST /prospects/search takes, company filters the keys POST /companies/search takes. Either way the search opens identically in the product UI, and the created row comes back with its filters in that same search vocabulary, ready to re-send.

Exactly two of the 46 people filter fields cannot round-trip through the product's filter rail — first_name and last_name — and are rejected with 422 SAVED_SEARCH_FILTERS_UNSUPPORTED naming the field, rather than stored in a form the app cannot reopen. Every other field stores, work_email, mobile_phone, personal_emails, linkedin_url, github_url and facebook_url included. type is immutable: PATCH can change the title and the filters, never the kind. Titles need not be unique, but a title shared by two searches can no longer be used as savedSearchName.

Errors:

• 422 VALIDATION_FAILED — The request failed the declared schema; param names the offending key and message quotes the rule it broke.
• 422 SAVED_SEARCH_FILTERS_UNSUPPORTED — filters names first_name or last_name — the only two people filter fields with no saved-search equivalent; param names the 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.