canonical: https://jentic.com/apis/dev.clickmeeting.com/clickmeeting

# Dev Clickmeeting ClickMeeting API

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.

## For AI agents

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

## Scope

Does not handle persistent team chat, telephony, or screen recording outside of conference sessions - use for webinar and meeting scheduling only.

## Capabilities

- 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
- Manage registrations and pull session attendee lists for a conference
- Send branded invitation emails to a contact list in a chosen language
- Generate post-event PDF reports for a session

## Use cases

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

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

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

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

Example prompt: 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 your Jentic One instance, so the agent only needs intents like 'create a webinar for next Tuesday' to drive the full workflow.

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

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

## Key resources

- **Conferences** — Create, update, and list meetings and webinars
- **Sessions** — Per-conference session histories and attendee data
- **Tokens** — Per-user access tokens and autologin hashes
- **Contacts** — Manage the contact list used for invitations
- **Registrations** — Manage and read conference registrations

## Why Jentic

- **Setup:** Wiring the ClickMeeting API by hand means learning its API key header and building the conference creation, token, invitation, session, and contact calls yourself. Through Jentic you install once, import the ClickMeeting API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** ClickMeeting puts the room id in the URL path (`/conferences/{room_id}/...`), so a rule can pin your agent to one conference room: it can issue tokens, send invitations, and read that room's sessions and nothing else. You choose the operations it may call, so creating or editing conferences is not included unless you add those operations.
- **Credential handling:** Your ClickMeeting API key is stored once, encrypted, by your own Jentic One instance and injected into the request header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a ClickMeeting webinar' or 'list session attendees', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the docs.

## Related APIs

- **Zoom Meetings API** — Zoom Meetings is a competing video conferencing API with broader market reach.
- **Webex API** — Webex covers meetings, webinars, and team messaging in a single API surface.
- **SendGrid Mail API** — Use SendGrid for branded invitation emails alongside ClickMeeting's room and token management.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

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

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

Yes. Jentic One runs self-hosted, so your own rules decide which ClickMeeting operations and credentials the agent may use. Because ClickMeeting puts the room ID in the URL path (`/conferences/{room_id}/...`), you can pin the agent to a single conference room so it only issues tokens, sends invitations, and reads that room's sessions and attendees. You pick the operations it may call, so creating or editing conferences stays off unless you explicitly add those operations.