ON24 REST API

Name: ON24 REST API 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.

Quickstart

Get started with ON24 REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an on24 webinar"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with ON24 REST API API.

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

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

GET STARTED

Start building with ON24 REST API API

Explore with Jentic

View OpenAPI Document

Use for: I want to create a new ON24 webinar for next month, Register a list of attendees for an upcoming event, Upload a slide deck to an existing webinar, Retrieve engagement analytics for last week's webinar

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

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.

Use Cases

Patterns agents use ON24 REST API 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 though Jentic?

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

Credential isolation

ON24 access tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped reference rather than the raw token, so credentials never leak into prompts.

Intent-based discovery

Agents search by intent (e.g. 'create on24 webinar') and Jentic returns the matching operation with its input schema, so the agent can call the right endpoint without browsing 66 paths.

Time to first call

Direct integration: 3-5 days to implement auth, lifecycle management, and analytics polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Zoom Meetings API

Zoom covers meetings and webinars with broader video calling features.

Choose Zoom when the use case is general meetings or smaller webinars rather than enterprise marketing events.

Alternative

Webex API

Webex offers webinars, events, and meetings with deep enterprise integrations.

Pick Webex when the customer is already standardised on Cisco collaboration tooling.

Complementary

Mailchimp API

Mailchimp can drive registration emails and post-event nurture flows alongside ON24 webinars.

Use Mailchimp to send promotional and follow-up campaigns tied to ON24 registration data.

FAQs

Specific to using ON24 REST API 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.