Meetings (BETA)
Use the meetings API to retrieve information about meetings created through a scheduling page. You can also book a meeting with a scheduling page through the API.
Learn more about using the API to create, update, and delete all types of meeting engagements.
With the meetings API, you can:
- Get a list of meeting links.
- Get booking information for a meeting link.
- Get the next availability page for a meeting link.
This could be useful if you have an app that can get a list of meeting links or book meetings. You could also use the meetings API to create an interface for your customers to book meetings with your team.
The following features aren’t supported when using the Meetings API:
- UTM, HubSpot UTK, and content tracking.
- Reschedule through this API.
- Send in CAPTCHA tokens.
- Create meetings with payment.
- Send in an IP address.
The sections below provides a walkthrough of how to use the v3 endpoints. For a full reference of the available endpoints and their required fields, click the Endpoints tab at the top of this article.
To get a list of meetings scheduling pages, make a GET request to /scheduler/v3/meetings/meeting-links. Use the amount of meeting links you want returned as the limit in the request URL and use your userID, name, and type as a query parameter.
To get and filter a list of meeting links, supply the filters you’d like to apply as query parameters (e.g., limit, type, and name), and provide your user ID as the organizerUserId query parameter. For example, if your user ID is 1234567, you’d make a GET request to /scheduler/v3/meetings/meeting-links?limit=1&name=menelson&organzerUserId=1234567&type=PERSONAL_LINK
The response for fetching a list of meeting scheduling pages would resemble the following:
The details of each response field are outlined in the table below:
| Field | Description |
|---|---|
id
| The ID of the activity. |
slug
| The end of the meeting link’s URL. |
link
| The full meeting URL. |
name
| The title of the meeting. |
type
| Indicates if the meeting is a one-on-one ( |
organizerUserId
| The user ID of the user who organized the meeting. |
userIdsOfLinkMembers
| The user IDs of the meeting link owner. |
defaultLink
| Indicates if the meeting is the user’s default meeting link. |
To get details about the initial information necessary for a meeting scheduler, make a GET request to /scheduler/v3/meetings/meeting-links/book/{slug}. Use your meeting link path as the slug and use your timezone as a query parameter.
For example, to get details about initial information necessary for meeting scheduler, make a GET request to /scheduler/v3/meetings/meeting-links/book/menelson&timezone=America%2FNew_York.
The response for fetching booking information would resemble the following:
The details of each response field are outlined in the table below:
To get the next availability page for a meeting, make a GET request to /scheduler/v3/meetings/meeting-links/book/availability-page/{slug}. Use your meeting link path as the slug and your timezone as a query parameter.
For example, to get make a the next availability page for a meeting, make a GET request to https://api.hubspot.com/scheduler/v3/meetings/meeting-links/book/menelson&timezone=America%2FNew_YorkThe response for fetching the availability page for a meeting would resemble the following:
To book a meeting using a meeting link, make a POST request to /scheduler/v3/meetings/meeting-links/book/{slug}. Use your meeting link path as the slug and your timezone as a query parameter.
For example to book a meeting, make a POST request to /scheduler/v3/meetings/meeting-links/book?timezone=America%2FNew_YorkThe request body should include the following information. Any information that's required in your meeting registration must be included in the request body:
Thank you for your feedback, it means a lot to us.