Fyno Verify

Verify OTP

This API enables you to validate the OTP entered by the user using either request_id (received in response of the Fire an Event API) or destination (such as phone number, email).

post/{WSID}/{version}/verify/validate

Path parameters

WSIDstring required

Enter your workspace ID. You can obtain this value from the API Keys page within your Fyno account.

version'live' | 'test' required

Specify the version for which you would like to manage the user profile.

Query parameters

request_idstring

Specify the request id of the triggered notification event that sent the OTP to the user. You must use this query parameter if you've disabled "Use destination as id" in the Fyno Verify setting.

destinationstring

Enter the destination where the OTP is sent. It can be either mobile no or email id. You must use this query parameter if you've enabled "Use destination as id" in the Fyno Verify setting.

otpstring required

Enter the OTP which you want to validate.

Response

OTP successfully validated

_messagestring required

statusstring required

Example response

{
  "_message": "OTP successfully validated.",
  "status": "ok"
}

Changes

Changed in 5 of the 35 revisions of this API.4110

Feb 17, 2025ee2cf82f4e6a6See the full diff
- ○
  the response property _message became required for the status 200
  response-property-became-required
- ○
  the response property _message became required for the status 400
  response-property-became-required
- ○
  the response property _message became required for the status 401
  response-property-became-required
- ○
  the response property status became required for the status 200
  response-property-became-required
- ○
  the response property status became required for the status 400
  response-property-became-required
- ○
  the response property status became required for the status 401
  response-property-became-required
Feb 10, 2025a0995c30bb0b1See the full diff
- ○
  endpoint added
  endpoint-added
Feb 10, 20252bbe1e92e0312See the full diff
- ▲
  api path removed without deprecation
  api-path-removed-without-deprecation
- ▲
  api path removed without deprecation
  api-path-removed-without-deprecation
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Feb 10, 20251e381a0ba09d111See the full diff
- ▲
  the query request parameter request_id became required
  request-parameter-became-required
- ●
  deleted the query request parameter destination
  request-parameter-removed
- ○
  endpoint added
  endpoint-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Feb 10, 20256f9dbe64142012See the full diff
- ▲
  api path removed without deprecation
  api-path-removed-without-deprecation
- ○
  added the new optional query request parameter destination
  new-optional-request-parameter
- ○
  the query request parameter request_id became optional
  request-parameter-became-optional

Full history