• Method: register
• Type: POST
• Complete URL: https://api.webinarjam.com/everwebinar/register

The request must include all of the required fields, based on the table below:

* Required fields
** Required if your webinar timezone is set to “Auto-detect the user’s time zone”.
*** This field might be required depending on the configured settings for each webinar
{+} The webinar_id and schedule must be obtained from a previous API call to retrieve the details of whatever specific webinar you want to register the person to. Also, please note that one particular schedule ID might refer to an entire series of webinars, and thus all individual webinar sessions within the same series will have the same schedule ID. In order to pin-point the specific individual session within a series, refer to the DATE parameter.
{-} For webinars configured to display the schedule in the attendee’s own time zone, the API will automatically convert the time zone to EST, unless you specify a particular time zone in your API call.
**** Use the DATE parameter to register a person to a specific webinar session date. Make sure it matches a valid date returned by a previous API call, or else the API will not be able to register the user to any event at all. Also, if the call was made using a custom timezone, make sure that the same timezone is passed with the request.

The response body will be a JSON object containing a user object with the following:

{+} live_room_url, replay_room_url and thank_you_url are unique to each attendee
* These fields will only be returned if they are enabled within the webinar’s configuration settings

Example CURL request:

curl --data "api_key=demokey&webinar_id=6&first_name=FirstName&last_name=LastName&[email protected]&phone_country_code=+1&phone=1234567890&schedule=55" https://api.webinarjam.com/everwebinar/register

Example return:

{
    "status": "success",
    "user": {
        "webinar_id": 6,
        "webinar_hash": "uvw1234",
        "user_id": 1234567,
        "first_name": "FirstName",
        "last_name": "LastName",
        "phone_country_code": "+1",
        "phone": "1234567890",
        "email": "[email protected]",
        "password": null,
        "schedule": "55",
        "date": "2024-01-05 12:00",
        "timezone": "America/Los_Angeles",
        "live_room_url": "https://event.webinarjam.com/go/live/6/ab1cd2ef3",
        "replay_room_url": "https://event.webinarjam.com/go/replay/6/ab1cd2ef3",
        "thank_you_url": "https://event.webinarjam.com/registration/thank-you/6/ab1cd2ef3gh4"
    }
}

• Method: webinar
• Type: POST
• Complete URL: https://api.webinarjam.com/everwebinar/webinar

The request must include all of the required fields, based on the table below:

* Required fields
** Required if your webinar timezone is set to “Auto-detect the user’s time zone”.
** For webinars configured to automatically display the schedule in the attendee’s own time zone, the API will automatically convert the time zone to EST if the time zone is not passed to the API call.

The response body will be a JSON object containing a webinar object with the following:

** This field will be returned only if they are enabled within that particular webinar configuration settings
*** These are generic links to the Live and Replay room, in case you want to send a user directly to those rooms without going through the Registration page
Note: The number of returned schedules will match “Displayed schedules” setting from the EverWebinar schedules configuration for each webinar
**** webinar_hash: this parameter is used in case you want your API to be able to generate the webinar’s one-click registration link.

Example CURL request:

curl --data "api_key=demokey&webinar_id=6" https://api.webinarjam.com/everwebinar/webinar

Example return:

{
    "status": "success",
    "webinar": {
        "webinar_id": 6,
        "webinar_hash": "uvw1234",
        "name": "Demo6",
        "title": "Demo6",
        "description": "My automated webinar",
        "schedules": [
            {
                "date": "2024-01-04 12:00",
                "schedule": 54,
                "comment": "Instant replay"
            },
            {
                "date": "2024-01-05 12:00",
                "schedule": 55,
                "comment": "Just in time"
            },
            {
                "date": "2024-01-05 13:00",
                "schedule": 56,
                "comment": "Every day, 01:00 PM"
            }
        ],
        "timezone": "America/Los_Angeles",
        "presenters": [
            {
                "name": "John Doe",
                "email": "[email protected]",
                "picture": "https://test.s3.amazonaws.com/default_user.jpg"
            }
        ],
        "registration_url": "https://event.webinarjam.com/register/6/uvw1234",
        "registration_type": "free",
        "registration_fee": 0,
        "registration_currency": "",
        "registration_checkout_url": "",
        "registration_post_payment_url": "",
        "direct_live_room_url": "https://event.webinarjam.com/go/live/6/uvw1234ab12",
        "direct_replay_room_url": "https://event.webinarjam.com/go/replay/6/uvw1234ab12"
    }
}

• Method: webinars
• Type: POST
• Complete URL: https://api.webinarjam.com/everwebinar/webinars

The request must include all of the required fields, based on the table below:

* Required fields

The response body will be a JSON object containing an array of webinars. Each webinar object will contain:

* webinar_hash: this parameter is used in case you want your API to be able to generate the webinar’s one-click registration link.

Example CURL request:

curl --data "api_key=demokey" https://api.webinarjam.com/everwebinar/webinars

Example return:

{
    "status": "success",
    "webinars": [
        {
            "webinar_id": 9,
            "webinar_hash": "tuvw1234",
            "name": "Demo6",
            "title": "Demo6",
            "description": "My automated webinar",
            "schedules": [
                "Instant replay",
                "Just in time",
                "Every day, 01:00 PM",
                "Every Monday, 02:00 PM",
                "Saturday, 6 Jan 2024, 03:00 PM"
            ],
            "timezone": "America/Los_Angeles"
        }
    ]
}

Welcome to the EverWebinar API!

In order to integrate with our API, you will first need to apply for approval in your Profile section.  In the below screenshot please fill out the following information:

1.  The URL of your app.  This will be either the URL of the software you’re writing to use our API, or the URL of a third-party app that uses our API, like Zapier.
2.  A description of what your app will do with the WebinarJam API.
3.  Whether or not your app will subscribe users to your webinars.
4.  Any notes pertaining to your app.  This can include login credentials to a demo account or any other information that may be useful.

You should receive a response within 48 hours from submission.  After that, view the rest of this article to integrate with our API.

Please take note of the few bullet points below before digging into the actual technical articles:

• Our API endpoint URL is https://api.webinarjam.com/everwebinar
• You’re required to connect to our server from a SSL secure connection. Non SSL connections will be dropped.

Your API Key can be found in your main webinar dashboard, by clicking on the Advanced link for any of your webinars. You don’t need a new API Key for each webinar, since the Key is global for your entire account.

For users subject to GDPR requirements (mostly European users), and since our API can potentially subscribe users to your webinars without their manual input, it’s your responsibility to make sure that…

• They have granted you permission to handle their personal data.
• They have agreed to be subscribed to your webinars.
• They have granted you permission to communicate with them in the future.

Finally, it’s important to note that our API system has a hardcoded limit of 20 API calls per second per user. That means that your script should not send more than 20 API calls per second to our API endpoint. If that limit is exceeded, the system will return a “Too many requests” error message (429 error), upon which you should wait 1 second and re-try the instruction again.

We strongly recommend you to implement in your scripts a queue system that throttles your outbound API calls to a maximum rate of 20 calls per second. That way, if your script goes through a burst of activity, it will pro-actively queue up the outbound calls and process them in a first-in-first-out sequential order, so they never go beyond the limit. It’s better to hold them back for a second or two than to get them error’ed out!