Skip to main content

Use the meetings engagement API to log and manage meetings on CRM records. You can log meeting activities either in HubSpot or through the meetings API. You can retrieve, update, or delete meeting engagements that are manually logged on a record, scheduled using the meetings tool, or scheduled using the Google Calendar or Office 365 calendar integration.

Below, learn the basic methods of managing meetings through the API. To view all available endpoints and their requirements, check out the reference documentation.

To create a meeting engagement, make a POST request to /crm/v3/objects/meetings.

In the request body, add meeting details in a properties object. You can also add an associations object to associate your new meeting with an existing record (e.g., contacts, companies).

In the properties object, you can include the following fields:

FieldDescription
hs_timestampRequired. This field marks the date and time that the meeting occurred. You can use either a Unix timestamp in milliseconds or UTC format.(BETA) When the property value is missing, the value will default to hs_meeting_start_time.
hs_meeting_titleThe title of the meeting.
hubspot_owner_idThe ID of the owner associated with the meeting. This field determines the user listed as the meeting creator on the record timeline.
hs_meeting_bodyThe meeting description.
hs_internal_meeting_notesThe internal notes you take for your team during a meeting that are not included in the attendee meeting description.
hs_meeting_external_urlThe external URL for the calendar event. For example, this could be a Google calendar link or a Microsoft Outlook calendar link.
hs_meeting_locationWhere the meeting takes place. The value could be a physical address, a conference room, a videoconference link, or a phone number. This appears on the calendar invite on the attendee's calendar.
hs_meeting_start_timeThe date and time when the meeting starts. The value for this property should match the value for hs_timestamp.
hs_meeting_end_timeThe date and time when the meeting ends.
hs_meeting_outcomeThe outcome of the meeting. The outcome values are scheduled, completed, rescheduled, no show, and canceled.
hs_activity_typeThe type of meeting. The options are based on the meeting types set in your HubSpot account.
hs_attachment_idsThe IDs of the meeting's attachments. Multiple attachment IDs are separated by a semi-colon.

To create and associate a meeting with existing records, include an associations object in your request. For example, to create and associate a meeting with contacts, your request may look similar to the following:

The associations object should include:

FieldDescription
toThe record you want to associate with the meeting, specified by its unique id value.
typesThe type of the association between the meeting and the record. Include the associationCategoryand associationTypeId. Default association type IDs are listed here, or you can retrieve the value for custom association types (i.e. labels) via the associations API.

Learn more about batch creating meetings by checking out the reference documentation.

You can retrieve meetings individually or in bulk. Learn more about batch retrieval by checking out the reference documentation.

To retrieve an individual meeting by its meeting ID, make a GET request to /crm/v3/objects/meetings/{meetingId}. You can also include the following parameters in the request URL:

ParameterDescription
propertiesA comma separated list of the properties to be returned.
associationsA comma separated list of objects to you want to retrieve associated record IDs from.

To request a list of all of meetings, make a GET request to crm/v3/objects/meetings. You can include the following parameters in the request URL:

ParameterDescription
limitThe maximum number of results to display per page.
propertiesA comma separated list of the properties to be returned.

You can update meetings individually or in batches. To update an individual meeting by its meeting ID, make a PATCH request to /crm/v3/objects/meetings/{meetingId}.

In the request body, include the meeting properties that you want to update. For example, your request body might look similar to the following:

HubSpot will ignore values for read-only and non-existent properties. To clear a property value, pass an empty string for the property in the request body.

Learn more about batch updating by checking out the reference documentation.

To associate a meeting with records, such as a contact and its associated companies, make a PUT request to /crm/v3/objects/meetings/{meetingId}/associations/{toObjectType}/{toObjectId}/{associationTypeId}. The request URL contains the following fields:

FieldDescription
meetingIdThe ID of the meeting.
toObjectTypeThe type of object that you want to associate the meeting with (e.g., contact or company)
toObjectIdThe ID of the record that you want to associate the meeting with.
associationTypeIdThe ID of the association type between the meeting and the other object type. You can retrieve this value through the associations API.

For example, your request URL might look similar to the following:

https://api.hubspot.com/crm/v3/objects/meetings/17612479134/associations/contact/104901/200

To remove an association between a meeting and a record, make a DELETE request to the same URL as above:

/crm/v3/objects/meetings/{meetingId}/associations/{toObjectType}/{toObjectId}/{associationTypeId}

You can pin a meeting on a record so it remains on the top of the record's timeline. The meeting must already be associated with the record prior to pinning, and you an only pin one activity per record. To pin a meeting, include the meeting's id in the hs_pinned_engagement_id field when creating or updating a record via the object APIs. Learn more about using the companies,contacts, deals, tickets, and custom objects APIs.

You can delete meetings individually or in batches, which will add the meeting to the recycling bin in HubSpot. You can later restore the meeting from the record timeline.

To delete an individual meeting by its meeting ID, make a DELETE request to /crm/v3/objects/meetings/{meetingId}.

Learn more about batch deleting by checking out the reference documentation.