Get a time series metric

threadTimeSeriesMetric returns a metric as one value per time bucket, such as threads created per day or median first response time per week. Use it for line and bar charts.

For TypeScript, the GraphQL SDK gives you a fully typed client for these operations.

This query requires the metrics:read permission, or metricsAgent:read for agent_ metrics. See Permissions.

Get a time series

input takes these fields:

metricName: any time series metric from the metrics reference
from and to: the date range, in UTC. See Dates and time zones
interval: the bucket size, with unit set to HOUR, DAY, WEEK, MONTH, QUARTER, or YEAR
mode: METRIC for values, or THREAD_IDS for the threads behind them
percentile: for duration metrics, an integer from 1 to 99. Defaults to 50
filters and groupBy: see Filter and group reporting queries

This query returns the daily 90th percentile first response time for email and Slack threads in September, split into the 5 slowest tiers plus __OTHER__:

Query

query threadTimeSeriesMetric($input: ThreadTimeSeriesMetricInput!) {
  threadTimeSeriesMetric(input: $input) {
    timestamps {
      iso8601
    }
    series {
      values
      group {
        dimension
        value
        label
      }
    }
  }
}

Variables

{
  "input": {
    "metricName": "threads_first_response_time",
    "percentile": 90,
    "from": "2026-09-01T00:00:00Z",
    "to": "2026-09-30T23:59:59Z",
    "interval": { "unit": "DAY" },
    "groupBy": [{ "dimension": "TIER", "topN": 5 }],
    "filters": { "messageSource": ["EMAIL", "SLACK"] },
    "mode": "METRIC"
  }
}

Read the response

timestamps lists the start of every bucket in the range, in order. Each entry in series has a values list that lines up with timestamps index by index, and a group that says which group the series belongs to. Without groupBy, series has one entry and its group is null. A null in values means there was no data in that bucket. Buckets are never dropped, so the list always covers the whole range. Threads in Todo, Snoozed, and Done (threads_status_count__*) carry the last known count forward instead.

Get the threads behind a bucket

Set mode to THREAD_IDS to get the distinct IDs of the threads behind the value. The IDs cover the whole range, so narrow from and to to one bucket to get its threads. To get one group’s threads, add the group as a filter instead of using groupBy, which isn’t allowed in this mode. This query returns the Enterprise tier threads that moved to Done on September 14:

Query

query threadTimeSeriesMetricThreadIds($input: ThreadTimeSeriesMetricInput!) {
  threadTimeSeriesMetric(input: $input) {
    threadIds
  }
}

Variables

{
  "input": {
    "metricName": "threads_status_transitions_count__done",
    "from": "2026-09-14T00:00:00Z",
    "to": "2026-09-14T23:59:59Z",
    "interval": { "unit": "DAY" },
    "filters": { "tierIdentifiers": [{ "externalId": "enterprise" }] },
    "mode": "THREAD_IDS"
  }
}

timestamps and series are null in this mode.

GraphQL API

Building Agents

Agent integrations

Webhooks

Channels

Customer Cards

UI Components

Security

Changelog

Get a time series metric

Get a time series

Read the response

Get the threads behind a bucket

​Get a time series

​Read the response

​Get the threads behind a bucket

Get a time series

Read the response

Get the threads behind a bucket