Call Records
Request Body
{
"startTime": "2026-04-01T00:00:00",
"endTime": "2026-04-10T23:59:59",
"skip": 0,
"take": 20,
"sortColumn": "start_time_dt",
"isAscending": false,
"issueTypeNames": ["Şikayet", "Teknik Sorun"],
"hasNewRequest": true,
"direction": 1,
"results": [1],
"includeAnalysis": false
}Text values in the examples (call types, queue names, labels such as directionName or resultName) are shown as they are returned for a Turkish-speaking tenant. Field names and the payload structure are the same for every tenant.
Parameters
The sum of skip + take cannot exceed 10,000. If it does, the system automatically reduces the page size.
Only calls whose analysis is complete are listed. A call that is still being analyzed does not appear in the results until its analysis finishes.
issueTypeNames values are matched against the Value or Description fields of the call type catalog in the system. An undefined value returns an error.
The results field has a different default behavior: if it is not included in the request at all, only calls with the Answered status are returned. To see all results, send "results": null.
Validation Errors
In the following cases, 400 Bad Request is returned in the standard ABP validation error format:
- The request body is empty (
requestis null) startTimeis later thanendTimeskipis negativetakeexceeds the applicable maximum (includeAnalysis: false → 500, true → 100)
Date and Time Behavior
The returned callDate value may be converted according to the user’s time zone setting. The integration team should agree on a single convention when sending dates.
| Recommendation | Description |
|---|---|
| ISO 8601 | Send all dates in the 2026-04-01T00:00:00 format |
| Time zone convention | Agree within your team whether UTC or Europe/Istanbul will be used |
Example cURL
curl --request POST 'https://public-api.thinkvoice.ai/api/app/public-calls/get-calls' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' --header 'Content-Type: application/json' --data-raw '{
"startTime": "2026-04-01T00:00:00",
"endTime": "2026-04-10T23:59:59",
"skip": 0,
"take": 20,
"isAscending": false,
"issueTypeNames": ["Şikayet", "Teknik Sorun"],
"hasNewRequest": true,
"direction": 1,
"results": [1],
"includeAnalysis": false
}'Responses
Because includeAnalysis: false was sent in the example above, analysis is returned as an empty array. If includeAnalysis: true is sent, each item is populated with analysis parameters in the { key, friendlyName, value } form, for example: [{ "key": "musteri_memnuniyeti", "friendlyName": "Müşteri Memnuniyeti", "value": "Olumlu" }].
Response Fields
For the steps to download the recording using recordUrl, see the Call Recording page.
Data Security and Masking
The following information is masked in the call title (title), summary (summary) and new request text (newRequestInfo):
| Data | Behavior |
|---|---|
| Phone number | Returned as [MASKED] if it appears in text fields. The customer’s number is returned only in the customerPhoneNumber field. |
Returned as [MASKED] | |
| National ID (TCKN) | Returned as [MASKED] |
The callId field is the call’s own identifier and is not considered sensitive data like a phone number — it is returned as plain text in the response.