Revoke asset
Revoke one asset's proofs. Revoking withdraws PROOFS, not the identifier: a phone or email row stays active (signing in with it again issues a new proof). Revoking one asset of a phone or email revokes every asset of that identifier. Revoking a DOMAIN asset runs the whole-domain cascade: every proof of the domain and every delegation issued from it are revoked, and the domain is demoted to reverification_required with its DNS challenge rotated. Cannot be undone. Owner only: an API key answers 403 owner_session_required for every asset type (revoke the proof itself with POST /proofs/{id}/revoke instead). A session needs a single-use revocation_bulk step-up grant bound to exactly the ids it sends (403 2fa_required; reason: target_mismatch when the grant names other ids). A notice goes to the owner. An already-revoked asset answers 200 with nothing revoked and spends no grant.
Request
- Base URL: https://api.proof.holdings
- URL: https://api.proof.holdings/api/v1/me/assets/{id}
- Auth: one of:
- HTTP bearer
- API key in cookie auth_token
Path parameters
MongoDB ObjectId
Response
Revoked (or already revoked — outcome says which)
Example response
{
"asset_id": "507f1f77bcf86cd799439011",
"identifier": "+1555***1001",
"delegations_revoked": [
{
"proof_id": "ph_dlg_0123456789abcdef0123456789abcdef",
"delegate": "pkg:npm/@acme/cli",
"delegate_type": "purl",
"principal": "example.com"
}
],
"notice": [
{
"kind": "email",
"address": "o***@example.com",
"outcome": "sent"
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.