FortWatchFortWatchDocs
Menu

Get the ownership state

GEThttps://api.fortwatch.ai/app/assets/{id}/ownership
Scope assets:readOperation ID getAssetOwnership

Whether the asset's ownership is proven and how, with the DNS TXT record or the HTTP file that proves it.

Parameters

NameInTypeDescription
idrequiredpathinteger

Example request

curl -X GET "https://api.fortwatch.ai/app/assets/42/ownership" \
  -H "Authorization: Bearer $FORTWATCH_API_KEY"

Response 200

The request succeeded.

FieldTypeDescription
verifiedrequiredboolean
verifiedAtrequiredstring (date-time) | null
methodrequiredobject | null
challengerequiredobject
tokenrequiredstring
methodsrequiredstring[]
dnsrequiredobject
hostrequiredstring
typerequiredstring
valuerequiredstring
httprequiredobject
urlrequiredstring
pathrequiredstring
contentrequiredstring
json
{
  "verified": true,
  "verifiedAt": "2026-10-16T12:00:00.000Z",
  "method": {},
  "challenge": {
    "token": "string",
    "methods": [
      "string"
    ],
    "dns": {
      "host": "app.example.com",
      "type": "string",
      "value": "app.example.com"
    },
    "http": {
      "url": "string",
      "path": "string",
      "content": "string"
    }
  }
}

Errors

400The request is not valid: a field is missing or has the wrong shape (the message names it).
401No valid credentials: the API key or access token is missing, revoked or expired (INVALID_API_KEY, INVALID_TOKEN).
403Not allowed: the key or token lacks this scope (SCOPE_REQUIRED), the route is dashboard-only (SESSION_REQUIRED), or a plan limit applies.
404Not found in your workspace.
429Too many requests (RATE_LIMITED): wait the seconds Retry-After gives.