HubSpot Video Conferencing Extension
Browse all Hubspot APIs42
AI ReadinessFoundational (D-)42/100
Official vendor OpenAPI document · agent-readyCommunicationsVideo ConferencingapiKey3 EndpointsREST
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.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-crm-video-conferencing-extension" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-crm-video-conferencing-extension" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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}
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
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
/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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
V
Video Conferencing Extension
- Foundational (D-)42/100
74
Foundational Compliance71
Developer Experience & Jentic Compatibility35
AI-Readiness & Agent Experience94
Agent Usability15
Security50
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
95%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
71
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
34%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
35
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
64%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
75%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
50
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
50%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Video Conferencing Extension API through Jentic.
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.
GET STARTED