HubSpot Marketing Events Extension

What authentication does the Marketing Events Extension API use?

It accepts the developer hapikey query parameter, OAuth 2.0 access tokens, the private-app-legacy header, and the hapikey query parameter as a legacy fallback. Jentic stores all of these credential types in its encrypted vault and provides agents with scoped tokens at execution time.

Can I record attendance for a contact that does not yet exist in HubSpot?

Yes. POST /marketing/v3/marketing-events/attendance/{externalEventId}/{subscriberState}/email-create accepts an email address directly. HubSpot creates or updates the contact record to match and records the attendance state in the same call, so no separate contact lookup is required.

What are the rate limits for the Marketing Events Extension API?

Standard HubSpot API limits apply: 100 requests per 10 seconds per private app token and 110 per 10 seconds per OAuth app per portal. For high-volume webinar imports, use the events upsert batch endpoint and the email-upsert attendance variant rather than one call per attendee.

How do I register a marketing event through Jentic?

Search Jentic for 'create hubspot marketing event', load the schema for POST /marketing/v3/marketing-events/events/upsert, and execute with an array of events keyed by externalEventId. For one event at a time, POST to /marketing/v3/marketing-events/events with the event payload.

Is the Marketing Events Extension API free?

API access is included with any HubSpot subscription that has Marketing Hub features. Marketing event records appear on contact timelines and in Marketing Hub reports; reporting depth scales with the Marketing Hub subscription tier.

Can I limit what my agent is allowed to do with the Marketing Events Extension API?

Yes. Because you run Jentic One yourself, your own rules decide which of the Marketing Events Extension operations the agent may call, so you can allow only what it needs, such as upserting and searching events, and recording attendance state by contactId or email. State-changing operations like cancelling or completing an event stay off limits unless you explicitly add them to the agent's set. Your HubSpot credential is stored once by your own instance and injected at execution time, never entering the agent's prompt or logs.