Sessions

Retrieve a reverification

Changed on

Retrieve a reverification scoped to a session. A resource server can use this to validate a reverification id it received from its client: confirm it is real, scoped to the expected session, completed, and how fresh each factor is. Single-use / replay detection is the caller's responsibility (the id is stable, so the caller dedups consumed ids).

get/sessions/{session_id}/reverifications/{reverification_id}

Request

  • Base URL: https://api.clerk.com/v1
  • URL: https://api.clerk.com/v1/sessions/{session_id}/reverifications/{reverification_id}
  • Auth: HTTP bearer

Path parameters

session_idstring required

The ID of the session the reverification belongs to

reverification_idstring required

The ID of the reverification

Response

Success

object'reverification' required

String representing the object's type. Objects of the same type share the same value.

idstring required
session_idstring required
user_idstring required
level'first_factor' | 'second_factor' | 'multi_factor' required

The level used for the reverification

status'needs_first_factor' | 'needs_second_factor' | 'complete' required
first_factor_verified_atinteger nullable required

Unix timestamp (ms) of the first factor verification, or null if not verified.

second_factor_verified_atinteger nullable required

Unix timestamp (ms) of the second factor verification, or null if not verified.

created_atinteger required

Unix timestamp of creation.

updated_atinteger required

Unix timestamp of last update.

Changes