There's a new version of the HubSpot API

We're also working on a new documentation website, you're invited to check it out and give us your feedback.

Create a group of timeline events

Last updated May 6, 2024

POST /integrations/v1/:application‐id/timeline/event/batch

Please note: beginning December 2024, the following changes will be made to the v1 Integration Timeline API.

  • You will not be able to update existing events.
  • You cannot use the PUT method to create events.

You can now use the POST method to create events, however it's recommended to transition to the v3 Timeline Events API for the most up to date features. Learn more about this update on the HubSpot Developer Changelog.

Method Details

HTTP Methods:


Content Type:


Response Format:


Requires Authentication?


Rate Limited?





Marketing & CRM

Required Scope:


Create or update a group of timeline events. This can be used to backfill events when your integration is first installed, or to efficiently sync a large number of events occurring over a short period of time. Up to 100 events can be included in a single batch.

See the Timeline Overview for more details about creating and working with events.

See creating or updating a single event for more details about the data that should be included for each event.

Required Parameters How to use Description
OAuth Access Token Authorization: Bearer {token}
Used in the request headers
Used to authenticate the request. Please see this page for more details about authentication.
NOTE: You must use an OAuth access token to create an event. API keys are not supported.
application-id Used in the request URL The ID of the application that the event type was created for. The eventTypeId used in the request body must line up with this application-id.
Events list "eventWrappers": []
Used in the request body
A list of events that you want to create or update. See creating or updating an event for more details on the format used for events.
Up to 100 events can be included in a single batch.

Returns a 204 No Content response on success.Otherwise, you'll receive a 4xx error, with more details about the specific error in the body of the response.

Note: if there are any problems with the request, the entire batch will fail, so a 4xx response means that no events will be created or updated.