ownership

Read whether a site's ownership is verified, and how to prove it

Whether a site's ownership is verified, and for every method what to place where and the last check's verdict (last_error says why one failed). Before any check was started there is no token and methods is empty: start one with sites_verify. A verified site unlocks the verified-only crawl settings (rate faster than 250 ms, more than 2 requests at a time, user-agent presets, credentials, custom headers). Next: configs_get to see the settings that apply now.

get/v1/sites/{site}/verification

Request

  • Base URL: https://frontshelf.io/api
  • URL: https://frontshelf.io/api/v1/sites/{site}/verification
  • Auth: HTTP bearer

Path parameters

sitestring required

Site ID (site_…), origin (https://example.com), or bare domain, resolved server-side; the response carries the canonical ID.

Response

Read whether a site's ownership is verified, and how to prove it

summarystring required

The answer in one or two sentences, with the numbers it rests on.

warningsstring[] required

What limits this answer (a cap, a read that was cut short). Empty when nothing does.

site_idstring required
originstring required
verifiedboolean required

True while at least one proof holds: the verified-only crawl settings apply.

verified_atstring nullable required

Since when the site is verified (ISO 8601); null when it is not.

tokenstring nullable required

The site's verification token; null until a check was first started (sites_verify mints it).

settings_urlstring required

The site's verification page in Frontshelf (app-relative), to hand your human.

Changes

No recorded changes to this operation across all 1 revision of this API.