Skip to main content

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.

The Events API exposes two listing endpoints. GET /api/eventos returns a summary of every event registered in the community, while GET /api/eventos/mis-eventos narrows that list to events in which the currently authenticated participant holds a membership. Both endpoints return an array of EventoPrincipalDTO objects — lightweight summaries intended for index and card views.

​
GET /api/eventos

Retrieves all community events. Both public and private events are returned; client-side filtering should be applied as needed based on the privado flag available in the full detail endpoint. Requires a valid JWT access token sent in the Authorization header.

​
Request

No query parameters or request body are required.

​
Response

Returns a JSON array of EventoPrincipalDTO objects.
​
id
Long
required
The event’s unique numeric identifier in the database.
​
nombreEvento
string
required
The human-readable display name of the event.
​
tipoEvento
string
An optional category or type label for the event (e.g. "meetup", "workshop"). May be null if not set.
​
fechaEvento
string
The scheduled date of the event in ISO 8601 format (YYYY-MM-DD). May be null if no date was provided at creation time.
​
imagenEvento
string
The filename of the event’s banner image stored on the server. Use this value to construct the full image URL. May be null if no image was uploaded.

​
Response Example

[
  {
    "id": 1,
    "nombreEvento": "Spring Boot Community Meetup",
    "tipoEvento": "meetup",
    "fechaEvento": "2025-09-20",
    "imagenEvento": "meetup-banner.png"
  },
  {
    "id": 2,
    "nombreEvento": "Open Source Workshop",
    "tipoEvento": "workshop",
    "fechaEvento": "2025-10-05",
    "imagenEvento": null
  }
]

​
curl Example

curl --request GET \
  --url http://localhost:8080/api/eventos \
  --header 'Authorization: Bearer <your_access_token>'

​
GET /api/eventos/mis-eventos

Returns only the events in which the currently authenticated participant is a member. The lookup is performed against the participant linked to the JWT token — no additional parameters are required. Requires a valid JWT access token sent in the Authorization header.

​
Request

No query parameters or request body are required.

​
Response

Returns a JSON array of EventoPrincipalDTO objects, filtered to the authenticated participant’s events. The shape of each object is identical to the response described above.

​
curl Example

curl --request GET \
  --url http://localhost:8080/api/eventos/mis-eventos \
  --header 'Authorization: Bearer <your_access_token>'

​
Error Responses

StatusDescription
401 UnauthorizedThe Authorization header is missing, the token has expired, or the token signature is invalid. The response body will contain an ErrorResponse object with status, mensaje, and timestamp fields.

​
401 Example

{
  "status": 401,
  "mensaje": "La sesión ha expirado",
  "timestamp": 1718467200000
}

Build docs developers (and LLMs) love

Get started for freeTalk to us