Install Jentic One Beta

Connect the Livestorm to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Livestorm, 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%2Fapi.livestorm.co%2Flivestorm" | 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%2Fapi.livestorm.co%2Flivestorm" | 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 Livestorm API.

Create events and update their topic, agenda, and configuration

Schedule sessions for an event with start time, recording mode, and language

Retrieve a full attendee list with engagement metrics for a session

Subscribe to webhooks for events such as session.attended or registration.created

GET STARTED

Start building with Livestorm API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Livestorm API for, with concrete tasks.

★ Marketing Webinar Automation

Drive webinar registration directly from a marketing automation tool. POST /events creates the event, POST /events/{id}/sessions schedules the session, and POST /sessions/{id}/people/bulk registers attendees imported from a campaign list. The webhook subscriptions then notify the marketing stack when registrants attend so segmentation and follow-up emails fire automatically.

Call POST /events to create 'Summer Product Launch', POST /events/{id}/sessions for 2026-07-15 14:00, then POST /sessions/{id}/people/bulk with the registration list.

Engagement Reporting and CRM Sync

Pull session attendance and engagement data into a CRM after each webinar. GET /sessions/{id}/people returns the participant list with attended flag and engagement metrics, which an integration job maps into CRM contact records. This replaces manual CSV exports from the Livestorm dashboard and makes attendance data available for sales follow-up within minutes of a session ending.

Call GET /sessions/{id}/people for the latest session ID, filter attended=true, and upsert each person as a CRM contact with the engagement score.

Webhook-Driven Realtime Notifications

Subscribe to Livestorm webhooks to react to registrations, attendance, and session lifecycle events in real time. The webhooks resource lets an agent register a callback URL and the events it cares about; Livestorm then POSTs JSON payloads as those events occur. This is ideal for slack notifications, on-the-fly Zapier-style routing, or live analytics dashboards.

Subscribe a webhook for 'session.attended' to https://hooks.example.com/livestorm and confirm the subscription returns a 201 with the webhook ID.

AI Agent Webinar Operations

An AI agent running events can schedule sessions, manage registrations, and pull attendance reports through Livestorm via Jentic. Jentic exposes events, sessions, people, and webhooks operations as discoverable tools chosen by intent, while the API key or OAuth token stays in your Jentic One instance.

Search for 'register a person for a webinar session', load the POST /sessions/{id}/people schema, and execute it for the email and session ID provided in agent input.

Key Endpoints

40 endpoints — livestorm is a webinar and meeting platform whose v1 api exposes events (the campaign or topic), sessions (individual instances of an event), people (registrants and attendees), webhooks for outbound notifications, and supporting workspace endpoints.

METHOD

PATH

DESCRIPTION

GET

/events

List events

POST

/events

Create an event

POST

/events/{id}/sessions

Schedule a session for an event

GET

/sessions/{id}/people

List session participants

POST

/sessions/{id}/people

POST

/sessions/{id}/people/bulk

Bulk register people for a session

GET

/me

Get the authenticated user and organization

GET

/events

List events

POST

/events

Create an event

POST

/events/{id}/sessions

Schedule a session for an event

GET

/sessions/{id}/people

List session participants

POST

/sessions/{id}/people

POST

/sessions/{id}/people/bulk

Bulk register people for a session

GET

/me

Get the authenticated user and organization

Why Jentic?

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

Setup

Wiring Livestorm by hand means choosing between its API key header and OAuth2 scheme and coding your own calls to the events, sessions, and registrant endpoints. Through Jentic you install once, import Livestorm from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Livestorm puts the event and session id in the URL path (/events/{id}/sessions, /sessions/{id}/people), so a rule can pin your agent to one event or session. You choose the operations it may call, so bulk registrant creation is not included unless you add it.

Credential isolation

Your Livestorm credential 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 'create a webinar event' or 'register a person for a session', and Jentic returns the matching Livestorm operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Livestorm API through Jentic.

What authentication does the Livestorm API use?

Livestorm supports both API key authentication (passed in a header) and OAuth 2.0 for partner integrations. Through Jentic, whichever credential you supply is stored encrypted in the vault and injected at execution time, so the agent never holds the raw value.

Can I bulk-register attendees with the Livestorm API?

Yes. POST /sessions/{id}/people/bulk accepts a list of registrants in a single request - name, email, and optional registration fields per person. This is the right endpoint for importing a marketing list rather than calling POST /sessions/{id}/people one person at a time.

What are the rate limits for the Livestorm API?

Livestorm applies per-account rate limits and returns 429 responses with a Retry-After header when exceeded. Bulk registration endpoints are intended exactly to avoid burst calls, so prefer /people/bulk to per-person registration when importing large lists.

How do I retrieve attendees of a session through Jentic?

Run pip install jentic, then search for 'list attendees of a webinar session'. Jentic returns the GET /sessions/{id}/people operation. Load its schema, pass the session id and any filters (attended, registered_at), then execute to get the participant list.

Is the Livestorm API free to use?

API access is included with paid Livestorm plans; the free plan does not include API access. Pricing is published on livestorm.co. The API itself does not charge per call - usage counts against the same plan limits as the web product.

How do I subscribe to Livestorm webhooks?

Use the webhooks resource to POST a new subscription with your callback URL and the event types you want delivered (for example session.attended, registration.created). Livestorm sends a JSON payload to your URL each time a matching event fires; the subscription can be deleted via the same resource.

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

Yes. Because you run Jentic One yourself, your own rules decide which Livestorm operations the agent may call and which credential it uses. Livestorm puts the event and session id in the URL path, such as /events/{id}/sessions and /sessions/{id}/people, so you can pin the agent to a single event or session. You can also grant read-only access, for example GET /sessions/{id}/people, while excluding write actions like POST /sessions/{id}/people/bulk unless you explicitly add them.

Livestorm

Name: Livestorm API
Brand: Livestorm
Availability: InStock

Official vendor OpenAPI document · agent-readyCommunicationsVideo ConferencingapiKey, oauth240 EndpointsREST

For Agents

Schedule webinars and meetings, register participants, retrieve engagement data, and subscribe to webhooks - through one API.

Use for: Schedule a new webinar session for next Tuesday, Register 200 attendees for an upcoming session in bulk, Retrieve the attendee list for last week's webinar, Tag a recurring event with 'product-launch'

Not supported: Does not handle email marketing, payment processing, or general-purpose video calls - use for managing webinar events, sessions, registrants, and webhooks only.

Livestorm is a webinar and meeting platform whose v1 API exposes events (the campaign or topic), sessions (individual instances of an event), people (registrants and attendees), webhooks for outbound notifications, and supporting workspace endpoints. Agents can create events, schedule sessions, register participants in bulk, retrieve engagement data, manage webhook subscriptions, and read organization and tag metadata. Authentication supports both API key and OAuth 2.0 for first-party and partner integrations.

Jentic One on Github View OpenAPI Document

Connect the Livestorm to your agent

Capabilities

Start building with Livestorm API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Livestorm