View Categories

Confirm email

< 1 min read

Table of Contents

Confirm Email #

Validates the six-digit verification code sent to the user and marks the email as verified so the onboarding flow can continue.

Endpoint #

POST https://api-test.10npay.com/User/email/confirm

Headers #

  • Authorization: Bearer <access_token>
  • Content-Type: application/json

Request Body #

{
  "id": 123,
  "token": "475013",
  "correlationType": 0
}
Field Type Description
id integer (int32) User identifier returned by POST /User. Required.
token string Six-digit code received in the verification email. Required.
correlationType integer (enum) Optional context flag — 0 for standard individual users, 1 for merchant correlation.

Responses #

200 OK — Email verified #

{
  "success": true,
  "message": "",
  "code": 200
}

4xx — Validation errors #

  • 400 Bad Request — invalid or expired code.
  • 404 Not Found — unknown userId.
  • 401 Unauthorized — missing/expired Bearer token.

5xx — Server errors #

Retry with exponential backoff; capture traceId from the response (if present) when contacting support.

Notes #

  • Only the most recent code sent through POST /User/email/send-confirmation is valid.
  • On success, isEmailVerified becomes true in the GET /User/{id}/status response.
  • If the user requests a new code, invalidate the previous one client-side and prompt for the latest value.
What are your Feelings