account.createVerification
import { Client, Orvano } from '@orvano/js'
const orvano = new Orvano(new Client({ endpoint: 'https://orvano.example.com' }))
await orvano.account.createVerification({ redirectUrl: 'https://app.example.com/auth/callback' })// app/page.tsx, a server component. Route handlers and server actions use createServerClient too.import { cookies } from 'next/headers'import { createServerClient } from '@orvano/nextjs'
export default async function Page() { const orvano = createServerClient({ endpoint: process.env.ORVANO_ENDPOINT!, cookies: await cookies(), }) await orvano.account.createVerification({ redirectUrl: 'https://app.example.com/auth/callback' }) return <p>Done</p>}import 'package:orvano_flutter/orvano_flutter.dart';
Future<void> main() async { final orvano = Orvano(Client(endpoint: 'https://orvano.example.com')); await orvano.account.createVerification( CreateVerificationRequest( redirectUrl: 'https://app.example.com/auth/callback', ), );}Emails the signed in user a link that verifies their email.
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.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”A request to email a verification link to the signed in user.
object
Your page that receives the link: a host that is one of the project’s web platforms (http only on localhost
or 127.0.0.1), or your app’s own scheme (its iOS, Android, or macOS identifier). The link adds
orvano_type=verification and orvano_token to it.
Responses
Section titled “Responses”The request has been accepted for processing, but processing has not yet completed.
default
Section titled “default”An unexpected error response.
An RFC 9457 problem details body. Every operation declares it as its default response, sent
as application/problem+json.
object
Identifies the error: https://orvano.dev/errors/<code>.
The standard HTTP reason phrase for the status.
The HTTP status code.
A short, safe sentence about this occurrence, when the server has one.
Orvano’s stable error code, from the ErrorCode catalog. SDKs treat it as a plain string.
The request ID to quote when reporting a problem; also sent as X-Request-Id.
Example
{ "type": "https://orvano.dev/errors/not_found", "title": "Not Found", "status": 404, "code": "not_found", "requestId": "4bf92f3577b34da6a3ce929d0e0e4736"}