Skip to Content
Call AnalyticsCall Detail

Call Detail

GET/api/app/public-calls/call
Returns the information and analysis results of a single call. Only calls that belong to the token owner's tenant can be queried.

If you know a call’s callId (for example from the Call Analysis Completed webhook or the Call Records response), you can fetch that call directly with this endpoint instead of scanning the whole list.

Query Parameters

FieldTypeRequiredDescription
callIdstring (UUID)YesID of the call to query. This is the callId value from the webhook payload or the Call Records response.

Example cURL

curl --request GET 'https://public-api.thinkvoice.ai/api/app/public-calls/call?callId=019e925a-5f79-7778-b0be-a45a146cf828' \
--header 'Authorization: Bearer <ACCESS_TOKEN>'

Responses

200Success
{ "callId": "019e925a-5f79-7778-b0be-a45a146cf828", "customerId": "11111111-2222-3333-4444-555555555555", "customerPhoneNumber": "+905xxxxxxxxx", "callDate": "2026-04-10T14:35:12", "queueName": "Musteri Hizmetleri", "topic": "Odeme", "subTopic": "Iade > Gecikme", "resolutionStatus": "Cozuldu", "title": "Iade sureciyle ilgili sikayet", "summary": "Musteri, [MASKED] numarasi icin iade surecinin geciktigini belirtti.", "callIssueType": "Şikayet", "newRequestInfo": null, "direction": 1, "directionName": "Giden", "resultId": 1, "resultName": "Cevaplandı", "hangupDirectionId": 1, "hangupDirectionName": "Müşteri", "endTime": "2026-04-10T14:41:47", "answerTime": "2026-04-10T14:35:20", "callDurationSeconds": 387.5, "queueWaitSeconds": 12, "personnelId": "22222222-3333-4444-5555-666666666666", "personnelName": "Ayşe Yılmaz", "agentId": "agent-42", "agentName": "İade Botu", "analysis": [ { "key": "musteri_memnuniyeti", "friendlyName": "Müşteri Memnuniyeti", "value": "Olumlu" } ], "metadata": { "ref_id": "q_6876" }, "recordUrl": "https://public-api.thinkvoice.ai/api/app/public-calls/019e925a-5f79-7778-b0be-a45a146cf828/record" }

The response body is a single object with the same fields as the items entries in the Call Records response; see the Response Fields table on that page for field descriptions. The difference: in the Call Detail response the analysis field is always populated (in Call Records it is populated only when includeAnalysis: true). The body is not wrapped in an items list as in Call Records.

401Token is invalid or missing
{ "error": "invalid_token" }
403Call not found
{ "error": { "code": null, "message": "Belirtilen call_id değerine ait çağrı bulunamadı.", "details": null, "validationErrors": null } }
429Rate limit exceeded. The limit is 40 requests per 60 seconds.
Retry-After: 60

Error Cases

CaseHTTPDescription
Missing or invalid token401The Authorization header is missing, invalid or expired.
Call not found403Returned if the callId is wrong or the call belongs to another tenant. A call from another tenant is never returned under any circumstances.
Invalid callId format400callId is not a valid UUID.

Call Detail only returns meaningful results for calls whose analysis is complete. For a call whose analysis has not finished, fields such as topic, summary and resolution status may be empty. We recommend waiting for the webhook notification sent when the call analysis completes and querying afterwards.

You can download the call recording from the recordUrl in the response. See the Call Recording page for details.

Last updated: