Reference in progress. ewent exposes more endpoints than are listed here. This page
covers the ones an integration actually needs and that we are willing to keep stable. The rest are internal and
may change without notice — if you need one that isn’t here,
ask rather than discovering it and depending on it.
Conventions
- Base URL
https://ewent.ai/api
Authorization: Bearer <key> on every request. Server-side only.- Every response carries
success. Failures add error.
ewent_token identifies an occurrence; rsvp_token an attendee within it.- Timestamps are ISO 8601. Send UTC and let ewent localise per attendee.
Events
| Method | Endpoint | What it does | Parameters |
|---|
POST |
occurrence_create |
Create a dated occurrence. |
title, start, timezone, location? |
POST |
occurrence_update |
Update an occurrence in place. |
ewent_token, + fields to change |
POST |
event_status |
Cancel, suspend or restore an occurrence. Triggers the broadcast. |
ewent_token, status |
Attendees
| Method | Endpoint | What it does | Parameters |
|---|
POST |
rsvp_create |
Attach an attendee. Returns the signed checklist URL. |
ewent_token, email, name?, timezone? |
GET |
rsvp_lookup |
Find an attendee record for an event. |
ewent_token, email | rsvp_token |
POST |
rsvp_cancel |
Cancel on the attendee’s behalf. Stops the pending cadence. |
ewent_token, rsvp_token |
GET |
attendees_export |
Export the attendee list for an occurrence. |
ewent_token |
Checklist
| Method | Endpoint | What it does | Parameters |
|---|
POST |
steps_set |
Replace the step list for an event. |
ewent_token, steps (JSON array) |
Partners
| Method | Endpoint | What it does | Parameters |
|---|
POST |
partners_set |
Replace speakers, sponsors and exhibitors for an event. |
ewent_token, partners (JSON array) |
POST |
partner_add |
Add a single partner record. |
ewent_token, kind, name, … |
POST |
partner_delete |
Remove a partner record. |
ewent_token, partner_id |
Messaging
| Method | Endpoint | What it does | Parameters |
|---|
POST |
send_email |
Send or dry-run a cadence message. |
ewent_token, rsvp_token, cp, test=1 | dryrun=1 |
POST |
email_consent |
Record or withdraw consent for an address. |
email, consent |
Errors
| Status | Meaning |
|---|
401 | Missing or invalid key |
404 | Unknown token |
405 | Wrong HTTP method for this endpoint |
422 | Validation failed — error says which field |
429 | Rate limited — retry after a short pause |
Not available yet
Said plainly so you don’t design around them: self-serve API keys, a sandbox environment, and
outbound webhooks. All three are planned. Until webhooks land, poll rsvp_lookup or take
the export.
ewent