Query Observability Conversations
Changed onQuery production conversations for this organization.
Omit group_by for rows, newest first, each with metric_results. Set it for counts per group: by status, agent, label, day, interface, direction, ended_by, a metadata_path, or metric_value for how a metric came out. Filters apply either way, so one narrowing answers both "show me" and "how many".
Request
- Base URLhttps://api.getbluejay.ai
- URLhttps://api.getbluejay.ai/v1/observability/conversations
- AuthHTTPBearer (a scheme the document does not define)
Query parameters
e.g. COMPLETED, SYSTEM_ERROR
inbound, outbound
E.164
Minimum duration in ms
Maximum duration in ms
Keep conversations linked to any of these issue IDs
Label text, resolved to an id
Metadata key, e.g. restaurant_code
Required when group_by is metric_value
Keep only conversations whose metric came out one of these values. Needs metric_name or metric_id. This is the filter, not the grouping.
Numeric metrics: keep results at or above this
Numeric metrics: keep results at or below this
Omit for rows; set for counts
Headers
API key required to authenticate requests.
Response
Successful Response
Changes
- info
added the new optional
queryrequest parameterissue_ids
- info
- info
added the optional property
//to the response with the status
- info