Skip to main content
PATCH
Update Saved Search
Send at least one of name and filters. filters replace the saved ones entirely — they are not merged. mode is only read together with filters and defaults to the current mode of the saved search.
The filters and the name are applied as two separate writes. If the rename is refused because the name is already taken (409), the new filters are already saved.

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Path Parameters

savedSearchId
string
required

Id of the saved search

Minimum string length: 1

Body

application/json
name
string

Display name, 1 to 200 characters after trimming. Unique within your team.

Required string length: 1 - 200
Example:

"Lyon SaaS founders"

filters
object[]

New filters, replacing the saved ones entirely. 1 to 10 filters of shape { filterId, in?, out?, exactMatch? } (no other key: an unknown key such as type answers API_INVALID_FILTERS), at most 1000 values per in / out and 1000 characters per value.

Required array length: 1 - 10 elements
mode
enum<string>

Search mode of the new filters. Only read with filters; defaults to the current mode of the saved search.

Available options:
leads,
companies
Example:

"leads"

Response

Saved search updated, in its new state

data
object

A People Database saved search: a named set of People Database filters saved by your team. It appears in the "Saved searches" menu of the People Database.