canonical: https://jentic.com/apis/hubspot.com/hubspot-crm-video-conferencing-extension

# HubSpot Video Conferencing Extension

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.

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

## Scope

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.

## Capabilities

- 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}
- Allow HubSpot meetings to auto-attach video conference links from the integrating provider
- Update the create, update, or delete callback URLs as the integrating service evolves
- Inspect the existing extension configuration to verify it points at the right service
- Disable the integration cleanly when the customer uninstalls the app

## Use cases

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

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

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

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

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

| Method | Path | Description |
| --- | --- | --- |
| PUT | /crm/v3/extensions/videoconferencing/settings/{appId} | Register or update the video conferencing URLs |
| GET | /crm/v3/extensions/videoconferencing/settings/{appId} | Read the registered settings |
| DELETE | /crm/v3/extensions/videoconferencing/settings/{appId} | Remove the registered settings |

## Key resources

- **Settings** — Per-app video conferencing extension configuration: create, read, and delete the URLs HubSpot calls for meetings.

## Why Jentic

- **Setup:** Wiring HubSpot's Video Conferencing Extension by hand means passing its developer hapikey as a query parameter, targeting the api.hubapi.com host, and registering the webhook URLs HubSpot calls yourself. Through Jentic you install once, import HubSpot Video Conferencing Extension from the API Directory, store the hapikey once, and your agent calls it.
- **Permission scoping:** The extension puts the app id in the URL path (/crm/v3/extensions/videoconferencing/settings/{appId}), so a rule can pin your agent to one app's settings for reading and updating its webhook URLs. You choose the operations it may call, so deleting the settings is not included unless you add it.
- **Credential handling:** Your HubSpot developer hapikey is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'register a HubSpot video conferencing extension' or 'update the video link webhooks', and Jentic returns the matching Settings operation with its input schema so the agent configures the integration without browsing the reference docs.

## Related APIs

- **Zoom Meetings API** — Zoom Meetings API generates the actual conference rooms and links your webhooks return to HubSpot.
- **HubSpot Meetings** — The Meetings object stores the HubSpot-side meeting record this extension attaches video links to.
- **HubSpot Meetings Scheduler** — Scheduler links produce HubSpot meetings that automatically pick up the configured video conferencing extension.

## FAQ

### What authentication does the HubSpot Video Conferencing Extension API use?

It authenticates with a developer hapikey passed as the hapikey query parameter, scoped to the app account that owns the appId. Through Jentic the developer hapikey is stored encrypted in the vault and injected at execution time so the agent never holds the raw secret.

### Can I integrate any video provider through this extension API?

Yes - the API is provider-agnostic. You expose three webhook endpoints (create, update, delete) and HubSpot calls them when a meeting needs a video link. The actual link generation happens in your service, so any video provider you can wrap behind those webhooks works.

### What are the rate limits for the Video Conferencing Extension API?

HubSpot applies its standard public app rate limits (100 requests per 10 seconds per app, plus daily quotas). The extension endpoints are infrequent (settings change rarely) so rate limits rarely bind in practice - the heavier traffic is the webhook callbacks HubSpot makes to your service.

### How do I register webhook URLs through Jentic?

Search Jentic for 'register hubspot video conferencing extension', load PUT /crm/v3/extensions/videoconferencing/settings/{appId}, and execute it with createMeetingUrl, updateMeetingUrl, and deleteMeetingUrl. Jentic validates the input shape before sending the request.

### What happens to existing meeting links if I delete the extension settings?

Existing meeting links remain on HubSpot meeting records, but HubSpot stops calling your webhooks for new or updated meetings. The links continue to point at your service, so the underlying video rooms still work until your service tears them down independently.

### Can I have more than one video conferencing extension active per app?

No. Each appId has a single registered set of create/update/delete URLs. To switch providers you update the URLs in place via PUT /crm/v3/extensions/videoconferencing/settings/{appId} or delete and re-register them.

### Can I limit what my agent is allowed to do with the HubSpot Video Conferencing Extension API?

Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, so you can allow it to read (GET) and register or update (PUT) the webhook URLs at /crm/v3/extensions/videoconferencing/settings/{appId} while withholding the DELETE that removes the settings. Since the app id lives in the URL path, a rule can pin the agent to a single app's configuration, and the developer hapikey stays with your instance rather than the agent. The operator sets these boundaries, so the agent only touches the operations and app you have explicitly permitted.