Install Jentic One Beta

Connect the Eventscase API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eventscase 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Feventscase.com%2Feventscase" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feventscase.com%2Feventscase" | 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 Eventscase API.

Retrieve events and individual event detail from Eventscase

List attendees per event and read individual attendee records

Manage the session schedule attached to each event

Read and update registration records by ID

Mirror Eventscase event data into a CRM or analytics warehouse

GET STARTED

Start building with Eventscase API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Eventscase API for, with concrete tasks.

★ Eventscase to CRM Sync

Mirror Eventscase attendees and registrations into Salesforce or HubSpot so commercial teams can act on signups while events are still live. The /attendees and /registrations endpoints provide the canonical lists, and the per-record reads give the structured payloads needed for CRM upserts. A working sync takes a day to wire up and runs continuously thereafter.

List attendees for event 'evt_2026' and upsert each one as a contact in HubSpot, tagging them with the event name

Schedule and Attendance Reporting

Produce sponsor and internal reports that combine the Eventscase session schedule with attendance numbers, so organisers know which sessions performed best. The /sessions and /attendees endpoints expose the structured data needed to build dashboards in Looker, Power BI, or Metabase. Reports are refreshed in minutes per cycle.

For event 'evt_2026', pull every session and the matching attendee count, then post a summary report to the #events Slack channel

Live Event Assistant

Power a chatbot that answers attendee questions like 'when is the AI keynote?' or 'is there a workshop on observability?' by calling the Eventscase sessions endpoint. The chatbot ships in hours when wired through a managed integration layer rather than directly against the API. This keeps on-site support staff focused on harder problems.

Call GET /sessions filtered by event ID and respond to 'when is the AI keynote at the user conference?' with start time and room

AI Agent Integration via Jentic

Connect Eventscase to an internal AI agent through Jentic so non-technical staff can pull attendee lists, schedule data, or registration counts in chat. Jentic handles credential isolation and intent search, so the API key never enters the model context. Set up takes minutes once Eventscase is connected.

Search Jentic for 'list eventscase attendees', load the operation, and answer 'how many people have registered for event evt_2026?'

Key Endpoints

13 endpoints — the eventscase api gives event organisers programmatic access to events, attendees, sessions, and registrations on the eventscase platform.

METHOD

PATH

DESCRIPTION

GET

/events

List events

GET

/events/{eventId}

Get a single event

GET

/attendees

List attendees

GET

/attendees/{attendeeId}

Get a single attendee

GET

/sessions

List sessions

GET

/registrations

List registrations

GET

/registrations/{registrationId}

Get a single registration

GET

/events

List events

GET

/events/{eventId}

Get a single event

GET

/attendees

List attendees

GET

/attendees/{attendeeId}

Get a single attendee

GET

/sessions

List sessions

GET

/registrations

List registrations

GET

/registrations/{registrationId}

Get a single registration

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Eventscase by hand means learning its X-API-Key header, tracking the api.eventscase.com/v2 base path, and coding the event, attendee, session, and registration reads yourself. Through Jentic you install once, import the Eventscase API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Eventscase puts the event id in the URL path (/events/{eventId}), so a rule can pin your agent to one event while still reading attendees, sessions, and registrations. Every operation is read-only here, and the agent only gets the ones you place in the allowed set.

Credential isolation

Your Eventscase 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.

Intent-based discovery

Agents search Jentic by intent such as 'list eventscase attendees' or 'read event sessions', and Jentic returns the matching Eventscase operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Eventscase API through Jentic.

What authentication does the Eventscase API use?

The Eventscase API uses an API key (ApiKeyAuth scheme). Through Jentic, the key is stored in the encrypted vault and injected at execution time, so it never appears in the agent's context or logs.

Can I list attendees per event with the Eventscase API?

Yes. GET /attendees returns attendees and GET /attendees/{attendeeId} reads an individual record. Combine with /events to scope by event when running cross-event reports.

What are the rate limits for the Eventscase API?

The OpenAPI spec does not declare explicit rate limits. Treat the API as standard for event SaaS, back off on HTTP 429 responses, and consult Eventscase developer documentation for current published limits.

How do I pull session schedules through Jentic?

Search Jentic for 'eventscase sessions', load the GET /sessions operation, and execute it filtered by event ID. Install with pip install jentic and use the async search, load, execute pattern.

Does the Eventscase API support reading registration records?

Yes. GET /registrations lists registrations and GET /registrations/{registrationId} reads a single record. This is the basis for CRM sync and reporting flows.

Can I limit what my agent is allowed to do with the Eventscase API?

Yes. Because you run Jentic One yourself, your own rules decide which Eventscase operations and credentials the agent may use, so you can hand it only the reads it needs, such as GET /sessions and GET /attendees, and withhold the rest. Since Eventscase carries the event id in the URL path at GET /events/{eventId}, a rule can pin the agent to a single event while it reads that event's attendees, sessions, and registrations. Every operation here is read-only, and the agent can call only the ones you place in the allowed set.

Eventscase API

Name: Eventscase API
Brand: Eventscase API
Availability: InStock

Official vendor OpenAPI document · agent-readyProductivityCalendar SchedulingapiKey13 EndpointsREST

For Agents

Read and manage Eventscase events, attendees, sessions, and registrations for syncing event data into CRMs, BI tools, and AI agents.

Use for: List all Eventscase events for our organisation, Get the attendee list for the user conference, Retrieve session schedule for event 'evt_2026', I want to read a specific registration record

Not supported: Does not handle payment processing, badge printing, or marketing email delivery - use for Eventscase event, attendee, session, and registration data only.

The Eventscase API gives event organisers programmatic access to events, attendees, sessions, and registrations on the Eventscase platform. With 13 operations across 8 paths it covers reading and managing events, listing and updating attendees, working with the session schedule, and tracking registrations. Authentication is via API key, and the API is well suited to syncing event data into CRMs, BI tools, and AI agents that answer attendee or schedule questions.

Jentic One on Github View OpenAPI Document