Releases Index
Verify a claim
View .md

Check the proof for a pending ownership claim

POST
/listing/claim/verify

Signed-in only, and the claim must belong to the caller (404 otherwise — no existence oracle). Checks the well-known token file and the DNS TXT record; either passes. Fails closed on any ambiguous response. 200 whether or not it verifies.

Authorization

bearerAuth
headerAuthorizationBearer <relk_… | relu_… | OAuth JWT>

Machine/operator tokens use the relk_ prefix; self-serve read-only user keys use relu_; Sign in with Releases supplies an OAuth access token. Required scope depends on the endpoint.

Request Body

application/json
  1. body
claimId*string
Length1 <= length

Response Body

Verification result (verified may be true or false)

application/json
  1. response
verified*boolean
checked*
claim*
Example Request
curl -X POST 'https://api.releases.sh/v1/listing/claim/verify' \  -H 'Content-Type: application/json' \  -d '{  "claimId": "string"}'
Example Response
{  "verified": true,  "checked": {    "wellKnown": "ok",    "dnsTxt": "ok"  },  "claim": {    "id": "string",    "org": {      "slug": "string",      "name": "string",      "webUrl": "string"    },    "status": "pending",    "method": "well-known",    "token": "string",    "createdAt": "string",    "verifiedAt": "string",    "revokedAt": "string",    "expiresAt": "string",    "instructions": {      "wellKnownUrl": "string",      "dnsRecordName": "string"    }  }}