Skip to content
Orvanov0.2.0

account.verifyEmail

POST
/v1/account/verification/confirm
import { Client, Orvano } from '@orvano/js'


const orvano = new Orvano(new Client({ endpoint: 'https://orvano.example.com' }))


const user = await orvano.account.verifyEmail({
  token: 'orv_el_Zm9vYmFyZm9vYmFyZm9vYmFyZm9vYmFyZm9vYmFyZm9vYmE',
})
console.log(user)

Verifies a user’s email with the token from a verification link. It needs no session and creates none; a client signed in as that user refreshes its session, so the access token’s claim changes at once. The token works once.

Client SDKs: JavaScript in the browser, Next.js, and Flutter call it for the signed in user, or with no credential. A failure answers with a problem details body; its code has a page under Errors.

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json

An email verification, with the token from the emailed link.

object
token
required

The orvano_token parameter of the emailed link.

string

Responses

Section titled “Responses”

200

Section titled “200”

The request has succeeded.

Media typeapplication/json

A user of a project.

object
id
required

The user ID.

string
email
required
Any of:
string
emailVerified
required

Whether the email has been verified. Also the access token’s email_verified claim.

boolean
emailVerifiedAt
required
Any of:
string format: date-time
name
required
Any of:
string
status
required

Whether the user may sign in.

string
Allowed values: active blocked
metadata
required

Your own data about the user: a JSON object of at most 16 KB.

object
createdAt
required

When the user signed up.

string format: date-time
lastSignInAt
required
Any of:
string format: date-time
Example
{
  "id": "01924f5e-8d2b-7c4d-8e21-3d5e6f7a8b9c",
  "email": "ada@example.com",
  "emailVerified": false,
  "name": "Ada Lovelace",
  "status": "active"
}

default

Section titled “default”

An unexpected error response.

Media typeapplication/problem+json

An RFC 9457 problem details body. Every operation declares it as its default response, sent as application/problem+json.

object
type
required

Identifies the error: https://orvano.dev/errors/<code>.

string
title
required

The standard HTTP reason phrase for the status.

string
status
required

The HTTP status code.

integer format: int32
detail

A short, safe sentence about this occurrence, when the server has one.

string
code
required

Orvano’s stable error code, from the ErrorCode catalog. SDKs treat it as a plain string.

string
requestId
required

The request ID to quote when reporting a problem; also sent as X-Request-Id.

string
Example
{
  "type": "https://orvano.dev/errors/not_found",
  "title": "Not Found",
  "status": 404,
  "code": "not_found",
  "requestId": "4bf92f3577b34da6a3ce929d0e0e4736"
}