Get one exclusion operation's audit trail
Returns ONE exclusion operation’s append-only transition trail, oldest first.
The trail is keyed by the operation’s own request_ref rather than by contract number, because the trail belongs to the OPERATION: a contract excluded more than once has more than one trail, and keying by contract would need a resolution step free to answer with the wrong one.
The tenant is derived from the validated identity: an operation that does not exist and an operation belonging to another tenant are the SAME answer, 404, so this read cannot be used to probe another tenant’s book.
evidence is handed back as the JSON document the writer stored, byte for byte, and its shape varies by event_type. It is deliberately not re-encoded: a trail exists to hold proof, and a server that rewrites proof cannot settle the argument the trail was kept for.
The trail is not paginated. It is capped at 200 entries and the cut is STATED through truncated rather than swallowed, because a silent cut reads as a complete history. A quarantined operation’s trail is served like any other: it is exactly the evidence an operator has about a row nothing will converge.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
The exclusion operation's own reference, exactly as the list returned it.
1 - 128^[A-Za-z0-9._-]{1,128}$
