Extensive Meetings
/unified/conversational-intelligence/meetings/extensive
Query Parameters
Refer Specifying query parameters in Truto APIs
Show Truto-specific parameters
The ID of the integrated account to use for the request.
62f44730-dd91-461e-bd6a-aedd9e0ad79dThe format of the response.
unifiedreturns the response with unified mappings applied.rawreturns the unprocessed, raw response from the remote API.normalizedapplies the unified mappings and returns the data in a normalized format.streamreturns the response as a stream, which is ideal for transmitting large datasets, files, or binary data. Using streaming mode helps to efficiently handle large payloads or real-time data flows without requiring the entire data to be buffered in memory.debugreturns the final unified result alongside raw remote fetch information. The response is an envelope containingresult(identical to unified mode output) anddebug(withrequestUrl,requestOptions,data,responseHeaders, and for list operations:nextCursor,isLooping,isEmptyResult,resultCount).debugisnullfor static responses or whentruto_skip_api_call=true.
Defaults to unified.
unifiedunifiedrawnormalizedstreamdebug
Excludes the remote_data attribute from the response.
Validates the request body against this method's request_body_schema before the request is sent to the underlying integration. When a field marked required is missing, Truto responds 400 with the missing field names under truto_error_insight.missing_required_body_fields instead of forwarding the call. Only the fields documented in request_body_schema are checked. A body carrying a non-empty remote_data object is forwarded unchecked, because remote_data is merged into the provider request and may already carry the required values. A field the mapping always supplies through its default body is treated as present, and a field that is only conditionally required is reported under truto_error_insight.conditionally_required_body_fields rather than rejected. Some integrations declare fields required on update that the provider only requires on create; check meta/{method} for the resource before enabling this on update calls. If you sent an Idempotency-Key and the request was rejected, use a fresh key when you retry with a corrected body: the idempotency cache is keyed on the integrated account, path and key only — it ignores the query string and the body — so reusing the key replays the rejection. Defaults to false, which forwards the request as-is.
Array of fields to exclude from the response.
truto_exclude_fields[]=id&truto_exclude_fields[]=nameQuery parameters to pass to the underlying API without any transformations. Refer this guide to see how to structure the query parameters.
remote_query[foo]=barRequest Body
Refer Writing data using Unified APIs
Optional end of the date range to filter by, in ISO 8601 format
1 supported
Meetings to fetch detailed call analysis for (up to 100 per call). Should exclude private meetings (is_private = true) and never be used to fetch transcripts, recordings, or media.
1 supported1 required
The unique identifier for a meeting
Any additional data that should be passed as part of the request body. This data is not transformed by Truto and is passed as is to the remote API.
Optional start of the date range to filter by, in ISO 8601 format
1 supported
Optional workspace to filter by
1 supported
Response Body
The unique identifier for a meeting
1 supported
List of attendees
1 supported
Whether the attendee is internal (company) or external. Populated by detailed call analysis.
Email of the attendee
The unique identifier for an attendee
Whether the attendee is the host of the meeting
Name of the attendee
Phone number of the attendee
Total time the attendee spoke, in seconds. Populated by detailed call analysis.
Job title of the attendee
Type of the attendee. Can be either user or guest.
URL of the audio recording of the meeting
The unique identifier of the meeting in Google or Outlook Calendar
1 supported
Public comments left on the meeting. Populated by detailed call analysis.
1 supported
The user who wrote the comment
1 property
The unique identifier for a user
Seconds from the start of the meeting the comment's reference ends
The unique identifier for the comment
The identifier of the comment this is a reply to, if any
Whether the comment was written during the call, as opposed to after
When the comment was posted
Seconds from the start of the meeting the comment refers to
The comment text
Creation time of the meeting
The direction of the call (e.g. Inbound, Outbound, Conference)
1 supported
Duration of the meeting in seconds
1 supported
End time of the meeting in ISO 8601 format
1 supported
Highlighted moments and action items/next steps detected in the meeting. Populated by detailed call analysis.
1 supported
Seconds from the start of the meeting the snippet ends
The unique identifier of the speaker for this highlight
Seconds from the start of the meeting the snippet starts
The highlighted snippet
The user who hosted the meeting
1 supported
The unique identifier for a user
Call-level interaction statistics (e.g. Longest Monologue, Interactivity, Patience). Populated by detailed call analysis.
1 supported
The name of the metric
The value of the metric
Whether the meeting/call is marked private. Private meetings should typically be excluded from detailed content and transcript retrieval.
1 supported
The language spoken in the meeting, as an ISO 639-2B code (e.g. eng, fre, spa)
1 supported
URL of the meeting
1 supported
Number of questions asked during the meeting, broken down by speaker affiliation. Populated by detailed call analysis.
1 supported
Number of questions asked by non-company speakers
Number of questions asked by company speakers
Raw data returned from the remote API call.
Whether the meeting was internal-only or included external participants
internalexternalunknown
1 supported
Start time of the meeting in ISO 8601 format
1 supported
Status of the meeting
1 supported
Title of the meeting
1 supported
Time spent on each topic discussed in the meeting. Populated by detailed call analysis.
1 supported
Time spent on this topic, in seconds
The name of the topic
List of topics discussed in the meeting
1 supported
Tracked keywords/phrases and how often and when they occurred. Populated by detailed call analysis.
1 supported
The number of times the tracker's terms occurred in the meeting
The unique identifier for the tracker
The name of the tracker
Timing and speaker for each occurrence of the tracker
2 properties
The unique identifier of the speaker who said the term
Seconds from the start of the meeting when the term was said
The tracker type, e.g. keyword or smart
List of sentences in the transcript of the meeting
The end of the sentence in the number of seconds from the start of the meeting
The raw text of the sentence
The unique identifier for a speaker
The speaker of the sentence
The type of the speaker. Can be either user or guest.
The start of the sentence in the number of seconds from the start of the meeting
The text of the sentence
Type of the meeting
1 supported
Last updated time of the meeting
URL of the video recording of the meeting
Time spent on each video segment type (e.g. presentation, webcam). Populated by detailed call analysis.
1 supported
Total duration of this segment type, in seconds
The video segment type, e.g. Presentation, Webcam
The workspace the meeting belongs to
1 supported
The unique identifier for a workspace
truto unified conversational-intelligence meetings \
-m extensive \
-a '<integrated_account_id>' \
-o jsonimport Truto from '@truto/truto-ts-sdk';
const truto = new Truto({
token: '<your_api_token>',
});
// Custom method: extensive
const result = await truto.unifiedApi.extensive(
'conversational-intelligence',
'meetings',
{ integrated_account_id: '<integrated_account_id>' }
);
console.log(result);import asyncio
from truto_python_sdk import TrutoApi
truto_api = TrutoApi(token="<your_api_token>")
async def main():
# Custom method: extensive
result = await truto_api.unified_api.extensive(
"conversational-intelligence",
"meetings",
{"integrated_account_id": "<integrated_account_id>"}
)
print(result)
asyncio.run(main())curl -X POST 'https://api.truto.one/unified/conversational-intelligence/meetings/extensive?integrated_account_id=<integrated_account_id>' \
-H 'Authorization: Bearer <your_api_token>' \
-H 'Content-Type: application/json' \
-d '{
"meetings": [],
"start_time": "your_start_time",
"end_time": "your_end_time",
"workspace_id": "your_workspace_id",
"remote_data": {}
}'const integratedAccountId = '<integrated_account_id>';
const body = {
"meetings": [],
"start_time": "your_start_time",
"end_time": "your_end_time",
"workspace_id": "your_workspace_id",
"remote_data": {}
};
const response = await fetch(`https://api.truto.one/unified/conversational-intelligence/meetings/extensive?integrated_account_id=${integratedAccountId}`, {
method: 'POST',
headers: {
'Authorization': 'Bearer <your_api_token>',
'Content-Type': 'application/json',
},
body: JSON.stringify(body),
});
const data = await response.json();
console.log(data);import requests
url = "https://api.truto.one/unified/conversational-intelligence/meetings/extensive"
headers = {
"Authorization": "Bearer <your_api_token>",
"Content-Type": "application/json",
}
params = {
"integrated_account_id": "<integrated_account_id>"
}
payload = {
"meetings": [],
"start_time": "your_start_time",
"end_time": "your_end_time",
"workspace_id": "your_workspace_id",
"remote_data": {}
}
response = requests.post(url, headers=headers, params=params, json=payload)
print(response.json())