canonical: https://jentic.com/apis/on24.com/on24

# ON24 REST API

The ON24 REST API exposes programmatic control of the ON24 webinar and virtual event platform. It covers the full webinar lifecycle: creating, editing, copying, and deleting events, managing speakers, slides, surveys, and related content, configuring email notifications and reminders, and handling registration. Analytics endpoints return event-level and client-level engagement data, and helper endpoints support content listings and media uploads.

## For AI agents

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

## Scope

Does not handle live video streaming infrastructure, payment processing, or CRM contact storage - use for ON24 webinar lifecycle, registration, and analytics only.

## Capabilities

- Create, edit, copy, and delete webinars under a client account
- Register attendees and update registrant records at event level
- Upload slide decks, documents, and videos into the event media manager
- Configure email notifications, calendar reminders, and event widgets
- Build survey questions and answers tied to a specific webinar
- Pull event-level and client-level engagement analytics for reporting
- Manage speaker bios and related content displayed during a webinar

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 | Register an attendee for an event |
| 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 |

## Key resources

- **Event Management** — Create, edit, copy, and delete webinars under a client
- **Registration** — Register, update, and list attendees for an event
- **Content Listings** — Upload slides, documents, and videos into the media manager
- **Analytics - Event Level** — Engagement and attendance metrics for a single event
- **Analytics - Client Level** — Roll-up engagement data across the client account

## Why Jentic

- **Setup:** Wiring the ON24 REST API by hand means managing its access token, threading the client id through every path, and building calls across 66 endpoints against api.on24.com/v2 yourself. Through Jentic you install once, import the ON24 REST API from the API Directory, store the access token once, and your agent calls it.
- **Permission scoping:** ON24 puts the client id and event id in the URL path (/client/{clientId}/event/{eventId}/...), so a rule can pin your agent to one client or one event: it can manage registrants and slides for that event and nothing else. You choose the operations it may call, so creating new events or copying events are not included unless you add them.
- **Credential handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Zoom Meetings API** — Zoom covers meetings and webinars with broader video calling features.
- **Webex API** — Webex offers webinars, events, and meetings with deep enterprise integrations.
- **Mailchimp API** — Mailchimp can drive registration emails and post-event nurture flows alongside ON24 webinars.

## FAQ

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