aevent API

Name: aevent API API
Brand: aevent API
Availability: InStock

★ Only Publicly Available SpecCommunicationsVideo Conferencingbearer45 EndpointsREST

For Agents

Run a webinar or virtual-event platform — analytics, actions, files, forms, integrations, and account settings — across 45 REST endpoints.

Quickstart

Get started with aevent API 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:
"get attendance analytics for a webinar"

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

Capabilities

What an agent can do with aevent API API.

Pull webinar attendance, launch, and breakdown analytics for any event

Configure scheduled actions that trigger during or after a webinar

Upload and manage event files via /files endpoints

Create custom forms to collect registrant or attendee data

Manage third-party integrations and pull their usage and data feeds

GET STARTED

Start building with aevent API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for aevent API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for aevent API, keeping it validated and agent-ready. aevent is a webinar and virtual-event platform that automates promotion and attendee engagement around live and pre-recorded sessions. The API exposes 45 endpoints covering attendance and breakdown analytics, scheduled actions, files, custom forms, holiday calendars, integrations and their data feeds, AI completion utilities, working-hour configurations, and account settings. Authentication uses an HTTP bearer token issued from the aevent dashboard.

Use Cases

Patterns agents use aevent API API for, with concrete tasks.

★ Webinar Analytics Reporting

Generate post-event analytics reports for marketing or sales operations teams. POST /analytics/launch returns launch-time metrics, /analytics/attendance returns attendee numbers and durations, and /analytics/breakdown returns segmented metrics. The data can be piped directly into a BI tool or weekly digest without using the aevent UI.

Call POST /analytics/attendance with the event id and date range to return per-session attendance and watch-time metrics

Event Automation and Scheduled Actions

Automate the moves that normally need a human in the live room. POST /actions creates a scheduled action — a chat post, link drop, or external API call — and the /hours and /holidays endpoints feed scheduling logic that respects the team's availability. Useful for production teams running multiple concurrent webinars.

Call POST /actions with type=link_drop, time_offset=15m, and the URL to schedule a CTA drop 15 minutes into a webinar

Integration and Data Sync

Use aevent's /integrations endpoints to manage third-party connectors and pull their data into a CRM or warehouse. GET /integrations lists configured integrations, /integrations/{id}/data accepts a POST to push data to the integration, and /integrations/{id}/usage reports what the integration has consumed. Useful when aevent sits in a stack with HubSpot, Salesforce, or Zapier.

Call GET /integrations to list active connectors, then POST /integrations/{id}/data with attendee records to push into the connected CRM

AI Agent Webinar Operator

Let an AI agent answer event-ops questions and trigger schedules via conversation. Through Jentic, the agent searches by intent, loads the matching aevent schema, and executes with the bearer token isolated in the vault. The agent can pull attendance after a session ends or schedule the next round of actions before it begins.

Search Jentic for 'get webinar attendance analytics', load /analytics/attendance schema, and execute with the event id

Key Endpoints

45 endpoints — jentic publishes the only available openapi specification for aevent api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/analytics/attendance

Return attendance metrics for an event

POST

/analytics/launch

Return launch-time metrics for an event

POST

/analytics/breakdown

Return segmented breakdown analytics

POST

/actions

Create a scheduled in-event action

POST

/files

Upload a file to an event

POST

/forms

Create a custom registrant or attendee form

GET

/integrations

List configured third-party integrations

POST

/integrations/{id}/data

Push data to a configured integration

POST

/analytics/attendance

Return attendance metrics for an event

POST

/analytics/launch

Return launch-time metrics for an event

POST

/analytics/breakdown

Return segmented breakdown analytics

POST

/actions

Create a scheduled in-event action

POST

/files

Upload a file to an event

Why though Jentic?

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

Credential isolation

Your aevent bearer token is stored encrypted in the Jentic vault and applied as the Authorization header at execution time, so agents never see the raw token in their context.

Intent-based discovery

Agents search by intent (e.g. 'get webinar attendance analytics') and Jentic returns the matching aevent operation with its body schema, so the agent calls the right /analytics endpoint without browsing docs.

Time to first call

Direct aevent integration: 1-2 days to wire auth, the analytics body shapes, and the integration data-push flow. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

WebinarJam

Live webinar platform with built-in registration and attendee features

Choose WebinarJam for an out-of-the-box webinar host with built-in player; choose aevent when automation, scheduled actions, and CRM integration are central

Alternative

ON24

Enterprise webinar and digital experience platform

Pick ON24 for enterprise webinars with regulated-industry features; pick aevent for lighter-weight automation and analytics on smaller events

Complementary

Calendly

Scheduling layer that books one-to-one meetings around events

Use Calendly for one-to-one scheduling alongside aevent's group webinars

Complementary

HubSpot Marketing Events API

CRM-side event records that pair with aevent for marketing follow-up

Use HubSpot Marketing Events to register attendance back into the CRM after pulling data from aevent's /analytics/attendance

FAQs

Specific to using aevent API API through Jentic.

Why is there no official OpenAPI spec for the aevent API?

aevent does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call aevent API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the aevent API use?

aevent uses an HTTP bearer token; pass an Authorization: Bearer <token> header with a token issued from the aevent dashboard. Through Jentic the token is stored in the vault and injected at execution time.

Can I pull webinar attendance analytics through the aevent API?

Yes. POST /analytics/attendance returns per-session attendee numbers and watch-time, /analytics/launch returns the metrics around event launch, and /analytics/breakdown returns segmented metrics for finer cuts.

How do I schedule an in-event action with the aevent API?

Call POST /actions with the action type, the event reference, and the time offset; the action will fire during the live session. Use /hours and /holidays endpoints to keep scheduled actions inside operating windows.

What are the rate limits for the aevent API?

aevent applies per-account throttling but does not declare specific limits in the spec. Watch for HTTP 429 responses, which Jentic surfaces verbatim so agents can implement back-off, and consult aevent support for plan-tier allowances.

How do I push attendees to a connected integration through Jentic?

Run pip install jentic, search Jentic with 'push data to an aevent integration', load the /integrations/{id}/data schema, and execute with the integration id and the records to send. Jentic injects the bearer token at execution time.