HubSpot Video Conferencing Extension

Name: Video Conferencing Extension API
Brand: Video Conferencing Extension
Availability: InStock

✓ Official Vendor SpecCommunicationsVideo ConferencingapiKey3 Endpoints

Install Jentic One Beta

Connect the Video Conferencing Extension to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Video Conferencing Extension, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Video Conferencing Extension API.

Register the meeting URLs HubSpot should call for video conferencing via PUT /crm/v3/extensions/videoconferencing/settings/{appId}

Read the currently registered settings for the app with GET /crm/v3/extensions/videoconferencing/settings/{appId}

Remove the video conferencing extension settings with DELETE /crm/v3/extensions/videoconferencing/settings/{appId}

GET STARTED

Start building with Video Conferencing Extension API

Explore with Jentic

View OpenAPI Document

For Agents

Register the create, update, and delete URLs that HubSpot calls when a meeting needs a video conference link, so HubSpot meetings can auto-attach a conference URL from the integrating video provider.

Use for: I need to register a video conferencing extension for my HubSpot app, Update the create-meeting URL my app exposes to HubSpot, Read the current video conferencing extension settings for an app, Remove the video conferencing extension when an app is uninstalled

Not supported: Does not generate video meeting rooms, transcribe calls, or schedule meetings — use for registering the create, update, and delete webhook URLs HubSpot calls for video links only.

The HubSpot CRM Video Conferencing Extension API lets a public app register the URLs HubSpot uses to manage video conferencing on meeting requests with contacts. The app provides three URLs — create, update, and delete — that HubSpot calls when a meeting link needs to be generated, modified, or removed for a HubSpot meeting. Once configured, HubSpot adds the resulting video conference link to the meeting invitation automatically. The API exposes three endpoints to get, update, and delete the extension settings for a given appId.

Use Cases

Patterns agents use Video Conferencing Extension API for, with concrete tasks.

★ Adding Auto-Generated Video Links to HubSpot Meetings

Companies that use a video provider (Zoom, Google Meet, an in-house service) want HubSpot meeting invites to include a unique video link without users copying and pasting. By registering the create/update/delete URLs via PUT /crm/v3/extensions/videoconferencing/settings/{appId}, the integrating app receives a callback every time a HubSpot meeting needs a link. The app generates the link in its own system and returns the URL to HubSpot, which embeds it in the invite.

Call PUT /crm/v3/extensions/videoconferencing/settings/{appId} with createMeetingUrl, updateMeetingUrl, and deleteMeetingUrl pointing at the app's webhook endpoints.

Inspecting Extension Configuration During Support

When a HubSpot customer reports that meeting links are missing or stale, support engineers fetch the current extension configuration to verify the right URLs are registered. GET /crm/v3/extensions/videoconferencing/settings/{appId} returns the configured URLs so the engineer can confirm or repoint them. PUT on the same path corrects misconfigured URLs in place.

Call GET /crm/v3/extensions/videoconferencing/settings/{appId} for the affected app and compare returned URLs against the expected production values.

Clean Uninstall on Customer Off-Boarding

When a customer disables the video conferencing app, the extension settings should be removed so HubSpot stops calling the now-defunct webhooks. DELETE /crm/v3/extensions/videoconferencing/settings/{appId} clears the registration in one call. This avoids ghost calls to dead endpoints and keeps the customer's portal clean.

Call DELETE /crm/v3/extensions/videoconferencing/settings/{appId} when the uninstall event fires, then verify with GET that the settings are gone.

AI Agent Provisioning a Video Integration

An onboarding agent provisions a new HubSpot video integration end-to-end: it spins up the app's webhook endpoints, then calls the Video Conferencing Extension API to register them. Through Jentic the agent searches for the extension operations, loads the PUT schema, and executes it with the correct URLs. Jentic stores the developer hapikey in its vault so the agent only handles scoped execution tokens.

Search Jentic for 'register hubspot video conferencing extension', load PUT /crm/v3/extensions/videoconferencing/settings/{appId}, and execute it with the freshly deployed webhook URLs.

Key Endpoints

3 endpoints — the hubspot crm video conferencing extension api lets a public app register the urls hubspot uses to manage video conferencing on meeting requests with contacts.

METHOD

PATH

DESCRIPTION

PUT