---
title: "Desk Signup Verify"
method: POST
path: "/auth/desk-signup/verify"
tags: ["auth"]
---

# Desk Signup Verify

`POST /auth/desk-signup/verify`

## Request

- Base URL: `https://api-v1.unusual.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api-v1.unusual.ai/auth/desk-signup/verify`
- Auth: none declared

Check a pending claim's DNS TXT proof; provision on success (WO-10 §4.4).

UNAUTHENTICATED AND IT MINTS AN ORG, so the shape of this endpoint is
"re-run every gate, then believe the DNS":

* the claim is an INTENT, never a pre-approval — by the time a proof
  clears, days may have passed: the company may have become a real
  customer (host clash → 409), the address may have been registered
  (→ 409), the PSL may be unusable (→ 503). Every gate the signup ran, ran
  here again, minus the spend limits (the DNS proof is the spend gate on
  this path, and burning a company-host bucket per "did it propagate yet?"
  click would lock out the very customer mid-verification).
* the proof is single-use: success clears the token, and a promoted claim
  (domain attached) stops resolving at all.
* an unknown or expired claim is refused with nothing to enumerate — the
  claim id is an unguessable bearer handle, and the responses to "wrong"
  and "never existed" are identical.

## Request body

- DeskSignupVerifyRequest
  - `claim_id` string, required

## Response `200`

Successful Response

- BackendDashboardServerRoutesDeskSignupDeskSignupResponse
  - `status` string, required
  - `message` string, required
  - `organization_id` string, nullable
  - `domain_id` string, nullable
  - `next_step` string, required
  - `claim_id` string, nullable
  - `verification` object, nullable

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/unusual/apis/dashboard-server.md) - [All operations](https://skmtc.dev/unusual/apis/dashboard-server/llms.txt) - [OpenAPI document](https://skmtc.dev/unusual/apis/dashboard-server/revisions/89f716930ead?raw)