ON24 REST API

Name: ON24 REST API
Brand: ON24 REST API
Availability: InStock

✓ Official Vendor SpecCommunicationsVideo ConferencingapiKey66 EndpointsREST

For Agents

Create and manage ON24 webinars, register attendees, upload slides and media, and pull engagement analytics across events.

Install Jentic One Beta

Connect the ON24 REST API to your agent

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

Create, edit, copy, and delete webinars under a client account

Upload slide decks, documents, and videos into the event media manager

GET STARTED

Start building with ON24 REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ON24 REST API for, with concrete tasks.

★ Webinar Lifecycle Automation

Spin up recurring webinar series programmatically by creating events, copying templates, and updating schedules without using the ON24 console. POST /client/{clientId}/event creates a webinar; POST /client/{clientId}/event/{eventId}/copy clones it for the next instance; PUT and DELETE handle ongoing edits.

Create a webinar titled 'Q3 Product Update' under client 12345 for 2026-07-15 14:00 UTC and copy it to schedule the same content for 2026-07-22.

Bulk Registration and Reminder Management

Sync registrations from a CRM into ON24 and keep email reminders aligned with event timing. POST /client/{clientId}/event/{eventId}/registrant adds attendees, PUT updates them, and PUT /client/{clientId}/event/{eventId}/emailcalendarreminder keeps reminder windows consistent across the campaign.

Register 50 attendees from a CSV to event 9876 under client 12345 and set the calendar reminder to 24 hours before start.

Post-Event Analytics Reporting

Pull attendance, engagement, and content interaction data after each webinar to build reports outside the ON24 console. Event-level analytics endpoints return per-event metrics; client-level analytics roll up activity across the account for executive dashboards.

Fetch event-level analytics for event 9876 including registration counts, attendance rate, and average viewing duration.

Agent-Run Webinar Operations via Jentic

Marketing agents create webinars, register attendees, and pull engagement metrics through Jentic without ever holding the ON24 access token. The agent searches for the operation, loads its schema, and executes with parameters from upstream marketing tools.

Use Jentic search 'create on24 webinar' to find POST /client/{clientId}/event, load the schema, and execute with the campaign's title and start time.

Key Endpoints

66 endpoints — the on24 rest api exposes programmatic control of the on24 webinar and virtual event platform.

METHOD

PATH

DESCRIPTION

POST

/client/{clientId}/event

Create a new webinar

GET

/client/{clientId}/event

List webinars under the client

POST

/client/{clientId}/event/{eventId}/registrant

POST

/client/{clientId}/event/{eventId}/slide

Upload slides to an event

POST

/client/{clientId}/event/{eventId}/copy

Copy an existing webinar

POST

/client/{clientId}/event/{eventId}/survey

Create survey questions and answers

PUT

/client/{clientId}/event/{eventId}/emailnotification

Update event email notification

POST

/client/{clientId}/event

Create a new webinar

GET

/client/{clientId}/event

List webinars under the client

POST

/client/{clientId}/event/{eventId}/registrant

POST

/client/{clientId}/event/{eventId}/slide

Upload slides to an event

POST

/client/{clientId}/event/{eventId}/copy

Copy an existing webinar

Why Jentic?

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

Credential isolation

Your ON24 access token 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 an on24 webinar' or 'register an attendee', and Jentic returns the matching ON24 operation with its input schema so the agent calls the right endpoint without browsing all 66 paths.

Time to first call

FAQs

Specific to using ON24 REST API through Jentic.

What authentication does the ON24 REST API use?

The API uses an access token passed as an apiKey credential. Jentic stores the token encrypted in the vault and the agent only ever holds a scoped reference, so the raw token never enters prompts or logs.

Can I create webinars programmatically with the ON24 REST API?

Yes. POST /client/{clientId}/event creates a webinar; PUT, DELETE, and POST /copy on the same resource cover the rest of the lifecycle. Speakers, slides, surveys, and reminders each have dedicated sub-resources.

How do I register attendees through the ON24 API?

POST /client/{clientId}/event/{eventId}/registrant adds a registrant; PUT on the same path updates them. GET on the registrant collection returns the existing list for reconciliation against a CRM.

What analytics does the ON24 REST API expose?

Two analytics tiers are available: event-level metrics for a single webinar (attendance, engagement, content interactions) and client-level rollups for cross-event reporting.

What are the rate limits for the ON24 REST API?

Rate limits are not declared in this OpenAPI spec. Consult apidoc.on24.com for current per-token limits before driving heavy bulk-registration traffic.

How do I pull event analytics through Jentic?

Search Jentic for 'on24 event analytics', load the schema for the matching analytics endpoint under /client/{clientId}/event/{eventId}, and execute with the event id. Jentic returns the parsed JSON for downstream reporting.

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

Yes. Because your Jentic One instance is self-hosted, your own rules decide which ON24 operations and credentials the agent may use. Since ON24 puts the client id and event id in the URL path (/client/{clientId}/event/{eventId}/...), you can pin the agent to a single client or event so it only manages registrants and slides for that event and nothing else. You choose the operations it may call, so creating new events or copying events with POST /client/{clientId}/event/{eventId}/copy are excluded unless you add them.

ON24 REST API

Connect the ON24 REST API to your agent

Capabilities

Start building with ON24 REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs