Webinars API

Create webinars, register attendees, and drive reminder + follow-up workflows

​

Overview

The Webinars API lets you run your entire webinar communication flow through Flywheel:

1. Create a webinar (or create it in the dashboard) and link it to a workflow
2. Register people as they sign up — registrants don’t need to exist in Flywheel first; profiles are created or matched automatically
3. Flywheel enrolls each registrant into every live workflow with a matching Webinar Registration trigger (reminder emails/SMS anchored to the start time, etc.)
4. Report attendance during or after the webinar so Webinar Attendance Split nodes can branch attendees vs no-shows for follow-up
5. Reschedule if the date moves — all pending anchored reminders automatically recompute to the new time

​

Authentication

All webinar endpoints require authentication using an API key and authentication type header. Include both headers in your requests:

Authorization: YOUR_API_KEY
Auth-Type: api

API keys are managed in the Flywheel dashboard under Settings → API Keys. All webinar objects are scoped to the organization the API key belongs to.

​

Create a Webinar

POST /v1/webinars

const response = await fetch('https://api.flywheel.cx/v1/webinars', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Auth-Type': 'api',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    webinar: {
      title: 'Onboarding Masterclass',
      start_time: '2026-09-01T17:00:00Z',
      timezone: 'America/New_York',
      duration_minutes: 60,
      join_url: 'https://zoom.us/j/123456789',
      provider: 'zoom',
      automation_id: 'a3a9c0de-...' // optional: workflow to associate
    }
  })
});

const { webinar } = await response.json();
// webinar.id → use this for registrations

Field	Type	Required	Description
id	string	No	Your own v4 UUID for the webinar. Makes the call safe to retry: the same id returns the webinar already created instead of a second one
title	string	Yes	Webinar title
start_time	string	Yes	ISO 8601 datetime with timezone offset
timezone	string	No	IANA timezone, e.g. America/New_York
duration_minutes	number	No	Length of the webinar
join_url	string	No	Link attendees use to join
provider	string	No	Platform label, e.g. zoom, livestorm. A label only — to connect Demio or WebinarJam, link the webinar (see below)
status	string	No	draft or scheduled (defaults to scheduled)
automation_id	string	No	A workflow of your organization to associate with this webinar

Webinars can also be created in the dashboard under Webinars. Either way they start as scheduled unless you pass draft.

​

Register a User

POST /v1/webinars/{webinar_id}/registrants

The core endpoint. Pass whatever your signup form collected as person — they do not need to be an existing Flywheel user. Flywheel matches them to an existing profile by external_user_id, email, phone or anonymous_id, or creates a new one. Send ad_source and the pixel’s visitor_id too and the registration carries its attribution.

const response = await fetch('https://api.flywheel.cx/v1/webinars/0d4f6f36-2b6a-4c1e-9a6f-1f2d3c4b5a69/registrants', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Auth-Type': 'api',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    person: {
      email: '[e-mail]',
      full_name: 'Jane Doe',
      phone: '[phone]',
      properties: {
        company: 'Acme',
        signup_source: 'landing_page'
      }
    },
    // Optional: straight off the landing page's query string, stored verbatim
    ad_source: { utm_source: 'facebook', utm_campaign: 'fall-launch', fbclid: 'IwAR...' },
    // Optional: window.flywheel('vid') when the page carries the Flywheel pixel
    visitor_id: '01J9ZX...'
  })
});

const { registration_id, person_id, already_registered, join_url, join_url_personal } = await response.json();

The response:

{
  "registration_id": "7c1b2a3d-5e6f-4a8b-9c0d-1e2f3a4b5c6d",
  "person_id": "9e2b4c71-0a5f-4d38-b6e1-3c7f8a2d5e94",
  "already_registered": false,
  "join_url": "https://us02web.zoom.us/w/81234567890?tk=...",
  "join_url_personal": true
}

Field	Type	Description
registration_id	string	The registration
person_id	string	The Flywheel person, matched or created
already_registered	boolean	true when this person was already registered for this webinar. Nothing was re-sent
join_url	string | null	The link this person joins with, the same one their messages carry: their own link when the linked platform issued one, otherwise the webinar’s join_url. null when the webinar has neither
join_url_personal	boolean	true when join_url is this person’s own link. false when it is the webinar’s shared link, or null

Use join_url for a join button on your thank-you page or in a calendar invite. Check join_url_personal first when the webinar requires registration on its platform: on such a Zoom webinar the shared link opens Zoom’s own registration form, not the room. A repeat registration returns the same link. A platform that could not be reached never fails the registration; the response then carries the shared link with join_url_personal: false.

Someone already in Flywheel can be registered by id instead: send { "person_id": "..." } in place of person.

POST /v1/webinars/register is deprecated (September 2026). It still works — same behaviour, it runs the same code — but new integrations should use the endpoint above. Its user object becomes person, and user.user_id becomes person.external_user_id; the response names the person person_id instead of org_user_id.

​

What happens on registration

1. Identification — the person is found (by external_user_id → email → phone → anonymous_id priority) or created. With visitor_id, the pixel visitor who filled the form in is claimed, bringing their touch history; ad_source is recorded for attribution. Name fields and custom properties are merged into their profile.
2. Registration — an idempotent registration record is created for the (webinar, user) pair.
3. Workflow enrollment — the user is enrolled into every live workflow with a Webinar Registration trigger matching this webinar (or bound to “any webinar”).
4. Event fired — a $fw_webinar_registration event is recorded on the user’s timeline with the webinar details, usable in event-triggered workflows, segments, and analytics.

Registering the same user for the same webinar twice is safe: the API returns the existing registration with already_registered: true and fires no duplicate workflows or events.

A canceled webinar refuses registrations with a 400 whose code is failed_precondition — registering would start its reminder workflows for a session that is not happening. The person is still identified (created or matched) first, so a signup from a stale page is not lost.

​

Person object

Field	Type	Description
external_user_id	string	Your own id for this person
email	string	Email address
phone	string	Phone number
first_name / last_name	string	Name fields
full_name	string	Split into first/last automatically when those aren’t supplied
anonymous_id	string	Anonymous id from your tracking
properties	object	Custom profile properties (string, number, boolean values)

At least one of external_user_id, email, phone or anonymous_id is required.

​

The $fw_webinar_registration event

Every new registration records this event with the following properties:

{
  "event_name": "$fw_webinar_registration",
  "custom_properties": {
    "webinar_id": "0d4f6f36-...",
    "webinar_title": "Onboarding Masterclass",
    "webinar_start_time": "2026-09-01T17:00:00.000Z",
    "webinar_join_url": "https://zoom.us/j/123456789",
    "registration_id": "7c1b2a3d-..."
  }
}

The $fw_ prefix is reserved — it can only be produced by Flywheel itself, so the event is a trustworthy signal in workflows and segments.

​

Webinar Platform Integrations (Demio)

If your organization has connected Demio (Dashboard → Settings → Integrations) and the webinar is linked to a Demio event in the webinar drawer, registration does two extra things automatically:

1. The registrant is pushed to the Demio event, so they exist in Demio without any extra call.
2. Demio’s personalized join link for that attendee is stored on the registration and exposed to workflows as the registration_join_url context variable — use it in reminder emails/SMS so each person gets their own join button.

Attendance also syncs automatically: about 30 minutes after the webinar’s scheduled end, Flywheel pulls Demio’s participants report and marks attendees, feeding Webinar Attendance Split workflow nodes with no manual attendance calls. You can still call the attendance endpoint below for corrections or non-Demio webinars.

​

Mark Attendance

POST /v1/webinars/attendance

Report that a registrant attended (or didn’t). Resolve the user by user_id or email. Attendance is read live by Webinar Attendance Split workflow nodes when they run, so you can report it during the webinar or after it ends. Reporting it also arms the webinar’s attended / no-show follow-up sequences. A canceled webinar refuses attendance (failed_precondition).

await fetch('https://api.flywheel.cx/v1/webinars/attendance', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Auth-Type': 'api',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    webinar_id: '0d4f6f36-2b6a-4c1e-9a6f-1f2d3c4b5a69',
    email: '[e-mail]',
    attended: true // optional, defaults to true
  })
});

​

Reschedule a Webinar

POST /v1/webinars/reschedule

Move the start time. Every pending “wait until webinar start ± offset” step in in-flight workflow runs is recomputed, the webinar’s own scheduled messages are re-anchored, and a linked platform’s attendance sync moves to the new end time — so everything timed off the webinar follows automatically.

const response = await fetch('https://api.flywheel.cx/v1/webinars/reschedule', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Auth-Type': 'api',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    webinar_id: '0d4f6f36-2b6a-4c1e-9a6f-1f2d3c4b5a69',
    start_time: '2026-09-08T17:00:00Z'
  })
});

const { recomputed } = await response.json();
// recomputed → number of pending reminder tasks moved to the new time

​

Manage Webinars, Series and Attendance

The endpoints above cover the signup path. The management API covers everything else the dashboard does — list and edit webinars, recurring series, registrants, the send plan, revenue and platform links. The same operations are available to AI agents as MCP tools on /mcp (list_webinars, get_webinar_plan, register_for_webinar and so on).

Method	Path	What it does
GET	/v1/webinars	List webinars. Filters: status, series_id, starts_after, starts_before, order (asc/desc), limit, offset
GET	/v1/webinars/{webinar_id}	One webinar with registration counts (registered, attended, no-show) and its messages by status
PATCH	/v1/webinars/{webinar_id}	Edit title, start_time, timezone, duration_minutes, join_url, status, automation_id. Omitted fields stay; null clears. A new start or duration re-anchors every reminder
DELETE	/v1/webinars/{webinar_id}	Delete a webinar that has no registrations, no sent messages and no series. Otherwise cancel it (status: canceled)
POST	/v1/webinars/{webinar_id}/clone	Copy to a new start_time, messages included as drafts. Optional new_webinar_id for safe retries
GET	/v1/webinars/{webinar_id}/registrants	Registrants with attendance, watch time, offer clicks and purchases. Filter by segment: registered, attended, no_show, left_early, clicked_offer, purchased, refunded
POST	/v1/webinars/{webinar_id}/registrants	Register someone: person_id, or a signup person with optional ad_source / visitor_id. Returns their join_url (see Register a User)
PUT	/v1/webinars/{webinar_id}/registrants/{person_id}/attendance	Set attended for one registrant
GET	/v1/webinars/{webinar_id}/plan	Every message the webinar sends and when, resolved for sample (or your entry_times) registration moments
GET	/v1/webinars/{webinar_id}/revenue	Revenue, split into attributed and unattributed, per message
PUT	/v1/webinars/{webinar_id}/platform	Link to demio, webinarjam or zoom (event_id; optional date_id for Demio and WebinarJam — left out on a WebinarJam webinar with several schedules, the one on the webinar’s date is picked). Zoom ids are checked against your connected Zoom account
DELETE	/v1/webinars/{webinar_id}/platform	Unlink from the platform. On a series’ template webinar, the series’ upcoming webinars sharing that Zoom webinar are unlinked too
GET / POST	/v1/webinar-series	List series / create one: name, cadence (interval_unit day/week, interval_count, weekday 0–6 for weekly, time_of_day HH:mm), timezone, duration_minutes, build_ahead_count, optional id. Link the series’ template webinar to a recurring Zoom webinar and every upcoming webinar of the series is linked to it too, in either order
GET / PATCH	/v1/webinar-series/{series_id}	A series with its sessions, skipped dates and next unbuilt dates / edit its rule or status (active, paused, archived)
POST	/v1/webinar-series/{series_id}/materialize	Build any sessions the series is short of now
POST	/v1/webinar-series/{series_id}/skips	Skip an upcoming date (occurrence_date, yyyy-MM-dd)
DELETE	/v1/webinar-series/{series_id}/skips/{occurrence_date}	Put a skipped date back
GET	/v1/webinar-series/{series_id}/revenue	Revenue across the series, with a per-session breakdown

Status moves are validated: draft → scheduled or canceled; scheduled → live, completed or canceled; live → completed or canceled; canceled → scheduled (messages whose time passed while canceled are not re-sent); completed is final.

​

Typical Integration

A landing-page signup form wired to Flywheel:

// 1. Once: create the webinar (or grab its id from the dashboard)
const { webinar } = await flywheel('/v1/webinars', {
  webinar: { title: 'Product Deep Dive', start_time: '2026-09-15T16:00:00Z' }
});

// 2. On every form submission: register the signup
app.post('/webinar-signup', async (req, res) => {
  await flywheel(`/v1/webinars/${webinar.id}/registrants`, {
    person: {
      email: req.body.email,
      full_name: req.body.name,
      properties: { signup_source: 'landing_page' }
    },
    ad_source: { utm_source: req.query.utm_source, fbclid: req.query.fbclid }
  });
  res.redirect('/thanks');
});

// 3. After the webinar: sync attendance from your platform (e.g. Zoom report)
for (const attendee of zoomAttendees) {
  await flywheel('/v1/webinars/attendance', {
    webinar_id: webinar.id,
    email: attendee.email
  });
}

Pair this with a workflow that uses the Webinar Registration trigger, anchored waits (“1 day before start”, “1 hour before start”), and a Webinar Attendance Split after the webinar ends for attendee vs no-show follow-ups.