HTTP guides
Entries and versions
Read complete records and perform signed lifecycle mutations.
Public routes resolve current entries, enumerate versions, and retrieve historical records. Mutation routes create, update, and revoke entries; each has an exact generated contract.
Reads
URL-encode the full DID and version separately. Do not concatenate raw user input into paths.
Mutations
Create, update, and revoke require their respective scoped capability and idempotency key. Create/update also require a valid publisher signature; see publishing. Revocation does not erase immutable history.
Source authority
This page describes the checked-in implementation, not the availability of a public registry.
mars-server/src/api/mod.rsmars-server/src/contracts.rsdocs/api/openapi.v1.json