GoToMeeting

Name: GoToMeeting API
Brand: GoToMeeting
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVideo Conferencingnone26 EndpointsREST

For Agents

Provision GoToMeeting organizers, schedule and update meetings, and pull historical or upcoming meeting data so an agent can manage a Corporate account programmatically.

Connect the GoToMeeting to your agent

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

Create, update, or delete a GoToMeeting meeting on behalf of an organizer

Provision a new organizer in a Corporate account or remove one when an employee leaves

List upcoming meetings for an organizer or group for calendar sync

Pull historical meeting records and attendee lists for reporting

GET STARTED

Start building with GoToMeeting API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for GoToMeeting, keeping it validated and agent-ready. The GoToMeeting API integrates GoToMeeting provisioning and meeting management into existing systems, so admins can add, suspend, or delete organizers and applications can create, update, or delete meetings on behalf of users. It exposes 26 endpoints across organizers, groups, meetings, and historical meeting data. The API is the supported route for syncing GoToMeeting Corporate accounts with internal directories and for embedding scheduled or ad-hoc meetings into third-party scheduling and CRM tools.

Use Cases

Patterns agents use GoToMeeting API for, with concrete tasks.

★ Calendar-to-GoToMeeting scheduling integration

When a user creates an event in a corporate calendar tool, the integration calls POST /meetings to schedule the GoToMeeting and writes the join URL back into the calendar invite. Updates to the calendar event flow through PUT /meetings/{meetingId}, and deletes call DELETE /meetings/{meetingId} to keep the two systems in sync.

Call POST /meetings with subject, starttime, endtime, and passwordrequired flags, then write the returned join URL into the calendar event.

HR-driven organizer provisioning

When HR onboards a new employee, the directory tool calls POST /organizers to create a GoToMeeting organizer for the employee's email, and DELETE /organizers/{organizerKey} when they leave. This removes the manual admin step in the GoToMeeting console and keeps Corporate licence usage aligned with the employee directory.

Call POST /organizers with the new hire's email, firstname, lastname, and groupKey, then store the returned organizerKey on the employee record.

Meeting attendance reporting

Operations teams pull /historicalMeetings and /meetings/{meetingId}/attendees to build attendance reports — total minutes attended, drop-off times, and attendee email lists. This feeds into engagement dashboards and licence-utilisation reviews without exporting CSVs from the GoToMeeting console.

Call GET /historicalMeetings for the past 30 days, then for each meetingId call GET /meetings/{meetingId}/attendees to build a per-meeting attendance roll.

AI agent meeting scheduling via Jentic

An AI assistant connected through Jentic accepts a natural-language scheduling request, searches Jentic for 'schedule a video meeting in GoToMeeting', loads the schema for POST /meetings, and creates the meeting. The join URL is returned to the user along with a calendar invite — the agent never sees the underlying API credential.

Through Jentic, search 'schedule a GoToMeeting', load the schema for POST /meetings, and execute it with subject, starttime, and endtime extracted from the user's request.

Key Endpoints

26 endpoints — jentic publishes the only available openapi specification for gotomeeting, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/meetings

Create a meeting

GET

/meetings/{meetingId}

Get a meeting

PUT

/meetings/{meetingId}

Update a meeting

DELETE

/meetings/{meetingId}

Delete a meeting

GET

/meetings/{meetingId}/attendees

Get attendees for a meeting

POST

/organizers

Create an organizer

GET

/historicalMeetings

List historical meetings

GET

/groups/{groupKey}/upcomingMeetings

Get upcoming meetings by group

POST

/meetings

Create a meeting

GET

/meetings/{meetingId}

Get a meeting

PUT

/meetings/{meetingId}

Update a meeting

DELETE

/meetings/{meetingId}

Delete a meeting

GET

/meetings/{meetingId}/attendees

Get attendees for a meeting

POST

Why though Jentic?

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

Credential isolation

GoToMeeting OAuth access and refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Jentic refreshes tokens on schedule and injects the bearer header at execution — the raw token never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'schedule a GoToMeeting') and Jentic returns the matching operation with its input schema, so the agent calls POST /meetings without parsing the developer portal.

Time to first call

Direct GoToMeeting integration: 1-2 days for OAuth handshake, token refresh handling, and meeting CRUD wiring. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Zoom API

Larger video conferencing platform with overlapping meeting and user provisioning endpoints

Choose Zoom when the team is on Zoom rather than GoToMeeting, or when webinar features are required.

Complementary

Google Calendar API

Calendar layer that holds the events for which GoToMeetings are created

Use Google Calendar to find or create the calendar event that the GoToMeeting join URL is attached to.

Complementary

Microsoft Teams Events API

Source of Outlook calendar events and Microsoft 365 user identity for organizer provisioning

Use Microsoft Graph when GoToMeeting organizers must be kept in sync with Microsoft 365 user accounts.

FAQs

Specific to using GoToMeeting API through Jentic.

Why is there no official OpenAPI spec for GoToMeeting?

GoToMeeting does not publish an OpenAPI specification on the developer portal. Jentic generates and maintains this spec so that AI agents and developers can call GoToMeeting 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 GoToMeeting API use?

GoToMeeting uses OAuth 2.0 access tokens issued via the Citrix/LogMeIn developer portal. The OpenAPI spec does not declare an inline security scheme, but production calls require an Authorization: Bearer access token. Through Jentic, the token and refresh credentials are held in the MAXsystem vault.

Can I create a GoToMeeting meeting through the API?

Yes. POST /meetings creates a meeting with the subject, starttime, endtime, password requirement, and meeting type, and returns the meetingId and join URL. PUT /meetings/{meetingId} updates the meeting and DELETE /meetings/{meetingId} cancels it.

Can I provision and remove organizers in a Corporate account?

Yes. POST /organizers creates an organizer for a new user, GET /organizers retrieves them by email, and DELETE /organizers/{organizerKey} removes them. This is the supported way to keep GoToMeeting Corporate licences aligned with the employee directory.

What are the rate limits for the GoToMeeting API?

The OpenAPI spec does not declare rate limits. Citrix enforces them at the application and account level — for production usage, add retry-with-backoff on 429 responses and prefer batched group endpoints (for example /groups/{groupKey}/upcomingMeetings) over per-organizer loops.

How do I schedule a GoToMeeting from an AI agent through Jentic?

Run pip install jentic, then have the agent search 'schedule a GoToMeeting', load the schema for POST /meetings, and execute it with subject, starttime, and endtime. Jentic resolves the OAuth token from the vault and returns the meetingId and join URL to the agent.