Get one deed's exact bytes
const url = 'http://127.0.0.1:8080/v1/deeds/example';const options = { method: 'GET', headers: {'Deedglass-Version': '2026-10-01', Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url http://127.0.0.1:8080/v1/deeds/example \ --header 'Authorization: Bearer <token>' \ --header 'Deedglass-Version: 2026-10-01'The stored canonical JSON of the deed envelope, byte for byte, so its hash and seal check offline. Deeds never change: the response is cacheable forever and its ETag is the body_hash. With Accept: application/cose the deed comes as a COSE_Sign1 signed statement (RFC 9052; not an RFC 9942 transparency-service object). Requires deeds:read.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The deed id (deed_…).
Header Parameters
Section titled “Header Parameters”The API version (YYYY-MM-DD). Leave it out to use your org’s pinned version (public routes use the latest). An unknown version is 400 api_version_invalid.
The ETag of a copy you hold.
Responses
Section titled “Responses”The deed.
A sealed deed (docs/DEED_SPEC.md). The stored and exported form is the RFC 8785 canonical JSON of this object. seal is Ed25519 over the bytes “deedglass/deed/v1\n” + body_hash.
object
Equal to body.deed_id (not signed; verifiers check it).
Deed v1. Every key is always present; which sections are null depends on kind (docs/DEED_SPEC.md §5). Digests only, never payloads.
object
“sha256:” + lowercase hex of SHA-256.
RFC 3339, UTC, exactly three fractional digits.
object
object
“sha256:” + lowercase hex of SHA-256.
object
object
object
RFC 3339, UTC, exactly three fractional digits.
RFC 3339, UTC, exactly three fractional digits.
object
object
object
object
object
“sha256:” + lowercase hex of SHA-256.
Example
{ "object": "deed", "body": { "v": 1, "kind": "action", "action": { "mode": "gateway" }, "policy": { "mode": "enforce", "decision": "allow" }, "approval": { "outcome": "approved" }, "execution": { "status": "succeeded" }, "witness": { "level": "L0", "verdict": "VERIFIED" } }}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
"sha256:<hex>": the deed’s body_hash.
The copy named in If-None-Match is current.
default
Section titled “default”An error. Every error has this envelope; doc_url explains the code.
object
object
One or more calm sentences with the next step.
The request field, query parameter or header the error is about.
On policy_invalid only. Each problem with its line, code and hint.
One finding about a policy file, with its position and the next step. Codes are stable and listed in docs/POLICY_ERRORS.md. In the policy_invalid error envelope each diagnostic also carries object: policy_diagnostic. The full PolicyDiagnostic schema is in openapi.yaml.
object
One agent action. Its sections mirror the deed’s. status is the one field an agent needs; state is the exact lifecycle state (docs/GATE.md). The Gate’s own responses (POST /v1/actions and its result report) add execution.result and witness.reasons; lists leave both out. The full Action schema is in openapi.yaml.
object
On undo_unavailable only. Every check of the undo, each with its fix. Additive (S23).
One of the twelve safety checks (S23 §3.3). Available means no check failed. The full UndoCheck schema is in openapi.yaml.
object
Example
{ "error": { "type": "invalid_request_error", "code": "not_found", "message": "There's no endpoint at GET /v1/helth. Did you mean /v1/health?", "param": null, "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d", "doc_url": "https://docs.deedglass.com/errors/not_found" }}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
The API version this response follows.