aevent API
Agent-ready OpenAPI document · curated by JenticCommunicationsVideo Conferencingbearer45 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Run a webinar or virtual-event platform - analytics, actions, files, forms, integrations, and account settings - across 45 REST endpoints.
Use for: Get attendance analytics for a recent webinar, Pull a launch breakdown for an event by source, Schedule an action to run during a webinar, Upload a slide deck file to an aevent event
Not supported: Does not handle live video streaming, payment processing, or end-attendee chat - use for aevent webinar configuration, automation, and analytics only.
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.
Install Jentic One Beta
Connect the aevent API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the aevent API, 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%2Faevent.com%2Faevent" | 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%2Faevent.com%2Faevent" | 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 aevent 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
Configure working hours and holiday calendars for scheduled actions
Read account settings including templates, custom fields, personalisation, and tooltips
Use Cases
Patterns agents use aevent 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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the aevent API by hand means learning its bearer auth and coding calls across its analytics, actions, and integration endpoints. Through Jentic you install once, import the aevent API from the API Directory, store the token once, and your agent calls it.
Permission scoping
aevent drives most operations through the request body and puts an integration id in the path only for integration data, so limit the agent to the operations it needs, such as reading attendance analytics. You choose which operations are in the allowed set, so anything you leave out is not reachable.
Credential isolation
Your aevent bearer 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 '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 the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using aevent 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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the aevent API?
Yes. Jentic One is self-hosted, so your own rules decide which aevent operations and credentials the agent can use. Because aevent drives most operations through the request body and only puts an integration id in the path for integration data, you can allow just the operations the agent needs, such as reading attendance analytics with POST /analytics/attendance, while leaving out actions like POST /integrations/{id}/data. Anything you keep out of the allowed set is not reachable, and your bearer token stays with your instance and is injected only at execution time.
GET STARTED