Base URL:
Version: 1.0.0
Authentication: API key required in
https://api.evento.so/api/public/v1
Version: 1.0.0
Authentication: API key required in
x-evento-api-key
headerQuick Start
Get up and running with the Evento Public API in minutes.Get API Access
Schedule a call with our team to get your API key.
View Endpoints
Explore our 5 available endpoints for event data.
Authentication
Learn how to authenticate your API requests.
Response Format
Understand our consistent response structure.
Available Endpoints
The Evento Public API offers 5 endpoints to access event data:Events
- GET /events/ - Retrieve detailed information about a specific event
Users
- GET /users//events - Get all public events created by a user
- GET /users//profile-events - Get events created by or RSVP’d to by a user
- GET /users//upcoming-events - Get upcoming events hosted by a user
- GET /users//past-events - Get past events hosted by a user
All endpoints return only public, published events. Private or draft events are never accessible via the Public API.
Authentication
All API requests require authentication via an API key. Include your API key in the request headers:Example Request
Obtaining an API Key
To obtain an API key, please contact the Evento development team:Schedule API Access Call
Our team will provide you with an API key and discuss your use case.
Response Format
All API responses follow a consistent JSON structure:Success Response
Error Response
Features
Date Filtering
Filter events by date range using
since
, from
, and to
parametersPagination
Control result sets with
limit
and offset
parameters (max 100 per page)Event Details
Get comprehensive event information including location, dates, creator, and links
Contribution Methods
Access payment and donation methods for events
Query Parameters
Date Filtering
since
orfrom
- Filter events starting from this date (ISO 8601)to
- Filter events up to this date (ISO 8601)
Pagination
limit
- Number of results to return (1-100, default varies by endpoint)offset
- Number of results to skip for pagination
Event Object
Events returned by the API include the following fields:Field | Type | Description |
---|---|---|
id | string | Unique event identifier |
title | string | Event title |
description | string | Event description (may contain markdown) |
cover | string | URL to event cover image |
location | string | Event location |
start_date | string | Event start date/time (ISO 8601) |
end_date | string | null | Event end date/time (ISO 8601) |
timezone | string | Event timezone (IANA timezone) |
status | string | Always “published” for public API |
visibility | string | Always “public” for public API |
cost | number | null | Event cost in USD (null = free) |
created_at | string | Event creation timestamp |
creator | object | Event creator information |
links | object | External links (Spotify, Wavlake) |
contributions | object | Payment/donation methods |
HTTP Status Codes
200 - Success
200 - Success
The request was successful. Data is returned in the response body.
400 - Bad Request
400 - Bad Request
Invalid parameters or request format. Check the error message for details.
401 - Unauthorized
401 - Unauthorized
404 - Not Found
404 - Not Found
The requested resource was not found.
500 - Internal Server Error
500 - Internal Server Error
Server error. Please try again or contact support if the issue persists.
Rate Limiting
Currently, there are no enforced rate limits. However, we recommend:- Maximum 100 requests per minute per API key
- Implement exponential backoff for retries
- Cache responses when appropriate
Please use the API responsibly. Excessive usage may result in rate limiting being implemented.
Best Practices
Caching
Implement appropriate caching to reduce API calls
Error Handling
Always check the
success
field before processing dataPagination
Use pagination for large result sets to improve performance
Date Filtering
Use date filters to retrieve only relevant events
Code Examples
JavaScript/Node.js
Python
Need Help?
API Reference
Detailed endpoint documentation with examples.
Contact Support
Get help from our technical team.
Changelog
Version 1.0.0 (August 26, 2025)
- Renamed API path from
/api/ext/v1
to/api/public/v1
- Reorganized endpoints to be more RESTful
- Added 4 new endpoints for user events
- Improved documentation and added comprehensive examples