API Reference
The SEDL Public API provides programmatic access to your event logging and data retrieval capabilities. Our API is designed to be simple, reliable, and easy to integrate into any application.
Base URL
All API requests should be made to:
https://api.sedl.dev
Authentication
SEDL uses two types of authentication tokens depending on the operation:
Event Logging Token
Used for creating events (write operations):
- Found in your app's dashboard
- Required for all event creation requests
- Unique to each app
- Should be kept secure on your backend servers
Resource Token
Used for reading data (read operations):
- Used to retrieve existing events and analytics data
- Read-only access to specific apps
- Can be shared with analytics tools and team members
Never expose authentication tokens in client-side code. Always make API calls from your backend servers to keep tokens secure.
Available Endpoints
Event Management
POST /public/create_event- Create a new eventGET /public/get_events- Retrieve events with filtering
Data Format
All API requests and responses use JSON format. Make sure to include the appropriate headers:
Content-Type: application/json
Rate Limiting
To ensure service quality for all users, the SEDL API implements rate limiting:
- Event Creation: 1000 requests per minute per app
- Data Retrieval: 100 requests per minute per resource token
When rate limits are exceeded, the API will return a 429 Too Many Requests status code.
Error Handling
The API uses standard HTTP status codes to indicate success or failure:
| Status Code | Meaning |
|---|---|
200 | OK - Request successful |
201 | Created - Event created successfully |
400 | Bad Request - Invalid request data |
401 | Unauthorized - Invalid or missing authentication |
403 | Forbidden - Access denied to resource |
404 | Not Found - Resource doesn't exist |
429 | Too Many Requests - Rate limit exceeded |
500 | Internal Server Error - Server-side issue |
Error Response Format
When an error occurs, the API returns a JSON response with details:
{
"success": false,
"error": "Invalid logging token",
"details": "The provided logging token is not valid or has expired",
"code": "AUTH_INVALID_TOKEN"
}
Getting Started
- Create an app in the SEDL dashboard
- Get your logging token from the app settings
- Create event types to categorize your events
- Start sending events using the API
Need Help?
- Check our Quick Start Guide for step-by-step setup
- Review Core Concepts to understand SEDL's data model
- See detailed endpoint documentation for creating events and retrieving data