REST API (v2) integration

eWebinar exposes a REST API (v2) for teams who need data flows that Zapier and the built-in integrations can't cover. Use it to list eWebinars, register attendees, pull analytics and conversations, or wire eWebinar into your own backend. The same API powers the eWebinar MCP server, so an AI assistant such as Claude, Cursor or ChatGPT can read your eWebinars and edit drafts for you.

Create an API key

1. Open Team settings → Integrations in the eWebinar app, or go straight to app.ewebinar.com/home/setup/settings/integrations.
2. Add the API access integration, or open it if your team already has it.
3. Click New key, give it a name (one key per client, for example "Nightly registrant sync"), and tick the permissions it needs under What it can do.
4. Click Create key and copy it straight away. A key is shown only once, when it is created. If you lose it, revoke it from the same list and create a new one.

• Keys belong to the team, not to one person. Changes made with a key show in history under the key's name.
• Creating, seeing and revoking keys is limited to team admins. Other roles can still open the integration to read the setup instructions.
• An older "Original key" may still appear if your team used the API before named keys. Prefer a new named key, then revoke the original one when you're ready.

Permissions

A key carries only the permissions ticked when it was created. An existing key can't be widened, so create a replacement instead. Read is always granted; the others are independent:

• Read: eWebinars, their settings, sessions, transcripts and analytics.
• Edit drafts: create and edit drafts, and upload media.
• Publish: publish and unpublish, and change settings that are live immediately.
• Integrations: connect and manage the team's integrations.
• Registrants: read registrants, register attendees, manage email allow-lists.
• Delete registrants: delete a registrant.

Every endpoint in the reference names the permission it needs. A valid key without that permission gets 403 FORBIDDEN, not 401. Two things no key can do: publish an eWebinar for the first time (that can start billing, so a signed-in person publishes it once from the dashboard, after which a key can re-publish it), and call GraphQL. REST v2 and the MCP server are the supported surfaces for machines.

Make a request

The base URL is https://api.ewebinar.com/v2. Send your key as a bearer token in the Authorization header:

curl https://api.ewebinar.com/v2/webinars \
  -H "Authorization: Bearer ew_api_YOUR_KEY"

List endpoints use cursor pagination: pass the nextCursor from one response on the next request until it comes back absent. Errors share one JSON envelope with a code to branch on (UNAUTHENTICATED, FORBIDDEN, NOT_FOUND, and so on), and requests are rate limited, returning 429 when a limit is exceeded. The details are under Getting started on the developer portal.

Connect an AI assistant (MCP)

The MCP server at https://api.ewebinar.com/mcp is a thin adapter over the same API: every tool maps to a REST route, so anything an assistant can do, you can do with curl. There is nothing to install. In the API access integration, under Connect an AI assistant, pick Cursor, Claude Code, Claude Desktop or another MCP client and copy the configuration, already filled in for your account. Prefer sign-in (OAuth) when a person can approve access in the browser: the assistant then acts as you, you choose what to allow on the consent screen, and draft history records your name.

1. Pick your assistant in the panel and copy the configuration (no key is needed for the sign-in path).
2. Paste it into the client (for example Cursor Settings → MCP, or Claude Code in the terminal).
3. When prompted, sign in to eWebinar and approve access.

For a build, a cron job or a server, where nobody can sign in, expand the key-based setup in the same panel and paste a team API key into the snippet. A key works the same way; edits made with it show as the key's name rather than a person. Edits stay on the draft either way; nothing you have published changes until you publish it.

Assistant access may need to be turned on for your team. If it isn't on yet, the panel still shows the steps and explains that the configuration will not answer until access is enabled. Contact us to turn it on.

Email verification for API registrations

An API registration has no form captcha, and the mailbox check the registration form runs at signup is skipped. Instead, eWebinar verifies the address before the first attendee notification is sent and saves the result.

• Addresses that come back invalid get no attendee email notifications.
• Anything else, including a check that could not finish, still sends. A verification outage never costs a registrant their confirmation, join link or reminders.
• Later notifications reuse the saved result instead of verifying again every time.
• Pass real, deliverable emails from your systems.

The same applies to other registrations made without the form, such as auto-registering contacts from your CRM.

Full reference

The developer portal at api.ewebinar.com/docs documents every way to work with eWebinar programmatically: the REST API v2 reference, the MCP server, webhooks and the JavaScript API for embedded widgets. The landing page and its getting-started guide are public; sign in to your eWebinar account to open the reference pages.

REST endpoints are grouped by resource: Webinars, Registrants, Registration, Conversations, Integrations, Widgets, Media, Webinar video, Scripts, Series, Team and Help. Each endpoint shows the permission it needs with request and response examples.

When to use REST vs Zapier vs Webhooks

• REST API / MCP: for pulling data out (reports, analytics, registrant exports), pushing data in from your own backend, or letting an AI assistant manage drafts with you.
• Webhooks: for getting notified when something happens in eWebinar (use Webhooks).
• Zapier: for no-code flows between eWebinar and 7000+ other apps (see Zapier integration).

---