Update Saved Search
Rename a saved search or switch its alert.
PATCH
https://api.foxreach.io/ api/ v1/ lead-finder/ saved-searches/{saved_search_id}Requires an API key with the write scope.
Path Parameters#
saved_search_idstringpathrequiredThe saved search id.
Body Parameters#
namestringbodyNew name, 1 to 200 characters.
alertEnabledbooleanbodySwitch the new-results alert on or off.
Response#
dataobjectShow data
idstringSaved search identifier.
namestringName.
kindstringpeople or companies.filtersobjectThe stored filter object.
lastRunAtstringISO 8601 timestamp of the last run, or
null.lastTotalintegerResult count from the last run, or
null.alertEnabledbooleanWhether alerts are on for this search.
createdAtstringISO 8601 timestamp.
Errors#
| Status | Description |
|---|---|
401 | Missing, invalid, revoked or expired API key |
403 | API key does not have the required scope: write |
404 | Lead Finder is not enabled while Lead Finder is switched off on this environment |
503 | Lead Finder is not configured when it is enabled but has no data provider key |
404 | Saved search not found: it does not exist in this workspace |
Rate Limit#
- 120 requests per minute, shared by every
writecall in your workspace. Fixed 60-second window. - Every response includes
X-RateLimit-Limit,X-RateLimit-Remaining,X-RateLimit-Reset(unix epoch seconds) andX-RateLimit-Bucket(write). - A
429response includes aRetry-Afterheader (seconds until the bucket resets).
For client-side patterns, see Rate Limiting.
Was this page helpful?
View as MarkdownLast updated November 4, 2026