Verify ownership

POSThttps://api.fortwatch.ai/app/assets/{id}/ownership/verify

Scope assets:writeOperation ID verifyAssetOwnership

Looks for the DNS TXT record or the HTTP file now. The first successful proof starts the asset's first scan; 422 when neither is found.

Parameters

Name	In	Type	Description
`id`required	path	integer

Example request

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

Response 200

The request succeeded.

Field	Type	Description
`verified`required	boolean
`method`required	object \| null
`alreadyVerified`required	boolean
`scan`required	object
`id`required	number
`assetId`required	number
`status`required	string
`createdAt`required	string (date-time)
`startedAt`required	string (date-time) \| null
`jobsTotal`required	number
`jobsDone`required	number

json

{
  "verified": true,
  "method": {},
  "alreadyVerified": true,
  "scan": {
    "id": 42,
    "assetId": 42,
    "status": "string",
    "createdAt": "2026-10-16T12:00:00.000Z",
    "startedAt": "2026-10-16T12:00:00.000Z",
    "jobsTotal": 1,
    "jobsDone": 1
  }
}

Errors

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

Every code is explained in Errors.

This page as Markdown