canonical: https://jentic.com/apis/eventmaker.io/eventmaker # Eventmaker API The Eventmaker API gives event organisers programmatic access to events, registrations, and attendees on the Eventmaker platform. With 9 operations across 5 paths it covers reading and creating events, retrieving event detail, managing registration records, and listing attendees for downstream sync into CRMs, badge systems, or marketing tools. Authentication is via API key, so it slots into agent workflows that pull live event data into reports or chat assistants. ## For AI agents Read Eventmaker events, create and update registrations, and list attendees for sync into a CRM or attendee communications workflow. ## Scope Does not handle payment processing, badge printing, or email delivery - use for Eventmaker event, registration, and attendee data only. ## Capabilities - Retrieve a list of Eventmaker events with their basic detail - Read a specific event by ID for capacity, dates, and metadata - Create new registrations against an event - Update or read existing registration records by ID - List attendees for an event for badge or follow-up workflows ## Use cases ### CRM Registration Sync Mirror new Eventmaker registrations into a CRM so sales reps can see which prospects signed up for which event in real time. The API exposes a registrations list and per-registration read so an integration can poll for new entries and push them to Salesforce, HubSpot, or Pipedrive. Setup typically takes a few hours of integration code. Example prompt: Fetch all registrations created today and push each one as a new contact and event interest record in the connected CRM ### Attendee Communications Generate pre-event reminders or post-event surveys by listing attendees per event and joining the data with an email or SMS service. The Eventmaker attendees endpoint gives the canonical attendee roster, so messaging tools always work from the same list of confirmed attendees. Most teams run this on the morning of the event and again the day after. Example prompt: List attendees for event 'summit-2026' and send each one a reminder email through SendGrid the day before the event ### Internal Event Catalog Power an internal events page or chat assistant that lists which Eventmaker events are running, who owns them, and how many registrations have come in. The events and registrations endpoints provide everything needed to build a lightweight internal directory or Slack bot. The first version can be built in an afternoon. Example prompt: Build a Slack message listing all Eventmaker events happening this month with their current registration count ### AI Agent Integration via Jentic Let an AI assistant book attendees onto Eventmaker events directly from a chat conversation. The agent uses Jentic to search for the registration operation, load its schema, and execute the call with vault-stored credentials. The whole loop is live within an hour of connecting an Eventmaker account to Jentic. Example prompt: Search Jentic for 'create eventmaker registration', load the operation, and register a guest with name and email captured in chat ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/events` | List events | | GET | `/events/{id}` | Get a single event by ID | | POST | `/registrations` | Create a registration | | GET | `/registrations/{id}` | Get a single registration | | GET | `/attendees` | List attendees | ## Key resources - **Events** — List events and read individual event detail - **Registrations** — Create, read, and update registrations against an event - **Attendees** — List attendees per event for follow-up workflows ## Why Jentic - **Setup:** Wiring Eventmaker by hand means learning its X-API-Key header, tracking the api.eventmaker.io/v1 base path, and coding the event, registration, and attendee reads yourself. Through Jentic you install once, import the Eventmaker API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Eventmaker takes the target event and attendee in the request body or query for registration and attendee reads, so scope the agent to the operations it needs, such as listing events and creating registrations, rather than to one record. Every operation you credit the agent with comes from the allowed set you define. - **Credential handling:** Your Eventmaker API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an eventmaker registration' or 'list events', and Jentic returns the matching Eventmaker operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Eventleaf API** — Comparable event registration platform with deeper session and contact list features - **Cvent API** — Enterprise event management with venue sourcing, travel, and compliance - **Mailchimp Marketing API** — Send pre-event and post-event campaigns to Eventmaker attendees - **Calendly API** — Book follow-up 1:1 meetings with Eventmaker attendees ## FAQ ### What authentication does the Eventmaker API use? The Eventmaker API uses an API key (apiKey scheme). When called through Jentic, the key is stored in the encrypted vault and injected at execution time so the agent never sees the raw secret. ### Can I create registrations through the Eventmaker API? Yes. POST /registrations creates a registration on an event, and GET `/registrations/{id}` reads the resulting record. The API is suited to programmatic signup flows from a custom landing page or chat assistant. ### What are the rate limits for the Eventmaker API? The OpenAPI spec does not declare rate limits explicitly. Eventmaker's developer documentation is the authoritative source; back off on HTTP 429 responses in production code and avoid tight polling loops. ### How do I list attendees for an event through Jentic? Search Jentic for 'eventmaker list attendees', load the GET /attendees operation, and execute it with the event filter. Install with pip install jentic and use the async search, load, execute pattern. ### Does the Eventmaker API expose all event metadata? GET `/events/{id}` returns the structured event record. The OpenAPI spec covers events, registrations, and attendees only; ticketing payments, custom field configuration, and email templates are managed in the Eventmaker dashboard rather than the API. ### Can I limit what my agent is allowed to do with the Eventmaker API? Yes. Because you run Jentic One yourself, your own rules decide which Eventmaker operations the agent may call and which credentials it may use. You can allow only the operations a task needs, such as listing events with GET /events and creating registrations with POST /registrations, while withholding others like reading a registration by ID or listing attendees. Every operation the agent can run comes from the allowed set you define, so it never reaches endpoints you have not granted.