Hi @Sanket. The post_recording.completed event fires once per meeting/webinar instance, after the host ends the meeting and the recording has been processed/uploaded to cloud. This is also when the recording “becomes available to view or download.” It does not fire once per start/stop segment inside the same meeting
If you stop and restart recording during a live meeting, you’ll still only get one post_recording.completed for that instance. To enumerate all segments/files created during that meeting, call GET /meetings/{meetingUUID}/recordings after you receive the webhook (remember to double-encode UUIDs that start with / or contain //).
If you actually end and restart the meeting (a new instance), Zoom will generate a new meeting UUID and you’ll get a separate post_recording.completed for that new instance. You can list all UUIDs tied to a meeting ID with GET /past_meetings/{meetingId}/instances
For earlier awareness of mid-meeting stops/starts, you can also subscribe to post_recording.stopped and reconcile when the final post_recording.completed arrives.