Eventmaker API

Name: Eventmaker API
Brand: Eventmaker API
Availability: InStock

✓ Official Vendor SpecProductivityCalendar SchedulingapiKey9 EndpointsREST

For Agents

Read Eventmaker events, create and update registrations, and list attendees for sync into a CRM or attendee communications workflow.

Install Jentic One Beta

Connect the Eventmaker API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eventmaker 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 Eventmaker API.

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

GET STARTED

Start building with Eventmaker API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Eventmaker API for, with concrete tasks.

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

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.

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.

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.

Search Jentic for 'create eventmaker registration', load the operation, and register a guest with name and email captured in chat

Key Endpoints

9 endpoints — the eventmaker api gives event organisers programmatic access to events, registrations, and attendees on the eventmaker platform.

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

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

Why Jentic?

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

Credential isolation

The Eventmaker API key is stored encrypted in the Jentic vault. Agents receive a scoped execution token at runtime, so the raw key is never present in the model context or in logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'create an eventmaker registration') and Jentic returns the matching operation with its input schema, so the agent supplies only the values that matter.

Time to first call

Direct integration: 4-8 hours for a working sync with retries and key rotation. Through Jentic: under 30 minutes from sign-up to first executed call.

FAQs

Specific to using Eventmaker API through Jentic.

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.