Which field uniquely identity the items inside -v1/cdr_feed

[mvcsharepointdev]

I am calling this API end point:-

--url https://analytics.webexapis.com/v1/cdr_feed?endTime=&startTime= \

and i am saving the records inside my own Database. but i am not sure which field uniquely identity the items? so incase i run multiple calls, to know if i need to add the record or update if the field was already added from a previous run ? for example can i depend on the  ReportID,, or there is another field ??

Thanks

[mvcsharepointdev]

@Janos Benyovszki thanks for the reply, but the api did not return such as field named as "callRecordingId" any advice? the fields are:-

Answer time

Answered

Direction

Called line ID

Call ID

Calling line ID

Start time

Call type

Client type

Client version

Correlation ID

International country

Device MAC

Duration

Inbound trunk

Org UUID

Original reason

OS type

Outbound trunk

Redirect reason

Related reason

Report ID

Report time

Route group

Site main number

Site timezone

Sub client type

User UUID

User type

User

Called number

Calling number

Location

Dialed digits

Releasing party

Redirecting number

Site UUID

Department ID

Transfer related call ID

Authorization code

Model

Local SessionID

Remote SessionID

Call transfer time

Local call ID

Remote call ID

Network call ID

Related call ID

User number

Call outcome

Call outcome reason

Ring duration

Answer indicator

Release time

Final local SessionID

Final remote SessionID

PSTN legal entity

PSTN vendor org ID

PSTN vendor name

PSTN provider ID

External customer ID

Redirecting party UUID

Public Calling IP Address

Public Called IP Address

Caller ID number

External caller ID number

Device owner UUID

Call Recording Platform Name

Call Recording Result

Call Recording Trigger

[Jeff Marshall]

I think Janos may have meant the Report ID field. The description for each field can be found on https://help.webex.com/en-us/article/nmug598/Reports-for-Your-Cloud-Collaboration-Portfolio?_gl=1*krhtm3*_gcl_au*MjExMDQzMTA3OC4xNzU1ODcwNTgzLjE4OTI2MzkxNzMuMTc1NjE0OTc0Ni4xNzU2MTQ5NzQ2#WxC-detailed-call-history-report. Each leg of a call should contain the same Report ID so you can use that to group different records together to indicate if they were part of the same call. 

[mvcsharepointdev]

@Jeff Marshall thanks ,, so the report ID will not uniquely identify each item inside the API call? so if i call the same API twice will i get the same report ID? BTW i generated the yesterday report and there is not any 2 items with the same report ID.. i am looking at a unique id for each item not just something to group the items 

[Jeff Marshall]

Sorry, I was mistaken. Report ID will be unique for each record and Correlation ID can be used to group them. The Report ID should remain the same on a record regardless of how many times you pull data for a specific time period. 

[Janos Benyovszki]

@mvcsharepointdev 

To uniquely identify the items retrieved from the Get Detailed Call History API, you can use the callRecordingId field. This field is a unique identifier for call recordings in Webex Calling and can be used to determine whether a record already exists in your database.

Steps to ensure unique identification:

1. Retrieve the call detail records using the API endpoint.
2. Check the callRecordingId field for each record.
3. Before adding a new record to your database, verify if the callRecordingId already exists.
4. If the callRecordingId exists, update the existing record; otherwise, add the new record.

This approach will help you manage the records efficiently and avoid duplicates.

Also wanted to let you know about our new AI Assistant, available on our Developer Portal. To open it click on the blue circle next to your profile image or use this address developer.webex.com/?ai-assistant-is-docked-window=true and to find out more about our AI Assistant, go to developer.webex.com/admin/docs/webex-aI-assistant-for-developers . It’s a great tool for quickly finding information, answering common questions, or navigating resources. Of course, if you need more detailed assistance, our support team is always here to help. Feel free to give it a try!