Supersede Attestation
Attestations
Supersede Attestation
Creates a new attestation that supersedes an existing one. The original attestation is marked as SUPERSEDED.
POST
Supersede Attestation
Creates a new attestation that supersedes an existing one. The original attestation is marked as
SUPERSEDED with a reference to the new version. The new attestation is signed with the specified key, recorded in the transparency log, and returned alongside the updated original. Both attestations remain verifiable, creating an auditable chain of credential versions. Only VALID attestations can be superseded — REVOKED or already SUPERSEDED attestations return a 409 Conflict.
How it works
1
Call supersede with original attestation ID
Provide the UUID of the attestation to supersede as a path parameter, along with the new payload and signing key.
2
Original attestation marked SUPERSEDED
The original attestation’s status changes to
SUPERSEDED with a timestamp and a reference to the new attestation ID.3
New attestation created with VALID status
A new attestation is minted with the updated payload, signed with the specified key, and recorded in the transparency log.
4
Both returned in response
The response includes both the old (superseded) and new (valid) attestation objects under
old and new keys.Parameters
uuid
required
The UUID of the original attestation to supersede. Must be in
VALID status.string
required
Base64url-encoded payload for the new attestation. This replaces the content of the original. For JSON claims, base64url-encode the JSON string. For documents, base64url-encode the file bytes.
string
required
Key identifier for the signing key to use for the new attestation. Can be the same key as the original or a different one (for example, after key rotation).
string
required
Cryptographic algorithm for signing the new attestation. Must match the key type of the specified
kid.string
required
Ensures safe retries in case of network failures. Reusing the same key with the same parameters returns the original response without creating a duplicate.
Common use cases
Responses
Supersede operations are idempotent when using the same
Idempotency-Key. Retrying a failed request with the same key is safe and will not create duplicate attestations.Authorizations
API key for machine-to-machine authentication
Path Parameters
Body
application/json
Updated payload for the new attestation

