Events Manage Event Definitions

Name: Events Manage Event Definitions API
Brand: Events Manage Event Definitions
Availability: InStock

✓ Official Vendor SpecAnalyticsProduct Analyticsoauth28 EndpointsREST

For Agents

Define and evolve custom behavioural event schemas in HubSpot — create event definitions, then add or remove typed properties without rebuilding the whole schema.

Quickstart

Get started with Events Manage Event Definitions in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create hubspot event definition"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Events Manage Event Definitions API.

Create a new custom behavioural event definition with a typed property set

Update an existing event definition's metadata and label by event name

Delete a custom event definition that is no longer in use

Add a new typed property to an event definition without redefining the whole schema

GET STARTED

Start building with Events Manage Event Definitions API

Explore with Jentic

View OpenAPI Document

Use for: I need to create a new custom event definition called checkout_completed, Add a typed property named order_value to the signup_completed event, Update the label of an existing custom event definition, Remove a deprecated property from an event schema

Not supported: Does not send event occurrences, query event history, or manage CRM contact records — use for defining and evolving custom event schemas only.

The HubSpot Manage Event Definitions API lets you create, update, and delete the schemas for custom behavioural events tracked against contacts in a HubSpot account. Each event definition declares a unique event name and a set of typed properties, which then governs every occurrence sent through the Send Event Completions API. This API also supports adding, updating, and removing individual properties on an existing event definition without redefining the whole schema, which keeps custom events evolvable as the product or campaign tracking changes.

Use Cases

Patterns agents use Events Manage Event Definitions API for, with concrete tasks.

★ Provision a Custom Event Schema

Before tracking a new product behaviour in HubSpot you must register an event definition with the property types it will carry. This API lets an agent create a definition such as checkout_completed with typed properties (order_value as number, currency as string), so that subsequent event completions are validated and reportable in HubSpot. Provisioning the schema once unlocks reporting, segmentation, and workflow triggers across the platform.

Call POST /events/v3/event-definitions with eventName=pe12345_checkout_completed and a property array including order_value (number) and currency (string).

Evolve an Event Schema Without Rebuilding

Product tracking needs change — add a new property to an existing event definition without losing historical occurrences or redefining the full schema. POST to the property subresource of an event definition to register a new typed property, or DELETE to remove a deprecated one. Useful when adding a new attribute (for example coupon_code on checkout_completed) mid-campaign.

Call POST /events/v3/event-definitions/{eventName}/property with name=coupon_code and type=string to add the property.

Schema Cleanup and Deprecation

Deprecate event definitions that are no longer in use by deleting the definition or removing specific properties to keep the HubSpot reporting catalogue clean. Listing the current schema before deletion lets an agent confirm there are no active dashboards that depend on the property. Useful for end-of-campaign cleanup and for reducing portal clutter when a product feature is sunset.

Call DELETE /events/v3/event-definitions/{eventName}/property/{propertyName} to remove a deprecated property, then DELETE /events/v3/event-definitions/{eventName} once unused.

AI Agent Schema Bootstrap via Jentic

An AI agent provisioning a new analytics integration searches Jentic for HubSpot event-definition operations, loads the create-definition schema, and submits the event with its property list. Jentic stores the OAuth credentials so the agent never handles raw tokens, and the typed input schema means the agent gets validation feedback before the call hits HubSpot.

Search Jentic for "create hubspot event definition", load the input schema, and execute POST /events/v3/event-definitions with the new event name and property array.

Key Endpoints

8 endpoints — the hubspot manage event definitions api lets you create, update, and delete the schemas for custom behavioural events tracked against contacts in a hubspot account.

METHOD

PATH

DESCRIPTION

POST

/events/v3/event-definitions

Create a new custom event definition

PATCH

/events/v3/event-definitions/{eventName}

Update an existing event definition

DELETE

/events/v3/event-definitions/{eventName}

Delete a custom event definition

POST

/events/v3/event-definitions/{eventName}/property

Add a property to an event definition

PATCH

/events/v3/event-definitions/{eventName}/property/{propertyName}

Update a property on an event definition

DELETE

/events/v3/event-definitions/{eventName}/property/{propertyName}

Delete a property from an event definition

POST

/events/v3/event-definitions

Create a new custom event definition

PATCH

/events/v3/event-definitions/{eventName}

Update an existing event definition

DELETE

/events/v3/event-definitions/{eventName}

Delete a custom event definition

POST

/events/v3/event-definitions/{eventName}/property

Add a property to an event definition

PATCH

/events/v3/event-definitions/{eventName}/property/{propertyName}

Update a property on an event definition

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

HubSpot OAuth and private app tokens are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped execution access — the raw bearer token never enters the agent's context window.

Intent-based discovery

Agents search Jentic with intents like 'create hubspot event definition' and Jentic returns the matching operation with its input schema, so the agent calls POST /events/v3/event-definitions with the right property types without browsing HubSpot docs.

Time to first call

Direct HubSpot integration: 1-3 days for OAuth setup, schema validation, and idempotency handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Events Send Event Completions

Send occurrences of the events you define here

Choose this once a definition exists and the agent needs to record actual event occurrences.

Complementary

Events Events

Read back the events captured against contacts

Choose this when the agent needs to query event history rather than manage schemas.

Complementary

CRM Contacts

Manage the contacts that events are fired against

Choose this when the agent needs to create or update the contacts referenced by event occurrences.

Alternative

Mixpanel

Schema-on-write product analytics with broader event modelling than HubSpot's custom events

Choose Mixpanel when the tracking use case is product-wide and not tied to the HubSpot CRM.

FAQs

Specific to using Events Manage Event Definitions API through Jentic.

What authentication does the Manage Event Definitions API use?

It accepts HubSpot OAuth 2.0 access tokens or private app tokens (legacy schemes oauth2_legacy and private_apps_legacy) sent as Bearer in the Authorization header. Through Jentic, the token is stored encrypted in MAXsystem and injected at execution time.

Can I add a property to an event without redefining the whole schema?

Yes. Call POST /events/v3/event-definitions/{eventName}/property with the property name and type. Existing occurrences are preserved and new sends can immediately include the property.

What property types are supported for event definitions?

HubSpot supports string, number, datetime, and enumeration property types on custom event definitions. Set the type field on each property when creating the definition or adding a property to an existing one.

What are the rate limits for this API?

HubSpot enforces account-level limits of 100 requests per 10 seconds for OAuth and private app tokens, with daily caps that depend on the subscription tier. Watch the X-HubSpot-RateLimit response headers to back off before hitting the cap.

How do I create a custom event definition through Jentic?

Run pip install jentic, search for "create hubspot event definition", load the schema for POST /events/v3/event-definitions, and execute with eventName and a property array. Sign up at https://app.jentic.com/sign-up.

What happens to existing occurrences when I delete an event definition?

Deleting a definition removes the schema and detaches the event from new reporting, but historical occurrences may remain in the events store for a retention window. Confirm with HubSpot's current docs before removing definitions in active use.