HubSpot Events Manage Event Definitions
Browse all Hubspot APIs43
AI ReadinessFoundational (D-)43/100
Official vendor OpenAPI document · agent-readyAnalyticsProduct 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.
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.
Install Jentic One Beta
Connect the Events Manage Event Definitions to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Events Manage Event Definitions, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-events-manage-event-definitions" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-events-manage-event-definitions" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
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
Update or remove an individual property on an existing event definition
Read back the current schema for a custom event before sending occurrences
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
DELETE
/events/v3/event-definitions/{eventName}/property/{propertyName}
Delete a property from an event definition
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
E
Events Manage Event Definitions
- Foundational (D-)43/100
52
Foundational Compliance63
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability70
Security69
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
52
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C-Signals: 4
92%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
17%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
2%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
12%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
67%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
70
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
70%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
69
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
69%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring HubSpot Event Definitions by hand means learning its OAuth2 access token auth, targeting the api.hubapi.com host, and shaping event and property schema payloads yourself. Through Jentic you install once, import HubSpot Event Definitions from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Event Definitions API puts the event name in the URL path (/events/v3/event-definitions/{eventName}), so a rule can pin your agent to one event definition for updating it and its properties. You choose the operations it may call, so deleting a definition or a property is not included unless you add it.
Credential isolation
Your HubSpot access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a HubSpot event definition' or 'add an event property', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 your Jentic One instance 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. Get started with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the HubSpot Event Definitions API?
Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. Because the event name sits in the URL path (/events/v3/event-definitions/{eventName}), you can pin the agent to a single event definition and its properties, and you choose which operations it may call, so destructive calls like DELETE /events/v3/event-definitions/{eventName} or removing a property are excluded unless you add them. Your HubSpot access token is held encrypted by your own instance and injected only at execution time, never reaching the agent's prompt or logs.
GET STARTED