AttributeQuery

POST /v1/attributes/query.

Every filter is optional and absent means "no constraint". Filters compose with AND; the values inside tags compose with OR (any of). The base set is nodes carrying at least one attribute - a bare paragraph is never a row of an attribute query, even under missing.

Type object

Shape

Field	Type	Description
workspaces	array of WorkspaceId	Which workspaces to search. Empty means every workspace this store holds. Default `[]`
has	string or null	Only nodes carrying this attribute key (`koru.due`, or a custom definition's key). Default `null`
missing	string or null	Only nodes not carrying this key. Combined with the base rule this reads "has some attribute, but not this one". Default `null`
tags	array of string	Only nodes carrying any of these tags, each a `TagId` in storage form. Ids, never names - the tag table owns names and rename must not change what a saved query matches. Default `[]`
priority	string or null	Only nodes whose `koru.priority` equals this token (`low \| medium \| high \| urgent`). Default `null`
min_priority	string or null	Only nodes whose `koru.priority` is this token or more important - the semantic order `low < medium < high < urgent`, never the alphabetic one. Default `null`
due	DueFilter or null	Which `koru.due` values match, stated per temporal type. Default `null`
sort	string or null	`due`, `priority` or `modified`. Absent means `modified` - newest first, which is what a surface with no opinion wants. Default `null`
group_by	string or null	Ask for corpus-wide counts beside the page. `tag` is the only token; absent means no groups, and the response's `groups` is empty. It is a separate question from paging, deliberately: a client can count a page itself, and what it cannot do is count the rows it did not fetch. So the counts come from their own statement over the same filter, and a group's count is the whole matching corpus rather than the page above it. Default `null`
limit	integer (uint, >= 0) or null	Rows per page. Absent means the server default; the server also caps it, so a huge number is a full page rather than a full table. Default `null`
offset	integer (uint, >= 0) or null	Rows to skip. Page by increasing this until a short page comes back. Default `null`

Example

{
  "workspaces": [],
  "has": "string",
  "missing": "string",
  "tags": [],
  "priority": "string",
  "min_priority": "string",
  "due": {
    "dates": {
      "after": "string",
      "before": "string"
    },
    "instants": {
      "after_ms": 0,
      "before_ms": 0
    }
  },
  "sort": "string",
  "group_by": "string",
  "limit": 0,
  "offset": 0
}

The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.

Used by

POST/v1/attributes/query
Which nodes carry these attributes, across workspaces, from the read model

Generated from contract version 1. Last updated November 12, 2026.