List field definitions (the metadata schema)
GET /fields
Returns field definitions, ordered by display group and display order. The result is the schema admins build through the field-management UI.
By default, archived (soft-deleted) fields are excluded — the
list is the live schema. Pass an explicit status to filter to
exactly one status; status=archived surfaces the tombstones
for anyone who needs them.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”When set, only fields whose applies_to is empty (=all)
or contains this asset_type ref are returned. Used by
the asset edit form to figure out which fields to show.
Implies subject_kind=asset — collection fields aren’t
applies_to-scoped.
Filter by subject kind. asset returns only asset-side
definitions (default behaviour for callers that don’t
specify); collection returns only collection-side
definitions. Omit to return both kinds.
Responses
Section titled “ Responses ”List of field definitions
object
Federation-stable slug. Globally unique.
What the field describes. asset definitions apply to
individual assets; collection definitions apply to whole
collections. One row is one or the other — operators who
want a field on both kinds create two rows.
Type-dependent constraints / values. Shape per ADR 0012.
object
Resource type refs this field applies to. Empty = all. Ignored when subject_kind = ‘collection’.
Auto-extraction source, e.g. {“type”:“exif”,“tag”:“DateTimeOriginal”}.
object
CanonicalField the metadata-extraction pipeline writes into this field. Empty = no extraction (the field stays operator-managed). Edited via the dedicated PUT …/extraction endpoint.
Write behaviour when extraction has a value. Empty = default (skip_if_set).
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Unexpected server error
object
Human-readable error summary
Example
the request could not be completed