Conversation Outcome Mapping Trends
Changed onGet conversation outcome category / sub category counts over time, split into contiguous windows so the result can be rendered as a trend/bar chart.
The window size is derived from the requested period:
-
≤ 2 days → 6-hour windows
-
≤ 14 days → daily windows
-
≤ ~1 month → weekly windows
-
> 1 month → monthly windows
-
template: Outcome mapping template to bucket outcomes by.
-
start / end: ISO 8601 range. end is exclusive; each window's end field is its last second (e.g. ...T23:59:59Z).
-
timezone: IANA timezone the day/month/6-hour bars align to (local calendar); defaults to UTC. Weekly bars are always anchored to start.
-
assistantIds: Optional, repeatable. Falls back to the template's saved assistantIds, then to all assistants.
Returns an empty list if the team has no outcome mapping configured yet, or if the given range is missing or empty.
Request
- Base URLhttps://api-qa.interactly.ai
- URLhttps://api-qa.interactly.ai/campaigns/v1/stats/outcomes/{template}/trends
- AuthHTTP bearer
Path parameters
Outcome mapping template to bucket outcomes by
Query parameters
IANA timezone (e.g. 'Asia/Kolkata') that day/month/6-hour bars align to; defaults to UTC.
Restrict to these assistants. Repeat: ?assistantIds=<id1>&assistantIds=<id2>.
Number of items per page
Page number
Search keywords
Filter by start time (ISO 8601 format)
Filter by end time (ISO 8601 format)
Response
Conversation outcome category / sub category counts bucketed into time windows
Example response
{
"message": "Stats fetched successfully."
}Changes
- info
added the new optional
queryrequest parameterassistantIds
- info
- info
added the new enum value
template_v2to thepathrequest parametertemplate
- info