Verify email address using a verification token

POST

/api/v1/auth/verify-email

Code sample: cURL

curl -X POST 'https://api.justcrawl.io/api/v1/auth/verify-email' \
  -H 'Content-Type: application/json' \
  -d '{"token":"<verification-token-from-email>"}'

• Production

Completes the email-verification flow. The token is single-use and has a 24-hour TTL. On success the user’s emailVerifiedAt timestamp is set and all pending verification tokens for this user are invalidated. The endpoint is idempotent: calling with a valid token on an already-verified account returns 200 with the “already verified” message instead of an error. Email verification unlocks the write-heavy operations (CSV upload, schedule create / trigger).

Agent Playground U13/KTD-8: if the verifying user has no organization yet, one is created from their email (the same provisioning the OAuth callback and POST /orgs’s empty-body path use) and the response carries org + an org-bearing accessToken so the client can commit it immediately, without waiting on the next token refresh to pick up the new membership.

Request Body^required

Media typeapplication/json

object

token

required

string

Example^generated

{
  "token": "example"
}

Responses

200

Email verified (or already verified). org and accessToken are present only when a fresh org was created.

Media typeapplication/json

object

message

string

org

object

accessToken

string

defaultApiKey

One-time plaintext API key for the new org — only present when org was just created.

string

Example^generated

{
  "message": "example",
  "org": {},
  "accessToken": "example",
  "defaultApiKey": "example"
}

400

Validation failed — request body or query is missing/invalid

Media typeapplication/json

object

error

string

Example

{
  "error": "Missing or invalid \"url\" field"
}

500

Unexpected server error. Logs and PostHog $exception capture

Media typeapplication/json

object

error

string

Example

{
  "error": "Something went wrong"
}