Verify user email

What it is for: Verify user email. Use this as part of password-based account authentication rather than broker system ingestion.
How to use it: Send a POST request to /auth/verify-email with the request body, query parameters, or multipart fields shown below. Authentication endpoint. It does not use the broker integration API key in the same way as /v1/... endpoints.
Successful response: HTTP 200. The body follows the endpoint schema; many integration endpoints wrap the useful payload under data with status and message.
Common error states:

400 invalid request body, query, ObjectId, pagination, file format, or missing required field.

401 missing, invalid, expired, or insufficient API key/token.

403 key is valid but cannot access this community/channel/user/resource, where supported by the service.

404 target resource, route, or community-scoped record was not found.

409 duplicate or conflicting state for create/update operations, where applicable.

500 unexpected Returning.AI service error.

curl --location 'https://api.returning.ai/auth/verify-email' \ --header 'Content-Type: application/json' \ --data-raw '{ "email": "samoqa@koletter.com", "code": "441225", "host": "ic.genesiv.com" }'

{ "meta": { "success": true, "message": "Email has been verified successfully", "devMessage": "Email has been verified successfully" }, "body": { "accessToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjIiLCJpYXQiOjE3MjE5MjI1MTYsImV4cCI6MTcyMjAwODkxNn0.RU6HbgnjhudD5h1hjCQ0OBo5HD2ANRtw8VNKHBLdvMA", "refreshToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjIiLCJpYXQiOjE3MjE5MjI1MTYsImV4cCI6MTcyMjUyNzMxNn0.95J7P0_vUGnAKARhwVhws0T-M_yZNzu-i-2XY-5H-Hk" } }

Request

Responses