List saved searches
const url = 'https://example.com/api/v1/search/saved';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/search/saved \ --header 'Authorization: Bearer <token>'Lists the saved searches. It requires a signed-in User with the data scope. It can return 401 if the session is missing or expired and 403 if access is denied. Route: /api/v1/search/saved. Inputs: . Safe reads can use bounded retries.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The caller’s saved searches
A saved search: a named query that works like a smart folder (DESIGN §32
S10). It is user data, stored as one JSON file per search in
<home>/.calternal/saved-searches/<id>.json.
object
Creation time (RFC 3339, UTC).
Stable identifier (a lowercase UUID). Links use it, so a rename never breaks them.
Display name chosen by the user.
True when the search shows in the sidebar.
The raw query, operators included, exactly as the search field shows it.
Last change time (RFC 3339, UTC).
Examplegenerated
[ { "created": "example", "id": "example", "name": "example", "pinned": true, "query": "example", "updated": "example" }]Authentication is required
The standard API error response: { "error": { ... } }.
object
Example
{ "error": { "code": "bad_request" }}