The events API lets organizers create and manage cultural events tied to registered ECHO venues. All GET endpoints are public and require no authentication. Creating or updating events requires a valid Bearer token in theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/HelenaLM32/ECHO/llms.txt
Use this file to discover all available pages before exploring further.
Authorization header. See Authenticate with the ECHO API for details on obtaining a token.
The base URL for all endpoints on a local development server is
http://localhost:8084. Replace this with your deployed API URL in production.Get all events
Example
Response fields
Unique identifier for the event.
ID of the venue where the event takes place.
Display title of the event.
Full description of the event.
Event start date and time in ISO 8601 format (e.g.,
2025-09-15T18:00:00).Event end date and time in ISO 8601 format.
Ticket price. Omitted if the event is free.
Event category (e.g.,
Ilustración, Música, Teatro).URL where attendees can purchase tickets.
URL of the event cover image.
Get events by creator
Path parameters
The numeric ID of the event creator.
Example
Get events at a venue
Path parameters
The numeric ID of the venue.
Example
Get event by ID
Path parameters
The numeric ID of the event to retrieve.
Example
Error codes
| Status | Meaning |
|---|---|
404 | No event exists with the given ID. |
Create event
multipart/form-data encoding to support cover image upload. Authentication is required.
Dates must be formatted as
yyyy-MM-ddTHH:mm or yyyy-MM-ddTHH:mm:ss. The seconds component is optional. Example: 2025-09-15T18:00.Form parameters
The numeric ID of the venue where the event will take place. The venue must already exist on ECHO.
Event start date and time. Format:
yyyy-MM-ddTHH:mm or yyyy-MM-ddTHH:mm:ss.Event end date and time. Must be after
startDate. Format: yyyy-MM-ddTHH:mm or yyyy-MM-ddTHH:mm:ss.Display title of the event.
Full description shown to attendees on the event page.
Ticket price as a decimal number (e.g.,
10.00). Omit for free events.Category label for the event (e.g.,
Ilustración, Música, Teatro).URL where attendees can purchase tickets.
Cover image file for the event banner.
Example
Error codes
| Status | Meaning |
|---|---|
400 | Missing required fields, invalid date format, or endDate is before startDate. |
401 | No valid authentication token provided. |
404 | The specified venueId does not exist. |
Update event
multipart/form-data to allow cover image replacement. Authentication is required.
Path parameters
The numeric ID of the event to update.
Form parameters
Updated venue ID. The venue must already exist on ECHO.
Updated start date and time. Format:
yyyy-MM-ddTHH:mm or yyyy-MM-ddTHH:mm:ss.Updated end date and time. Format:
yyyy-MM-ddTHH:mm or yyyy-MM-ddTHH:mm:ss.Updated event title.
Updated event description.
Updated ticket price.
Updated category label.
Updated ticket purchase URL.
Replacement cover image file.
Example
Error codes
| Status | Meaning |
|---|---|
400 | Invalid date format or endDate is before startDate. |
401 | No valid authentication token provided. |
403 | Not authorized to update this event. |
404 | No event exists with the given ID. |