# Call direction discrepancy between call log and recording endpoints **URL:** \ **Category:** Phone\ **Created:** [May 22, 2024, 4:06pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495 "2024-05-22T16:06:50Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![dlzoomdev](https://avatars.discourse-cdn.com/v4/letter/d/cdc98d/32.png) [@dlzoomdev](https://devforum.zoom.us/u/dlzoomdev)\ **Post date:** [May 22, 2024, 4:06pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/1 "2024-05-22T16:06:50Z")
We use zoom’s phone API to retrieve recordings and call logs. We noticed that the direction in the recording response differs from the response for the pertaining call log for the same call log id. Why is this? We should have the same direction on both responses; which one is correct and how can we work round this? Recording response: (from /phone/recordings) ```auto { "id": "recording_123", "caller_number": "caller_123", "caller_number_type": 2, "caller_name": "caller_name_123", "callee_number": "callee_123", "callee_number_type": 1, "callee_name": "Foo Bar", "direction": "outbound", "duration": 292, "download_url": "download_url_foobar", "file_url": "file_url_foobar", "date_time": "2024-05-21T09:48:07Z", "recording_type": "Automatic", "call_log_id": "call_log_123", "call_id": "call_123", "owner": { "type": "user", "id": "user_123", "name": "Foo Bar", "extension_number": 1234567890 }, "site": { "id": "site_123" }, "end_time": "2024-05-21T09:52:59Z", "disclaimer_status": 0 } ``` Call log response: ```auto { "id": "call_log_123", "user_id": "user_123", "call_type": "voip", "caller_number": "caller_phone_number_123", "caller_number_type": 2, "caller_number_source": "external", "caller_location": "United Kingdom", "callee_user_id": "callee_user_id_123", "callee_number": "callee_phone_number_123", "callee_number_type": 1, "callee_name": "Foo Bar", "direction": "inbound", "duration": 293, "result": "Auto Recorded", "date_time": "2024-05-21T09:48:05Z", "path": "pstn", "site": { "id": "site_123", "name": "site-name-foo-bar" }, "recording_id": "recording_123", "recording_type": "Automatic", "has_voicemail": false, "call_id": "call_123", "owner": { "type": "user", "id": "owner_123", "name": "Foo Bar", "extension_number": 1234567890 }, "caller_country_code": "44", "caller_country_iso_code": "GB", "callee_did_number": "callee_phone_number_123", "callee_country_code": "44", "callee_country_iso_code": "GB", "answer_start_time": "2024-05-21T09:48:06Z", "call_end_time": "2024-05-21T09:52:59Z", "department": "dept_123", "cost_center": "" } ``` ---
**Author:** ![dlzoomdev](https://avatars.discourse-cdn.com/v4/letter/d/cdc98d/32.png) [@dlzoomdev](https://devforum.zoom.us/u/dlzoomdev)\ **Post date:** [June 7, 2024, 10:02am UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/2 "2024-06-07T10:02:21Z")
Is anyone still available to answer this query? ---
**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\ **Post date:** [June 13, 2024, 3:46am UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/3 "2024-06-13T03:46:23Z")
Hi @dlzoomdev , not sure for this. What is the complete call path? ---
**Author:** ![dlzoomdev](https://avatars.discourse-cdn.com/v4/letter/d/cdc98d/32.png) [@dlzoomdev](https://devforum.zoom.us/u/dlzoomdev)\ **Post date:** [June 14, 2024, 2:40pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/5 "2024-06-14T14:40:15Z")
Hi @gianni.zoom Thanks for getting back to me. The first payload is the response for `/phone/call_logs/:id/recordings` and the second payload is the response for `/phone/call_logs/:callLogId`. Would it be possible to have a private call to help you diagnose this further? ---
**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\ **Post date:** [June 14, 2024, 8:52pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/6 "2024-06-14T20:52:26Z")
Hi @dlzoomdev , can you please review this document: > **[Understand Zoom Phone call history](https://developers.zoom.us/docs/zoom-phone/understanding-call-history/)** > > The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform. It speaks to getting the call path which may be able to illuminate for the behavior you’re seeing. If it still does not line up after then, we can figure out next steps for clarity. ---
**Author:** ![dlzoomdev](https://avatars.discourse-cdn.com/v4/letter/d/cdc98d/32.png) [@dlzoomdev](https://devforum.zoom.us/u/dlzoomdev)\ **Post date:** [June 18, 2024, 5:47pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/7 "2024-06-18T17:47:37Z")
Hi @gianni.zoom I used the old endpoint `/phone/call_logs/:callLogId` as well as the new endpoint `/phone/call_history/{callLogId} ` and both of the them share the same discrepancy; they both show the call direction as `inbound` but `/phone/call_logs/:id/recordings` shows the same call as having a direction of `outbound`. I would like to request a further investigation - can we figure out what steps we need to take? ---
**Author:** ![dlzoomdev](https://avatars.discourse-cdn.com/v4/letter/d/cdc98d/32.png) [@dlzoomdev](https://devforum.zoom.us/u/dlzoomdev)\ **Post date:** [June 28, 2024, 3:39pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/8 "2024-06-28T15:39:21Z")
Hi @gianni.zoom Can we get an update on this issue we reported please? It would be good to have a private chat with you or another of your peers to disucss this further as there may be information to be shared to assist you further. Cheers, ---
**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\ **Post date:** [July 9, 2024, 3:26pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/9 "2024-07-09T15:26:11Z")
Hi @dlzoomdev , Yes please provide the following in the private message I’m initiating (check notifications) and I will escalate accordingly: - client id - dev email associated with credentials making API request - API response zm-tracking-id (found in the response headers) from all responses - screenshots of call direction fields ---
**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\ **Post date:** [July 15, 2024, 2:59pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/10 "2024-07-15T14:59:11Z")
Hi @dlzoomdev , thanks for providing the info needed to test! This is being investigated internally and I will share more updates as they become available (ZSEE-135322). ---
**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\ **Post date:** [July 23, 2024, 8:01pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/11 "2024-07-23T20:01:50Z")
Followed up with service engineering on this. Still waiting to hear back. ---
**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\ **Post date:** [November 25, 2024, 5:28pm UTC](https://devforum.zoom.us/t/call-direction-discrepancy-between-call-log-and-recording-endpoints/110495/12 "2024-11-25T17:28:40Z")
From developer: Apologies for the late response, it’s been a busy one on my side! We were anticipating that we may communicate this discrepancy a bit better but we opted to instead work round the issue by prioritising the call log’s direction first, else use the recording’s direction itself. This was coded a few months ago and since then we are not aware of any regression in call direction since.