Verify backend OTP

Verifies backend OTP sessions with server credentials.

POST/api/v1/backend-otp/verify

Auth: Bearer API key with server_otp scope

Required headers

Header	Required	Value	Description
Authorization	Yes	Bearer <token>	API key, server OTP key, or public OTP token depending on endpoint.
Content-Type	Yes	application/json	All POST requests expect JSON payloads.

Request body

Field	Type	Required	Description
sessionId	string	Yes	Session id from send route.
email	string	Yes	Email used during send.
code	string	Yes	OTP code.

Code examples (all supported languages)

Snippets use placeholder tokens. Replace them with real credentials from your dashboard.

curl -X POST "https://risumail.risu.in/api/v1/backend-otp/verify" \
  -H "Authorization: Bearer YOUR_SERVER_OTP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sessionId":"otp_backend_01J...","email":"user@example.com","code":"654321"}'

Response schema

Canonical schema inferred from the documented success payload. Copy this block when generating typed clients.

{
  "type": "object",
  "required": [
    "success",
    "data"
  ],
  "properties": {
    "success": {
      "type": "boolean"
    },
    "data": {
      "type": "object",
      "required": [
        "verified"
      ],
      "properties": {
        "verified": {
          "type": "boolean"
        }
      }
    }
  }
}

Success response example

{
  "success": true,
  "data": {
    "verified": true
  }
}

Common error cases

Status	Code	When
404	SESSION_NOT_FOUND	Session expired or unknown.
429	RATE_LIMITED	Too many verify attempts.

Implementation notes

This endpoint is optimized for backend service verification workloads.

Back to API reference index Error handling playbook