List Authorisations

Return every ยง9 step 3 authorisation grant against the record's versions, newest first. One row per version.authorization_granted audit event. The list isn't paginated โ€” authorisations are bounded (at most one per (version, text_version) pair).

Path params

ParamDescription
recordIdDDS record id

Why 404 instead of empty list

The handler runs a parent-record visibility check first. If the record isn't visible to the caller (cross-org or missing), the response is 404 rather than 200 + [], so clients can distinguish "no authorisations" from "no permission".

Response shape

Each row uses the same attributes shape as the POST endpoint โ€” see Create Authorisation. Ordering is by granted_at DESC so the most recent acknowledgement (for the current version) appears first.

Use cases:

  • Inspector view: "show me every authorisation on this record".
  • UI: highlight the current-version authorisation by filtering to the row whose version_id matches the record's current_version.id.

Errors

StatusCodeWhen
401UNAUTHORIZEDMissing/invalid API key
404NOT_FOUNDRecord isn't visible to the caller

Required scope: ingestions:read