Verify email verification code

Consumes verification session and returns verified=true on success.

POST/api/v1/email-verification/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 call.
email	string	Yes	Verified email.
code	string	Yes	OTP code from user.

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/email-verification/verify" \
  -H "Authorization: Bearer YOUR_SERVER_OTP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sessionId":"ev_01J...","email":"user@example.com","code":"842103"}'

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
400	INVALID_CODE	Invalid code format or mismatch.
404	SESSION_NOT_FOUND	Session expired or unknown.

Implementation notes

Same verification payload shape as backend-otp verify endpoint.

Back to API reference index Error handling playbook