/api/v3/events/{eventId}/registrants
Authentication: Requires API Key in the request header.
Authorization: The event must belong to the account associated with the API token. Returns 403 if the event belongs to a different account.
Path Parameters:
Query Parameters:
Response: Paginated list of registrant objects for the specified event.
Rate limit: Once every 1 second for unique requests.
Pagination: This endpoint uses cursor-based pagination with a default page size of 100 registrants. To iterate through all results:
- Make the first request without a
cursorparameter - If
page.next_cursoris notnull, make another request withcursorset to that value - Repeat until
page.next_cursorisnull
200 OKRegistrants retrieved successfully.401 UnauthorizedAuthentication failed (missing or invalid API token).403 ForbiddenEvent does not belong to this account.404 Not FoundEvent not found.429 Too Many RequestsRate limit exceeded.500 Internal Server ErrorUnexpected server error.
On-Demand Webinars
The endpoint accepts an on-demand webinar ID in theeventId path parameter. The response schema, filters, sorting, pagination, authorization and rate limits are identical to live webinars, so existing integrations parse on-demand responses with no changes.
Notes:
participatedistrueonce the registrant has watched more than 10 seconds of the recording — the same threshold as the “Watched” metric in on-demand analytics.attendance_rateanddurationreport watch percentage and watch time. Both arenullif the registrant has never watched.join_urlis the registrant’s personalized, tokenized watch URL.approvedis alwaystrue. On-demand webinars have no approval flow, and the field is kept for schema compatibility.referrerreturns"api"for registrants created through the Create Webinar Registrant endpoint.- Watch activity is reflected whenever it happens. A registrant who watches 30 days after registering returns updated
participated,attendance_rateanddurationvalues on subsequent calls.updated_afterfilters by registration date only. Later watch activity does not change a registrant’supdated_aftervalue, so an incremental sync will not surface registrants whose watch metrics changed after they registered. To keep watch data current, re-pull the full registrant list on a schedule.- While an on-demand webinar is unpublished, its public page and any issued
join_urllinks return 404. Registrant data remains available through this endpoint, and the links work again once the webinar is republished.