Skip to content

Authority API

Authority records consolidate per-DLU surface-form / canonical entities into corpus-wide identifiers. Once an authority record exists, every DLU that agrees on entity_id is asserting the same real-world person, place, or group. Today most DLU rows carry entity_id: null; this surface is how curators promote canonical mentions into authority records.

MethodPathSummaryKey paramsResponse
GET/authority/{kind}List authority recordskind (path:string)(no body)
POST/authority/{kind}Create authority recordkind (path:string)
body: CreateAuthorityBody
(no body)
GET/authority/{kind}/searchSearch authority recordskind (path:string)
q (query:string)
(no body)
DELETE/authority/{kind}/{id}Delete authority recordkind (path:string)
id (path:integer)
(no body)
GET/authority/{kind}/{id}Get authority recordkind (path:string)
id (path:integer)
(no body)
PATCH/authority/{kind}/{id}Update authority recordkind (path:string)
id (path:integer)
body: JSON
(no body)
GET/authority/{kind}/{id}/mentionsList mentions of an authority recordkind (path:string)
id (path:integer)
(no body)

Search persons authority by name fragment

Terminal window
curl -H "X-API-Key: $API_KEY" \
"$ARCHAIC/authority/person/search?q=romay"

The no-anchor-no-entry rule applies to every write that asserts an entity, event, or relationship: each row must carry at least one (page, line) mention with a confidence score, or the engine drops it at write time. Bulk endpoints surface dropped rows in their per-id response so callers can inspect.