---
title: "Delete domain verification"
method: DELETE
path: "/api/v1/verifications/domain/{id}"
tags: ["Verifications"]
---

# Delete domain verification

`DELETE /api/v1/verifications/domain/{id}`

## Request

- Base URL: `https://api.proof.holdings`
- URL: `https://api.proof.holdings/api/v1/verifications/domain/{id}`
- Auth: HTTP bearer

Remove a domain verification this account started that has not been verified. A verified domain is refused with `409 domain_verified`: deleting it would revoke its control proof and every delegation issued from it, so that stays a signed-in act — on the Domains page of the dashboard, or with the MCP `delete_domain` tool under a login session. A domain in `reverification_required` (its proofs were revoked; it stays on the account until the owner removes it) and one mid-cascade (`revoking`) are refused the same way.

## Path parameters

- `id` string, required: MongoDB ObjectId

## Response `204`

Domain verification deleted

## Other responses

- `400`: `validation_error` — the id is not a well-formed id
- `401`: Missing or invalid API key
- `403`: `account_key_required` — this API key is bound to one sub-account; account-level changes need an account-wide key or the dashboard. API key lacks the `verifications:write` scope
- `404`: `domain_not_found` — no such domain on this account
- `409`: `domain_verified` — the domain is `verified`, `reverification_required` or `revoking`; remove it signed in as the owner instead (dashboard Domains page, or MCP `delete_domain` under `start_login`)

---

[API](https://skmtc.dev/proof/apis/proof-holdings-api.md) · [All operations](https://skmtc.dev/proof/apis/proof-holdings-api/llms.txt) · [OpenAPI document](https://skmtc.dev/proof/apis/proof-holdings-api/revisions/b15f506de696?raw)