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.

Deleting an event is a permanent, irreversible operation. When this endpoint is called, the event record is removed from the database along with all of its associated participant memberships and administrator assignments. There is no soft-delete or recovery mechanism — once deleted, the event and its relationships cannot be restored.
Deleting an event removes it permanently, including all associated participant memberships and administrator assignments. Any participant IDs that were enrolled in the event will lose their association. This action cannot be undone.

​
Endpoint

DELETE /api/eventos/delete/{id}
Requires a valid JWT access token sent in the Authorization header.

​
Path Parameters

​
id
integer
required
The unique numeric database ID of the event to delete. This value is available as the id field on any event listing or detail response.

​
Response

On success, the server returns 200 OK with an empty response body. No Content-Type header or JSON payload is included.

​
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 with status, mensaje, and timestamp fields.
404 Not FoundNo event exists with the supplied id. The event may have already been deleted or the ID may be incorrect.

​
401 Example

{
  "status": 401,
  "mensaje": "Token inválido",
  "timestamp": 1718467200000
}

​
404 Example

{
  "status": 404,
  "mensaje": "Evento no encontrado",
  "timestamp": 1718467200000
}

​
curl Example

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

Build docs developers (and LLMs) love

Get started for freeTalk to us