Skip to main content
POST
Claim a domain for bind-on-verify

Authorizations

Authorization
string
header
required

Bearer token in the Authorization header. Two token types are accepted:

  • Organization API key (sk_...) issued via the dashboard. Org-scoped, long-lived, for server-to-server use.
  • User JWT obtained via the OAuth 2.1 authorization code flow with PKCE. User-scoped, short-lived. Discover the authorization server at /.well-known/oauth-authorization-server and the protected-resource metadata at /.well-known/oauth-protected-resource/api.

Path Parameters

domain
string
required
Example:

"examplepub.com"

Response

Claim issued

success
enum<boolean>
required
Available options:
true
domain
string
required
authoritative_location
string
required
instructions
string
required