Eventlayer / API & operations
API reference
Find endpoint schemas and the context needed to make a request.
The interactive reference lists Eventlayer’s HTTP operations, request bodies and response schemas. Start with the quickstart if you are making your first call.
Authentication
Use your server-side API key for API requests. Manage keys and webhook endpoints in the dashboard. Incoming webhooks use a separate signing secret. See authentication.
SDK and HTTP field names
SDK input uses camelCase, such as attendeeId and startAt. HTTP request bodies
use fields such as attendee_id and start_at. Resource responses retain the
HTTP field names. Examples label their language and execution context.
Handle the response
The SDK returns { data, error, response }. Inspect error before using data.
Network failures throw. Raw HTTP responses have their own status and response
envelope; the interactive reference documents those schemas.
Use errors and request IDs, pagination and retries and recovery when building your integration.