The problem
▎ Meetings booked through the public Scheduler v3 API (POST /scheduler/v3/meetings/meeting-links/book) never get native Google Meet conferencing on the resulting Google Calendar event — only a plain text link pasted into the location/description. Because of this, features that rely on native conferencing (like the AI Notetaker) never work on API-booked meetings, even though the booking itself is otherwise correct (right contact, right time, a real webConferenceUrl in the response).
▎
▎ Proof it’s not a config issue
▎ We compared meetings booked via the API against meetings booked manually through the exact same scheduling link (same account, same Google Meet location preset). The manual ones get full native conferencing; the API ones never do. We also tried fixing an existing API-booked event after the fact (via the Google Calendar API, both attaching an existing Meet link and requesting a new one) — neither works. Native conferencing seems to only be creatable at the moment an event is created, not applied afterward.
▎
▎ Evidence HubSpot already supports this internally
▎ Inspecting the network requests made by the actual public booking page, it calls a different, undocumented endpoint (POST https://api-na2.hubspot.com/meetings-public/v1/book) — not the documented /scheduler/v3/… API. That internal endpoint clearly knows how to create native conferencing; the public API just doesn’t expose the same capability.
▎
▎ The ask
▎ Please add support for native Google Meet (and other conferencing providers) conferencing when booking meetings through the public Scheduler v3 API — matching the behavior of the booking page widget. This would let integrations that book meetings programmatically (like ours) work correctly with AI Notetaker and any other feature that depends on real calendar conferencing data.