ClickMeeting API

Name: ClickMeeting API API
Brand: ClickMeeting API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVideo ConferencingapiKey22 EndpointsREST

For Agents

Schedule meetings and webinars, manage registrations, generate join tokens, and pull session and attendee data through the ClickMeeting REST API.

Connect the ClickMeeting API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 ClickMeeting API API.

Create and schedule meetings or webinars in ClickMeeting

List active, upcoming, or finished conferences by status

Update or delete a specific conference by room ID

Generate per-user access tokens to give individual attendees a join link

GET STARTED

Start building with ClickMeeting API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ClickMeeting API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ClickMeeting API, keeping it validated and agent-ready. ClickMeeting is a webinar and meeting platform used for marketing webinars, training sessions, and online events. The REST API exposes conference creation, session listings, registrations, contacts, and access tokens, so external systems can schedule meetings, sync attendees back into a CRM, and generate per-user join links without using the ClickMeeting UI.

Use Cases

Patterns agents use ClickMeeting API API for, with concrete tasks.

★ Webinar Scheduling from a Marketing Stack

Marketing operations teams schedule webinars from their campaign tooling instead of the ClickMeeting UI. POST /conferences creates the room with title, time, and access settings; the response includes the room ID used by every other call. This makes webinar creation reliable and auditable inside the campaign workflow.

POST /conferences with the webinar title, start time, and access type, then store the returned room ID against the campaign record.

Per-Attendee Join Links

Conferences with paid or gated access need unique join links per attendee. The /conferences/{room_id}/tokens endpoints generate per-user tokens, while /conferences/{room_id}/room/autologin_hash supports auto-login flows. Together these let external systems hand each registered attendee a personalised join URL without exposing a shared link.

POST /conferences/{room_id}/tokens for each registered attendee and email them their unique join URL.

Registration and Attendee Sync

Marketing and CRM teams sync ClickMeeting registrations and post-session attendance back into their CRM to score leads. /conferences/{room_id}/registrations returns the registration list, while /conferences/{room_id}/sessions/{session_id}/attendees returns who actually attended. Most teams reconcile both into a single attendance record per contact.

Call GET /conferences/{room_id}/sessions to get the session ID, then GET /conferences/{room_id}/sessions/{session_id}/attendees and upsert each attendee into the CRM with an attended flag.

Multilingual Invitation Workflow

Teams running webinars across regions use POST /conferences/{room_id}/invitation/email/{lang} to send branded invitations in a specific language. Combined with POST /contacts to seed the contact list, this avoids juggling separate email tools for the invite step.

POST /contacts with a list of recipient emails, then POST /conferences/{room_id}/invitation/email/de to send German invitations to the contact list.

Agent-Driven Webinar Operations

AI agents help marketing ops teams schedule webinars, send invitations, and pull attendance reports through Jentic. The ClickMeeting API key sits in the Jentic vault, so the agent only needs intents like 'create a webinar for next Tuesday' to drive the full workflow.

Search Jentic for 'create a ClickMeeting webinar', load the POST /conferences operation, and execute it with the title and time pulled from a calendar event.

Key Endpoints

22 endpoints — jentic publishes the only available openapi specification for clickmeeting api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/conferences/{status}

List conferences filtered by status

POST

/conferences

Create a new meeting or webinar

PUT

/conferences/{room_id}

Update an existing conference

POST

/conferences/{room_id}/tokens

Generate per-user access tokens

POST

/conferences/{room_id}/invitation/email/{lang}

Send invitation emails in a chosen language

GET

/conferences/{room_id}/sessions

List sessions for a conference

GET

/conferences/{room_id}/sessions/{session_id}/attendees

List attendees for a specific session

POST

/contacts

Add contacts to the invitation list

GET

/conferences/{status}

List conferences filtered by status

POST

/conferences

Create a new meeting or webinar

PUT

/conferences/{room_id}

Update an existing conference

POST

/conferences/{room_id}/tokens

Generate per-user access tokens

POST

/conferences/{room_id}/invitation/email/{lang}

Send invitation emails in a chosen language

Why though Jentic?

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

Credential isolation

The ClickMeeting API key is held encrypted in the Jentic vault. Agents call ClickMeeting through Jentic and never see the raw key — the apiKeyAuth header is injected at execution time.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a ClickMeeting webinar' or 'list session attendees') and Jentic returns the matching operation with its input schema.

Time to first call

Direct ClickMeeting integration: 1-2 days for auth, conference lifecycle, and attendee sync. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Zoom Meetings API

Zoom Meetings is a competing video conferencing API with broader market reach.

Choose Zoom when the audience already lives in Zoom; choose ClickMeeting when the workflow is webinar-led with built-in registration and invitation tooling.

Alternative

Webex API

Webex covers meetings, webinars, and team messaging in a single API surface.

Choose Webex when the organisation is standardised on Cisco collaboration; choose ClickMeeting for webinar-first workflows.

Complementary

SendGrid Mail API

Use SendGrid for branded invitation emails alongside ClickMeeting's room and token management.

Use SendGrid when you need richer email templates and deliverability than ClickMeeting's invitation endpoint provides.

FAQs

Specific to using ClickMeeting API API through Jentic.

Why is there no official OpenAPI spec for ClickMeeting API?

ClickMeeting does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ClickMeeting API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ClickMeeting API use?

ClickMeeting uses an API key passed in a request header (apiKeyAuth scheme). Through Jentic the key is stored encrypted in the vault and injected at execution so the raw value never enters agent context.

Can I create a webinar with the ClickMeeting API?

Yes — POST /conferences creates a meeting or webinar with title, start time, and access type. The response returns a room ID used for tokens, registrations, and session lookups.

How do I send personalised invitation links with the ClickMeeting API?

Use POST /conferences/{room_id}/tokens to generate per-user access tokens, then deliver each token as part of a join URL to the corresponding attendee. For autologin, also use POST /conferences/{room_id}/room/autologin_hash.

What are the rate limits for the ClickMeeting API?

The OpenAPI spec does not declare specific rate limits. For high-volume token or invitation workflows, batch calls and implement exponential backoff on 429 responses.

How do I pull session attendees through Jentic?

Search Jentic for 'list ClickMeeting session attendees', load the GET /conferences/{room_id}/sessions/{session_id}/attendees operation, and execute it with the room and session IDs. Jentic injects the API key at execution.