Schemas

Get a field's curation history

The concept's curation trail, newest first — what a consumer replays to keep a cached vocabulary correct: maturity moves (tier_changed), merges in either direction (merge_log_absorbed, merge_log_merged_into, absorbed), cleanup actions applied to it (renamed, rewritten, split, deleted), the current redirect (superseded) and the names that now fold onto it (alias_added). The same changes are announced live on GET /v1/events as field.* signals. Never follows redirects — the trail belongs to the id asked for.

get/v1/fields/{id}/history

Request

  • Base URL: https://api.talonic.com
  • URL: https://api.talonic.com/v1/fields/{id}/history
  • Auth: HTTP bearer

Path parameters

idstring uuid required
Example:a1b2c3d4-e5f6-7890-abcd-ef1234567890

Resource UUID.

Query parameters

limitinteger

Response

Curation events, newest first.

field_idstring uuid required
canonical_namestring required
maturity'core' | 'proven' | 'candidate' required

Named maturity level — the contract a consumer caching the vocabulary can rely on (tier is the frozen numeric twin: core = 1, proven = 2, candidate = 3).

  • core: universal, fully trusted; safe to bind schemas, dashboards and downstream models to. Demotion is hysteresis-guarded and always emits field.demoted.
  • proven: recurring and useful; stable id, name may still be groomed (field.renamed / field.merged announce it).
  • candidate: newly discovered; may be merged, renamed or expire with no notice beyond the event feed. Do not hard-code.
totalinteger required

Changes

No recorded changes to this operation across all 1 revision of this API.