Skip to main content

Saved Filters

List saved filter presets: named combinations of filter conditions, search terms, and sort settings your team reuses across the API and dashboard.

Saved filters are named, reusable filter configurations: a stored combination of conditions, free-text search, and sort settings for the document filter. The GET /v1/search/saved-filters endpoint lists the presets saved in your organization so integrations can reapply the same filter logic your team uses in the Talonic dashboard.

The public API is read-only for saved filters. Create, edit, and delete presets in the Talonic dashboard; then load them here and pass the stored conditions to POST /v1/documents/filter.
GET/v1/search/saved-filters

Query parameters

source_idstringFilter saved filters by source connection.

Request

Response (List)

Response fields

dataarrayArray of saved filter objects, most recently updated first.
data[].idstringSaved filter UUID.
data[].namestringDisplay name for the saved filter.
data[].conditionsarraySaved filter conditions array.
data[].searchstring | nullSaved free-text search string.
data[].sortobject | nullSaved sort configuration.
data[].source_connection_idstring | nullSource scope if set.
data[].created_atstringISO 8601 creation timestamp.
data[].updated_atstringISO 8601 last update timestamp.

Response (GET /v1/search/saved-filters)

{
  "data": [
    {
      "id": "sf_a1b2c3d4",
      "name": "Acme invoices 2024",
      "conditions": [
        { "fieldId": "fld_a1b2c3d4", "operator": "eq", "value": "Acme Corp" }
      ],
      "search": null,
      "sort": { "fieldId": "fld_e5f6g7h8", "direction": "desc" },
      "source_connection_id": null,
      "created_at": "2024-10-01T09:00:00Z",
      "updated_at": "2024-10-01T09:00:00Z"
    }
  ]
}

Errors

Error responses

401unauthorizedMissing or invalid API key.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.

Saved filters work as reusable presets for POST /v1/documents/filter. Your team stores a complex combination of conditions, search text, and sort order once in the dashboard; your integration then lists the presets, picks one by name or ID, and passes its conditions, search, and sort directly to the filter endpoint. All saved filters are organization-wide, so every team member and API key sees the same list.