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.