BigMarker's GET /api/v1/conferences/:conference_id returns recording_duration — the actual recording length in seconds — once a webinar has ended and a recording exists. The connector does not sync it.

There is also GET /api/v1/conferences/:conference_id/recording, exposing duration, recording_status, published, download_ready and filesize.

Either works for us: add recording_duration to conference, or add the recording endpoint as a new table.

Why we need it

We currently estimate recording length from the longest observed watch time. That works, but it drifts as more people watch and is unreliable for newly launched webinars, which are the ones we most need to evaluate.

Source confirmation

BigMarker's Director of Customer Strategy has confirmed both fields are available and has offered to involve their integrations team.