The registration endpoint creates a brand-new user account and, in the same transaction, automatically provisions an associated Participant profile using the same username. On success it returns a signed JWT access token (valid for 1 hour) and a refresh token (valid for 7 days) that the client can use immediately to authenticate subsequent requests.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CristianRR94/springCommunity/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
Request Body
The username for the new account. Must be between 6 and 20 characters and must be unique across all registered users. Used as the login identifier — not the email address.
The account password. Must be at least 8 characters long and contain at least one digit (0–9).
A valid email address. Must follow standard email format and must be unique across all registered users.
Request Example
Response
A200 OK response with a JSON body containing both tokens.
A signed JWT access token. Include this in the
Authorization: Bearer <token> header for all protected requests. Default TTL: 1 hour (configurable via JWT_EXPIRATION).A signed JWT refresh token. Use this with
POST /auth/refresh to obtain a new token pair once the access token expires. Default TTL: 7 days (configurable via JWT_REFRESH_EXPIRATION).Response Example
Error Responses
| Status | Condition |
|---|---|
400 Bad Request | Validation failure — e.g., nombre is shorter than 6 characters, password does not contain a digit, or email is not a valid email format. The response body contains a single mensaje field with the first validation error message. |
Error Response Body
curl Example
Registering a user also creates an associated Participant profile with the same username (
nombre). This participant profile is required to join events and send messages in the community. Both the user and participant records are created within a single database transaction — if either step fails, neither record is persisted.