Skip to main content
PATCH
Resend OTP

Headers

Idempotency-Key
string

Optional. A unique value you choose, such as a UUID, that makes retries safe. For 24 hours, a request with the same Idempotency-Key value and the same path parameters, query and body returns the original response instead of running again. Values are scoped to your API key and to this endpoint. A 409 means the first request with this value is still running (this clears within 5 minutes), or the value was already used for a different request. A 503 with Retry-After means nothing ran: retry with the same value after that many seconds.

Example:

"a96d14c5-8e60-4f6b-9d80-5c18c0e4202a"

API-Version
string

Pin request, response, and webhook shapes to a specific dated API version (YYYY-MM-DD). Omit to use the version pinned to your API key (set when the key is created; new keys default to the latest version). New integrations should target the latest version.

Pattern: ^\d{4}-\d{2}-\d{2}$
Example:

"2026-11-02"

Path Parameters

requestId
string
required

Unique identifier of the credential request. Must be a valid MongoDB ObjectId.

Example:

"507f1f77bcf86cd799439011"

Query Parameters

id
string

User's VIA identifier

Example:

"did:web:humanos.tech:user:73ebefdd-a549-4873-aad9-def80c40c8c8"

internalId
string

Identifier to help you identify the user in your own system. We recommend using a unique value.

Example:

"internal-12345"

contact
string

Contact email or phone, including documented synthetic request aliases

Response

Returns a confirmation that the OTP was sent successfully via email or SMS.

ok
boolean
required

Whether the operation was successful

Example:

true