Skip to main content
POST
Specify the category using the type parameter to filter and view ingested knowledge or user memories within a database or collection:
  • type=knowledge (default) - knowledge sources (documents, app sources).
  • type=memory - user memories.
Supports pagination, metadata filters, and field projection. For metadata design and query-time behavior, see Scoping using metadata.

Request body

1. Filters

  • filters is a structured object with three optional categories. Filters are exact-match constraints i.e. filtered values are matched against stored values as exact values. There are no range, contains, or OR operators on this endpoint; run multiple calls and merge client-side for OR behavior.
  • AND/OR: All filter pairs combine with a logical AND. To express OR semantics, run multiple calls and union them client-side.
  • ids + filters: When ids is non-empty, only those IDs are considered, but other filters still apply on top - useful for “show me items 1, 2, 3 that also belong to department=legal”.

2. Including Fields for convenient data objects

When you don’t need every field on every row, pass include_fields to keep response payloads small. Only the listed fields are populated; omitted fields should be treated as unavailable in that response. id, database, and collection are always returned. Allowed values are title, type, description, note, timestamp, metadata, additional_metadata, and relations. Omit or pass null to return everything.
Projectable vs. fetchable fields. content, url, and attachments are not valid include_fields values - they are stripped from list responses, and requesting one returns 400. Fetch them per-source via Inspect Context.
include_fields only applies to type=knowledge. It is ignored for type=memory.
When type=memory, data is a ListUserMemoriesResponse instead - same idea but with a data.user_memories[] array of memory items.
Use the canonical v2 names. Prefer filters.metadata and filters.additional_metadata. Legacy filters.tenant_metadata and filters.document_metadata are accepted for back-compat, with canonical keys winning on conflicts.
Related Resources

Authorizations

Authorization
string
header
required

API key sent as a Bearer token: "Bearer prefix.secret"

Body

application/json

List request

collection
string

Collection scope. Defaults to the default collection when omitted. Formerly sub_tenant_id; the sub_tenant_id alias is still accepted (deprecated).

Example:

"team_docs"

database
string

Database/Collection are the canonical v2 names; TenantID/SubTenantID are their deprecated aliases (reconciled here in UnmarshalJSON and centrally by the TenantAliases middleware).

Example:

"acme_corp"

filters
object
Example:
ids
string[]

When provided, only items with these IDs are returned. Pagination and filters still apply.

Example:
include_fields
string[]

Field projection — only the listed fields plus id, database, collection are returned. Only applies to type=knowledge.

Example:
page
integer

Current page number (1-indexed).

Example:

1

page_size
integer

Number of items per page.

Example:

50

sub_tenant_id
string
deprecated

deprecated: use collection

Example:

"sub_tenant_4567"

tenant_id
string
deprecated

deprecated: use database

Example:

"tenant_1234"

type
enum<string>

Bucket to list: knowledge (default) or memory.

Available options:
knowledge,
memory
Example:

"knowledge"

Response

OK

data
object
Example:
error
object

Error message, empty string on success.

Example:
meta
object
Example:
success
boolean

Whether the request succeeded.

Example:

true