canonical: https://jentic.com/apis/eventleaf.com/eventleaf # Eventleaf API The Eventleaf API lets event organizers manage in-person and virtual events end to end, including event records, registrations, registration option groups, attendees, sessions, and contact lists. It exposes 38 operations across 29 paths for reading event details, capturing registration submissions, tracking session attendance, and synchronising contacts to external CRMs. The API uses an API key for authentication and is suited to event registration workflows, badge printing pipelines, and post-event reporting. ## For AI agents Look up Eventleaf events, retrieve and create registrations, track session attendance, and manage contact lists for event marketing follow-up. ## Scope Does not handle ticket payment processing, badge printing hardware, or marketing email delivery - use for event registration, attendance, and contact list management only. ## Capabilities - Retrieve event details, registration types, and session schedules from Eventleaf - Create new registrations against an event and update existing registration records - Search registrations and contacts by structured query rather than paginated browsing - Pull session attendance data for individual sessions or full events - Manage contact lists by adding, updating, or removing contacts captured at events - Inspect registration option groups and the registration form schema before submitting ## Use cases ### Event Registration Sync Pull new Eventleaf registrations into a CRM or marketing automation platform so sales and marketing teams can follow up with attendees in real time. The API exposes per-event registration listings and search, so an integration can poll for new entries or react to specific filters such as ticket type or company name. Most syncs run continuously during the event lead-up and complete in minutes per cycle. Example prompt: Fetch all registrations for event 12345 created in the last hour and write each new attendee to the connected CRM as a contact ### Session Attendance Reporting Capture which attendees joined each session for post-event analytics, sponsor reports, and CPD certificate issuance. The Eventleaf API returns attendance rosters per session and per event, enabling accurate session-level engagement metrics rather than headline event counts. Reports can be generated within hours of an event closing. Example prompt: Pull the attendance list for session ABC at event 12345 and email a CPD certificate to every confirmed attendee ### Contact List Management Maintain segmented contact lists captured from event registrations or contact-form opt-ins, then push those segments to an email service provider for nurture campaigns. The API supports list creation, contact add and remove operations, and structured search by attribute. Marketing teams can segment contacts in seconds rather than exporting CSVs. Example prompt: Create a new contact list called 'Q3 prospects' and add every contact who registered for events in the last 30 days ### AI Agent Integration via Jentic An AI assistant for an events team can answer questions about upcoming events, registration counts, and session capacity by calling the Eventleaf API through Jentic. The agent uses Jentic's intent search to find the right operation and Jentic's vault to inject the API key without exposing it to the model context. Setup takes minutes once a Jentic account is connected. Example prompt: Search Jentic for 'list eventleaf registrations', load the operation, and answer 'how many people have registered for the AGM so far?' ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /api/v1/events | List events visible to the API key | | GET | /api/v1/events/{eventId}/registrations | List registrations for an event | | POST | /api/v1/events/{eventId}/registrations | Create a new registration | | POST | /api/v1/events/{eventId}/registrations/search | Search registrations with structured filters | | GET | /api/v1/events/{eventId}/attendance | Read attendance data for an event | | GET | /api/v1/contactlists | List contact lists | | POST | /api/v1/contactlists/{contactListId}/contacts | Add a contact to a list | ## Key resources - **Events** — Read events and their metadata, registration option groups, registration types, and sessions - **Registrations** — Create, retrieve, update, and search registrations for an event - **Sessions** — List sessions and read session attendance rosters - **Contact Lists** — Create and manage contact lists and the contacts within them ## Why Jentic - **Setup:** Wiring Eventleaf by hand means learning its API key header, matching the api.eventleaf.com base path, and coding the per-event registration and contact-list calls yourself. Through Jentic you install once, import the Eventleaf API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Eventleaf puts the event id in the URL path (/api/v1/events/{eventId}/registrations), so a rule can pin your agent to one event: it can list and add registrations for that event and nothing else. You choose the operations it may call, so you can allow reading attendance and adding contacts while leaving anything you do not want out of the allowed set. - **Credential handling:** Your Eventleaf 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 'list eventleaf registrations' or 'add a contact to a list', and Jentic returns the matching Eventleaf operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Cvent API** — Enterprise event management platform with broader venue and travel features - **Swoogo API** — Event registration and management platform aimed at marketers - **Mailchimp Marketing API** — Send the captured event contacts into email marketing journeys - **Calendly API** — 1:1 and small-group scheduling alongside larger Eventleaf events ## FAQ ### What authentication does the Eventleaf API use? The Eventleaf API uses an API key sent with each request. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the agent calling /api/v1/events never sees the raw secret. ### Can I create new registrations through the Eventleaf API? Yes. POST /api/v1/events/{eventId}/registrations creates a registration for an event, and PATCH /api/v1/events/{eventId}/registrations/{registrationId} updates an existing one. The registration form schema is exposed at /api/v1/events/{eventId}/registrations/registrationform so you know which fields are required. ### What are the rate limits for the Eventleaf API? The OpenAPI spec does not declare explicit rate limits. Treat the API as standard for event SaaS providers and back off on HTTP 429 responses; check Eventleaf's developer documentation for the current published limits before running large bulk syncs. ### How do I pull session attendance through Jentic? Search Jentic for 'eventleaf session attendance', load the GET /api/v1/events/{eventId}/attendance/{sessionId} operation, then execute it with the event and session IDs. Install with pip install jentic and run the search, load, execute flow asynchronously. ### Does the Eventleaf API support searching registrations by email? Yes. POST /api/v1/events/{eventId}/registrations/search accepts structured filter criteria, so you can locate a registration by attendee email or other registration form fields without paging through the full list. ### Can I manage contact lists captured from event signups? Yes. The /api/v1/contactlists endpoints let you create lists, add and remove contacts, and search contacts within a list. This is useful for piping event signups into an email marketing tool segmented by event. ### Can I limit what my agent is allowed to do with the Eventleaf API? Yes. Because you run Jentic One yourself, your own rules decide which Eventleaf operations and credentials the agent may use. Since the event id sits in the URL path, such as /api/v1/events/{eventId}/registrations, you can pin the agent to a single event so it only lists and creates registrations there. You also choose the exact operations it can call, allowing it to read attendance or add contacts to a list while leaving every other endpoint out of the allowed set.