Creating an event requires aDocumentation 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.
multipart/form-data request containing two parts: a JSON-encoded EventoDTO payload under the key evento, and an optional binary image file under the key image. The server validates the DTO fields, stores the image if provided, and persists the new event. Upon successful creation the endpoint returns the full EventoDTO of the newly created event, including its assigned id.
The authenticated participant is automatically added as both a participant and an administrator of the created event. You do not need to include the creator’s ID in
participantesEvento or administradores — those fields are ignored on creation and derived server-side.Endpoint
Authorization header.Content-Type:
multipart/form-data
Request Parts
A JSON-encoded
EventoDTO object. Must be sent as the part named evento. The following fields are recognised:nombreEvento(string, required) — The display name of the event. Must not be blank. Maximum 255 characters.tipoEvento(string, optional) — A category or type label. Maximum 255 characters.fechaEvento(string, optional) — The scheduled date inYYYY-MM-DDformat. If provided, the date must not be in the past.informacion(string, optional) — Free-text description or details about the event.chat(string, optional) — A chat identifier or thread reference to associate with the event.privado(boolean, optional, defaultfalse) — Set totrueto mark the event as private.oculto(boolean, optional, defaultfalse) — Set totrueto hide the event from all general listings.maxNumParticipantes(integer, optional, default255) — Maximum number of participants. Must be between0and255inclusive.
An optional binary image file to use as the event’s banner. Accepted formats:
JPEG, PNG, GIF, WebP. Maximum file size: 5 MB. If omitted, imagenEvento in the response will be null.Response
Returns the fullEventoDTO of the newly created event. See Get Event for a description of every response field.
Response Example
curl Example
Error Responses
| Status | Description |
|---|---|
400 Bad Request | A @Valid constraint on the DTO was violated — for example, nombreEvento is blank or maxNumParticipantes is outside the 0–255 range. The mensaje field in the response body will contain the first failing validation message. |
401 Unauthorized | The Authorization header is missing, the token has expired, or the token signature is invalid. |
422 Unprocessable Entity | A domain-level validation rule was violated — for example, fechaEvento is set to a past date. |