# WebinarJam’s API: what will it tell you about an attendee, and when?

URL: https://callhush.com/platforms/webinarjam
Last updated: 2026-07-27

No: and the gap goes further than the webhooks. WebinarJam's leave-early trigger is a negative trigger its own documentation evaluates after the session concludes, and the registrants-and-attendees API returns an entry time and a duration with no exit timestamp at all. What that leaves, and how WebinarJam and EverWebinar differ on API access.

Registration and live attendance, as they happen. Departure, never: not during the session, and not afterwards either, which is the part almost nobody checks.

There is no WebinarJam webhook for an attendee leaving during the session. “If they leave early” is a **negative trigger**, and WebinarJam’s own automation documentation says negative triggers are evaluated after the webinar session concludes. The gap is wider than the trigger list, though: the registrants-and-attendees API returns an entry time and a duration and **no exit timestamp at all**, so there is nothing to poll for either. Everything on the registration side, by contrast, is a genuine push event.

- **0**: Fields in the registrants-and-attendees API that record when somebody left the session (Source: [WebinarJam API: Get a list of registrants and attendees](https://support.webinarjam.com/en/articles/15370152-get-a-list-of-registrants-and-attendees-webinarjam-api))
- **8**: Triggers Zapier advertises for WebinarJam. One of them is named as though it fired live (Source: [Zapier: WebinarJam integrations](https://zapier.com/apps/webinarjam/integrations))
- **2 business days**: Typical processing time for an API key application: approval required, paid subscribers only (Source: [WebinarJam support: Apply for an API key](https://support.webinarjam.com/en/articles/15370143-apply-for-an-api-key-for-webinarjam-or-everwebinar))

## Is there a WebinarJam webhook for an attendee leaving mid-session?

No, and the honest word for it on this platform is **impossible** rather than difficult. People search for this as “attendee drop off”, which is worth separating into its two meanings before answering, because they are not the same problem. Losing people between registration and the session is the one that decides your show-up rate, and WebinarJam gives us everything we need to work on it. Losing somebody who was watching and walked out mid-session is the one this section is about, and nothing on the platform reports it while the session is running.

The vendor states the rule itself. Its automation documentation divides triggers in two: [“Positive triggers are executed as soon as the event occurs”](https://support.webinarjam.com/en/articles/15369997-create-autoresponder-automation-rules-for-your-webinar) against “Negative triggers are evaluated after the webinar session concludes”: with “If they register” and “If they attend the live webinar” on the first list, and “If they miss the webinar” and “If they leave early” on the second.

*Where a departure would have to show up on WebinarJam, and whether it does*

| Surface | What it carries | Usable mid-session? |
| --- | --- | --- |
| Custom webhook, positive triggers | Registration and live attendance, “executed as soon as the event occurs” | Yes: but neither is a departure |
| Custom webhook, negative triggers | “If they leave early”, “If they miss the webinar” | No: “evaluated after the webinar session concludes” |
| Zapier’s “Registrant Leaves Before” | The same negative trigger under a name that reads live | No |
| Registrants-and-attendees API | entered_live, time_live: an entry time and a duration | No exit timestamp exists to read |
| REST API webhook endpoints | None. The developer API documents no webhook endpoints | Nothing to subscribe to |

> **The report closes the last door, and it is the door people assume is open:** When a webhook is missing, the usual fallback is to poll a report and diff it. That fallback does not exist here. The documented registrant fields include [`entered_live` and `time_live`](https://support.webinarjam.com/en/articles/15370152-get-a-list-of-registrants-and-attendees-webinarjam-api), when they arrived, and how long they stayed, and no field for when they left. You cannot poll your way to a signal the platform never records.

For completeness, this is not WebinarJam being worse than the field. Mid-session exit is a **no on every row** of [our compatibility matrix](https://callhush.com/platforms), including the single platform that does push a leave event during the session, where it has been reported [not arriving at all, with no entry in the vendor’s own webhook logs](https://devforum.zoom.us/t/bug-webinar-participant-left-webhook-sometimes-not-fired/69552). We do not sell that capability on any platform, so on WebinarJam it costs you nothing you would otherwise have had.

## What is actually different between the WebinarJam and EverWebinar APIs?

Less than the two product pages suggest. They share an API host, a credential, an autoresponder engine and a Zapier app, so the positive-versus-negative trigger behaviour, the approval process, the rate limit and the phone fields are the same on both. One approval covers both products, which means nobody fills the form in twice.

*WebinarJam and EverWebinar, on the questions that decide an integration*

| Question | WebinarJam | EverWebinar |
| --- | --- | --- |
| API credential | One application, approved by hand | The same key: one set covers both products |
| Registration event | Positive trigger, fires as the event occurs | Identical |
| Live join event | Positive trigger, fires as the event occurs | Identical |
| Mid-session exit | Negative trigger, evaluated after the session concludes | Identical |
| Phone on the registration form | phone_country_code and phone, both first-class fields | Identical |
| Rate limit | 20 API calls per second per user | Identical |
| What genuinely differs | Scheduled live sessions | Automated sessions: changes the timing model, not the integration |

So “EverWebinar versus WebinarJam” is not an integration question at all. It is a question about how much time exists between somebody registering and the session starting, and that is answered on [evergreen webinars](https://callhush.com/evergreen-webinars), not here. The trigger-name trap that catches buyers on the automated side is written up on [the EverWebinar page](https://callhush.com/platforms/everwebinar).

- **1 key**: One approved credential covers both WebinarJam and EverWebinar (Source: [WebinarJam support: Apply for an API key](https://support.webinarjam.com/en/articles/15370143-apply-for-an-api-key-for-webinarjam-or-everwebinar))
- **20 / sec**: Hardcoded API calls per second per user, with a queue recommended by the vendor to stay under it (Source: [WebinarJam support: Connect to the WebinarJam or EverWebinar API](https://support.webinarjam.com/support/solutions/articles/153000168633-connect-to-webinarjam-or-everwebinar-api))

## How do I get WebinarJam API access, and how long does it take?

It is not self-serve, and the queue in front of it is the only part of a WebinarJam setup with a calendar dependency. Better started in week one than discovered in week three.

1. **Submit the API key application**: Approval is required before the WebinarJam or EverWebinar API can be used, access is available to paid subscribers only, and requests are typically processed within two business days. The application asks what the app is, how it uses the API, whether it subscribes users, and where your contact data comes from.
2. **Confirm the phone field is switched on and read what sits beside it**: phone_country_code and phone are first-class fields, and the vendor notes both might be required depending on the settings for each webinar. What the form says next to that field, who is being consented to, and whether an artificial voice is mentioned, is a legal question rather than a technical one, and it is settled before anything sends.
3. **Point the custom webhook at us, on the positive triggers only**: Registration and live attendance are positive triggers and are executed as soon as the event occurs. Nothing is configured against the negative triggers, because a message that arrives after the session has ended is a follow-up, not a reminder.
4. **Throttle outbound calls under the published ceiling**: The API is hardcoded at 20 calls per second per user, and the documentation recommends a queue that throttles all outbound calls to that rate rather than absorbing 429s. This is an implementation note, not a scheduling risk.

None of the above is a claim about how fast anything of ours happens. We publish no timing figures anywhere on this site, because no webinar platform publishes a webhook delivery guarantee to measure one against.

## If there is no live leave signal, what still works on WebinarJam?

The part that decides the number you care about. Registration and people who show up are completely different topics, and attendance is settled before the session opens: which is exactly where WebinarJam is strong. A pushed registration event, a real phone field, and a live join signal that stops us contacting somebody already watching.

The piece with the strongest evidence behind it needs no platform event at all: a call before the session that gets the registrant to say, in their own words, when they will join and what they will be doing right before. It runs off your session time and our own timer, so it behaves the same here as anywhere else in the matrix. That is the micro-commitment, and it is the mechanism we sell rather than any particular channel.

- **3 of 5**: Capabilities in our matrix WebinarJam answers with a plain yes, including the phone number on the form
- **0**: Platform events required by the call before the session: the piece with the strongest evidence behind it

The people who walked out mid-session are not abandoned either. They are picked up after the event with everybody else who did not stay, from attendance data that does arrive: which is a follow-up rather than a rescue, and we would rather call it what it is. The ranked tactics, with the evidence behind each one marked, are on [how to increase webinar attendance](https://callhush.com/increase-webinar-attendance).

You run a webinar. We come in and increase your show-up rate and your post-webinar sales, with our AI voice and SMS system: and you finally know why every registrant signed up. The whole table is on [platforms](https://callhush.com/platforms), the sister product is covered on [EverWebinar](https://callhush.com/platforms/everwebinar). The two platforms whose limitations look least like this one are [StealthSeminar](https://callhush.com/platforms/stealthseminar), where a leave event exists but nobody has published when it fires, and [BigMarker](https://callhush.com/platforms/bigmarker), where the blocker is the phone field rather than any webhook. The way we ask to be measured is [the pilot](https://callhush.com/pilot). If that is worth twenty minutes, [book a call](https://ainora.lt/contact?from=callhush).

## Frequently asked questions

### Does WebinarJam have a webhook for an attendee leaving?

Not one that fires during the session. “If they leave early” sits on WebinarJam's negative-trigger list, and its own automation documentation says negative triggers are evaluated after the webinar session concludes. There is no configuration that changes this, and we would rather you read that sentence on the vendor's page than take our word for it.

### Could you poll the API for exit times instead?

There is nothing to poll. The documented registrant and attendee fields include entered_live and time_live, an entry time and a duration watched, and no exit timestamp. A polling design needs a field that changes; this one does not exist.

### Zapier lists a “Registrant Leaves Before” trigger. Doesn't that contradict all this?

It proves the trigger exists, not that it fires during the session. Zapier describes it as triggering when a registrant leaves the live webinar before a specific timestamp, but the underlying evaluation is the same negative trigger the vendor documents as post-session. A trigger name is the easiest thing in this category to mistake for a capability.

### Is WebinarJam's API self-serve?

No. Approval is required before you can use it, access is available to paid subscribers only, and applications are typically processed within two business days. One approved credential covers both WebinarJam and EverWebinar, so it is one application rather than two.

### Is EverWebinar a better choice if I want more of this to work?

Not on any of these questions: the two share an API host, a credential, an autoresponder engine and a Zapier app, so the answers are identical. What differs is scheduled sessions versus automated ones, which changes how much time exists between registration and the session rather than what the integration can see.

### So is WebinarJam a bad platform to run this on?

No. It answers three of the five columns in our matrix with a plain yes, including the phone number on the registration form, which is the one nothing works without. The capability it cannot support is the one we decline to sell on every platform, including the platform that technically has it.

---

CallHush is operated by AINORA, MB (Vilnius, Lithuania). Book a call: https://ainora.lt/contact?from=callhush