Bugfix: Update to the Custom Behavioral Events API for unknown event names

[dennisedson]

We're making an update to the Custom Behavioral Events API. Currently, the send event endpoint (POST /events/v3/send) will accept an event with an unknown eventName, but will return an HTTP 204 response. Event data is processed asynchronously, which results in events with an unknown name being dropped. The end result is that requests with unknown names do not create events in HubSpot, but the response still shows a 204 response indicating a success.

What's changing?

Beginning on January 23, 2023, the eventName will be checked when the API request is made, and if the name is invalid an HTTP 400 response will be returned, with an error message pointing out the unknown eventName.

If you've worked with the previous version of the Events HTTP API, please note that the v3 API does not support dynamically creating event names, and you'll need to first create the event in HubSpot before events can be sent through the v3 HTTP API.

The Custom Behavioral Events API is currently in beta, and we recommend subscribing to our changelog to make sure you stay up to date with changes to this API.