
Custom Behavioral Events API
Custom Behavioral Events API
Send custom behavioral events into HubSpot through the /events/v3/send endpoint.
Very narrow surface with a clear purpose
Focused on event ingestion rather than analytics retrieval
Confirm that the app has the analytics.behavioral_events.send scope, then send a minimal event to /events/v3/send and verify the event name and property payload are accepted.
Uptime · 30-day window
About this API
This API is not for general CRM reads and writes; it is specifically for custom behavioral event ingestion. The center of the surface is /events/v3/send, guarded by the analytics.behavioral_events.send scope. The resource surface includes "/events/v3/send", with groupings such as "Behavioral_Events_Tracking".
For backend teams, that is useful when the goal is to send product behavior events into hubspot, feed custom events into marketing automation, or centralize behavioral event delivery from a backend service. The spec lists scopes such as "analytics.behavioral_events.send".
Focused on event ingestion rather than analytics retrieval Some listed auth scheme names are legacy-flavored, so choose carefully
What you can build
- 1Send product behavior events into HubSpot
- 2Feed custom events into marketing automation
- 3Centralize behavioral event delivery from a backend service
Strengths & limitations
Strengths
- Very narrow surface with a clear purpose
- The scope explicitly names behavioral event sending
- Lists hapikey, oauth2_legacy, and private_apps_legacy security schemes
Limitations
- Focused on event ingestion rather than analytics retrieval
- Some listed auth scheme names are legacy-flavored, so choose carefully
Example request
curl https://hubapi.com/<endpoint> \
-H "Authorization: Bearer $ACCESS_TOKEN"Getting started
Confirm that the app has the analytics.behavioral_events.send scope, then send a minimal event to /events/v3/send and verify the event name and property payload are accepted.
Technical details
- Auth type
- oauth
- Pricing
- unknown
- Protocols
- REST
- Response time
- 463 ms
- Last health check
- 5/12/2026, 7:37:39 AM