Eventleaf API

Name: Eventleaf API
Brand: Eventleaf API
Availability: InStock

✓ Official Vendor SpecProductivityCalendar SchedulingapiKey38 EndpointsREST

For Agents

Look up Eventleaf events, retrieve and create registrations, track session attendance, and manage contact lists for event marketing follow-up.

Install Jentic One Beta

Connect the Eventleaf API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eventleaf API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Eventleaf API.

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

GET STARTED

Start building with Eventleaf API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Eventleaf API for, with concrete tasks.

★ 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.

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.

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.

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.

Search Jentic for 'list eventleaf registrations', load the operation, and answer 'how many people have registered for the AGM so far?'

Key Endpoints

38 endpoints — 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.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Eventleaf API key is stored encrypted in the Jentic vault. Agents receive a scoped execution token at run time and never see the raw key, so it cannot be leaked through a model prompt or log line.

Intent-based discovery

Agents search Jentic by intent (e.g., 'list eventleaf registrations') and Jentic returns matching operations with their input schemas, so the agent calls the right path without reading Eventleaf's documentation.

Time to first call

Direct integration: 1-2 days to wire registration polling, attendance pulls, and key rotation. Through Jentic: under 30 minutes from sign-up to executing the first registration query.

FAQs

Specific to using Eventleaf API through Jentic.

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.

Eventleaf API

Connect the Eventleaf API to your agent

Capabilities

Start building with Eventleaf API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs