Meetily
Agent APIGuides

Record on a calendar event

Start recording when a meeting begins and stop when it ends, driven by an external trigger.

This captures audio

Starting a recording captures real audio and fires the app overlay. Only automate this for meetings the participants know are being recorded, and get their consent. Scope the token to record only.

This recipe starts a recording when a calendar event begins and stops it when the event ends. The trigger (a calendar integration, a cron job, or a scheduler) is yours; this page shows the Meetily calls it makes.

Start at the event start

When your trigger fires at the event's start time, call the recording start endpoint.

curl -s -X POST http://127.0.0.1:8420/v1/recording/start -H "Authorization: Bearer $MEETILY_PRO_TOKEN" -H "content-type: application/json" -d '{"meeting_name":"Weekly sync"}'

Stop at the event end

When your trigger fires at the event's end time, call the recording stop endpoint.

curl -s -X POST http://127.0.0.1:8420/v1/recording/stop -H "Authorization: Bearer $MEETILY_PRO_TOKEN"

Confirm it started

To be sure capture began before you rely on it, wait for the recording.started event (a one-shot SSE stream).

curl -N -s "http://127.0.0.1:8420/v1/recording/wait?until=started" -H "Authorization: Bearer $MEETILY_PRO_TOKEN"

Remote triggers need pre-arm

If your trigger runs on another device over the LAN rather than on the Meetily machine, a remote recording start is refused with 403 not_prearmed unless remote_recording_prearmed is set. See Pairing and LAN access. Running the trigger on the same machine over loopback avoids this.

Always run the Capability Preflight first so the trigger fails cleanly if Meetily is not running.

Last updated on

On this page