Clarification request: call_log_id timeline and /phone/call_logs/{callLogId}/recordings deprecation status

Phone
, ,
1

Hello Zoom Developer Support Team,

We are currently migrating from legacy Call Log APIs/webhooks to Call History/Call Element.

Background
We reviewed the Zoom Phone changelog and migration guide, and we also received a direct reminder email about the Call Log deprecation timeline.
We understand migration is required, but we still need exact field-level and endpoint-level dates to finalize our production rollout safely.
References:

Why exact dates matter for us

  • We currently store call_log_id as a unique relation key in our DB (relationDataId).

  • We also use GET /phone/call_logs/{callLogId}/recordings in production workflows (periodic status reconciliation and transferred-call recording retrieval).
    Because of this, field-level and endpoint-level timeline differences can directly impact production data linkage and recording ingestion.

Could you please clarify the following with exact dates (UTC), if possible?

  1. Webhook payload fields (call_log_id)

    • When will call_log_id be removed from webhook payloads (if planned)?

    • If timelines differ by event family, please specify separately (call_log, call_history, call_element).

  2. API response fields in call_log / call_path

    • For APIs planned to change in November 2026, when exactly will IDs inside call_log or call_path be removed (if planned)?

    • Will there be any grace period where both old and new fields are returned?

  3. GET /phone/call_logs/{callLogId}/recordings

    • Is this endpoint planned for deprecation/sunset?

    • If yes, what is the exact deprecation/sunset date and the recommended replacement endpoint?

We mainly need timeline and replacement confirmation so we can complete migration without production impact.

Thank you very much.

2

@elisa.zoom @joan.zoom
Thank you as always.

Apologies for the additional question, but I wanted to check if there have been any updates on my previous inquiry.

This information is important for our implementation decisions, so I would greatly appreciate it if you could prioritize reviewing and responding when possible.

Thank you for your support.