ClickMeeting
MESSAGING · CALENDAR
Webinar rooms, registrations, sessions, and recordings on their account.
Connecting ClickMeeting in practice
One API key per account, generated in Settings and sent as X-Api-Key, and the DevZone publishes no rate limit of any kind. The trap is retention rather than throughput: conference rooms inactive for more than six months are removed from the conferences list automatically and moved into a ClickMeeting database.
Worth knowing
- Rooms inactive for more than six months disappear from GET /v1/conferences, so an agent reconciling against its own store will read the absence as a deletion.
- The response format is chosen by file extension on the path — .xml, .js, .php, .printr — and omitting the extension silently gives you JSON, so a typo changes the parser’s input rather than erroring.
- Joining a room is a two-step dance: access tokens and the autologin hash are separate POST endpoints per conference, not query parameters on the room URL.
- Regenerating the API key in Settings invalidates the previous one immediately, and there is no second key to rotate through.
Checked against ClickMeeting API guide (2026-09-29), ClickMeeting API function reference (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put ClickMeeting behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.