Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ricardomb-tech/auth-service/llms.txt

Use this file to discover all available pages before exploring further.

After registering, the user receives an email containing a single-use verification link. The link embeds a token that the client must forward to this endpoint. On success the account transitions from PENDING_VERIFICATION to ACTIVE status, after which it can be used to log in. Unlike the registration and resend endpoints, this endpoint distinguishes success from failure with different HTTP status codes — the caller already possesses the token, so there is no enumeration risk in signalling an invalid or expired token clearly.

​
POST /auth/verify

Authentication: None required

​
Request Body

​
token
string
required
The verification token extracted from the link in the verification email. Must not be blank.

​
Response — 200 OK

{
  "message": "Tu cuenta ha sido verificada. Ya puedes iniciar sesión."
}

​
Error Responses

StatusCondition
400 Bad RequestThe token is invalid, has already been consumed, or has expired. Returns application/problem+json with a detail field describing the reason.
Example 400 response: 
{
  "type": "about:blank",
  "title": "Bad Request",
  "status": 400,
  "detail": "El token de verificación es inválido o ha expirado.",
  "instance": "/auth/verify"
}

​
curl Example

curl -s -X POST http://localhost:8080/auth/verify \
  -H 'Content-Type: application/json' \
  -d '{
    "token": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  }'
Token TTL is 24 hours. If the verification link has expired before the user clicks it, they can request a fresh one via POST /auth/resend-verification using the same email address. The expired token will be rejected with a 400 response.

Build docs developers (and LLMs) love

Get started for freeTalk to us