/api/v3/events/{eventId}/registrants
Authentication: Requires API Key in the request header.
Path Parameters:
Request Body Paramaters:
email: Email address of the registrant. Must be unique per event.first_name: Registrant’s first name.last_name: Registrant’s last name.custom_fields: List of custom registration fields. Each item holds the fieldlabel(the custom field name) and the submittedvalue.Notes:
email,first_name&last_nameare always mandatory for every webinar.- Rest of parameters are mandatory only if defined so in the registration form setup when scheduling the event.
phonefield: phone number in international format, separated to country code and phone number.textfield limited to 256 characters.checkboxfield: limited to TRUE or FALSE
200 OKRegistration created successfully.401 UnauthorizedAuthentication failed (Invalid or missing API token).403 ForbiddenThe event belongs to another account.404 Not FoundEvent not found.409 ConflictDuplicate registration (a registrant with the same email already exists for this event), or the on-demand webinar is not published.422 Unprocessable EntityValidation error (for example, invalid email format, unsupported country code, or invalid custom_fields payload).
On-Demand Webinars
The endpoint accepts an on-demand webinar ID in theeventId path parameter. The request and response contracts are identical to live webinars — no new routes and no schema changes.
Notes:
- Registration is allowed only for published on-demand webinars. Registering to an unpublished webinar returns
409 Conflict.- While a webinar is unpublished, its public page — including previously issued
join_urllinks — returns 404. Republishing restores those links, and registrants do not need to register again.join_urlis the registrant’s personalized, tokenized watch URL. Opening it lands the registrant directly on the player, skipping the registration form.- Riverside sends no emails for on-demand registrations, whether created through the API or the registration form. Delivery of the watch link is owned by you.
- Registrants created through the API return
referrer: "api"in Get Registrants, and are otherwise indistinguishable from form registrants across the registrants list, counts, engagement analytics and CRM sync.- Watch activity through the link is attributed to the created registrant, and is reflected in the
participated,attendance_rateanddurationfields of Get Registrants.- There is no registrant cap for on-demand webinars.