HubSpot Meetings

Name: HubSpot Meetings API
Brand: HubSpot Meetings
Availability: InStock

✓ Official Vendor SpecProductivityCalendar Schedulingoauth2,apiKey4 EndpointsREST

Install Jentic One Beta

Connect the HubSpot Meetings to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HubSpot Meetings, 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 HubSpot Meetings API.

List every meeting link published by users on a HubSpot portal

Retrieve the rendered availability page for a meeting link by slug

Look up a specific meeting link's booking page metadata before scheduling

GET STARTED

Start building with HubSpot Meetings API

Explore with Jentic

View OpenAPI Document

For Agents

List HubSpot scheduler meeting links, read their availability windows, and book a meeting slot on behalf of a contact.

Use for: I need to book a meeting with a HubSpot sales rep, List the meeting links available on this HubSpot account, Find the next open slot on a specific HubSpot meeting link, Schedule a discovery call on the AE's HubSpot link

Not supported: Does not create meeting link configurations, manage rep availability rules, or send calendar invites outside HubSpot - use for listing links and booking slots only.

Use Cases

Patterns agents use HubSpot Meetings API for, with concrete tasks.

★ Embedded scheduling in a custom app

Surface a sales rep's HubSpot meeting calendar inside a custom product or onboarding flow without iframing the HubSpot widget. The API returns the available time blocks for a given meeting slug so the app can render its own picker UI, then submits the booking back to HubSpot which logs the meeting against the matched CRM contact.

GET /scheduler/v3/meetings/meeting-links/book/availability-page/{slug} for the AE's slug, surface open slots to the user, then POST /scheduler/v3/meetings/meeting-links/book with the chosen start time and contact email.

Lead routing to the right rep's calendar

Match an inbound lead to the right account executive based on territory or product line and book the discovery call directly on that AE's HubSpot meeting link. Because the booking uses the rep's published slug, the meeting lands on their calendar with HubSpot's standard reminder and rescheduling flow already attached.

List meeting links via GET /scheduler/v3/meetings/meeting-links, filter to the matched AE's slug, then POST /scheduler/v3/meetings/meeting-links/book with the lead's email and chosen 30-minute slot.

Calendar availability sync for chatbots

Give a website chatbot or AI assistant the ability to answer 'when can I meet with sales' by reading the live availability of the relevant HubSpot meeting link. The chatbot calls the availability page endpoint, parses the next open windows, and offers them inline in the conversation rather than handing off to a separate booking page.

Fetch GET /scheduler/v3/meetings/meeting-links/book/availability-page/{slug}, extract the next three open slots, and present them in the chat for the user to confirm.

Agent-driven meeting booking through Jentic

An AI agent receives a request like 'book a 30-minute call with Maria next Tuesday afternoon', uses Jentic to find the HubSpot Meetings booking operation, and executes the booking with the contact's email pre-filled. Jentic injects the HubSpot OAuth token so the agent never sees the raw credential.

Through Jentic, search for 'book a HubSpot meeting', load the schema for POST /scheduler/v3/meetings/meeting-links/book, and execute it with slug='maria-discovery', startTime, and the contact email.

Key Endpoints

4 endpoints — the hubspot meetings api exposes the public-facing meeting links that sales reps and customer success managers publish through the hubspot sales scheduler.

METHOD

PATH

DESCRIPTION

GET

/scheduler/v3/meetings/meeting-links

List all meeting links on the portal

GET

/scheduler/v3/meetings/meeting-links/book/{slug}

Fetch the booking page for a specific meeting link

GET

/scheduler/v3/meetings/meeting-links/book/availability-page/{slug}

Get the rendered availability windows for a meeting link

POST

/scheduler/v3/meetings/meeting-links/book

Book a meeting on a published link

GET

/scheduler/v3/meetings/meeting-links

List all meeting links on the portal

GET

/scheduler/v3/meetings/meeting-links/book/{slug}

Fetch the booking page for a specific meeting link

GET

/scheduler/v3/meetings/meeting-links/book/availability-page/{slug}

Get the rendered availability windows for a meeting link

POST

/scheduler/v3/meetings/meeting-links/book

Book a meeting on a published link

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your HubSpot OAuth or private-app token 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 'book a HubSpot meeting' or 'get HubSpot meeting availability', and Jentic returns the matching scheduler operation with its input schema so the agent calls the right endpoint without browsing the HubSpot reference docs.

Time to first call

FAQs

Specific to using HubSpot Meetings API through Jentic.

What authentication does the HubSpot Meetings API use?

It accepts HubSpot OAuth 2.0 access tokens and private-app tokens passed as a Bearer header. Through Jentic the credential lives in your encrypted Jentic One instance and is injected at execution time so the agent never sees it.

Can I book a meeting on someone else's HubSpot meeting link?

Yes - POST /scheduler/v3/meetings/meeting-links/book takes the public slug of the meeting link plus the desired start time, and the booking is logged on the slug owner's HubSpot calendar without the booker needing to be in the same portal.

What are the rate limits for the HubSpot Meetings API?

It is governed by HubSpot's standard public API limits: 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for private apps, plus a per-portal daily request budget that varies by Hub tier.

How do I find available time slots through Jentic?

Search Jentic for 'get HubSpot meeting availability', load the schema for GET /scheduler/v3/meetings/meeting-links/book/availability-page/{slug}, and execute it with the rep's slug. Jentic returns the parsed availability windows as JSON.

Does this API let me create new meeting links?

No. Creation, configuration, and team assignment of meeting links happen inside the HubSpot UI. This API only lists existing links, reads availability, and books slots on them.

Is the booking attached to the right contact in HubSpot CRM?

Yes. When the booking payload includes an email that matches an existing HubSpot contact, the meeting engagement is associated with that contact record automatically. New emails create a contact under the meeting owner's portal.

Can I limit what my agent is allowed to do with the HubSpot Meetings API?

Yes. Jentic One is self-hosted by you, so your own rules decide which HubSpot Meetings operations your agent may call and which credential it uses. Because the meeting-link slug sits in the URL path, you can pin the agent to a single link and let it only list links and read availability while withholding the POST that books a slot. Booking is enabled only when you explicitly add that operation to the agent's allowed set.