Skip to main content
The Summary Definitions authoring UI has been retired. The endpoints below still work, but the GET /api/v1/summary-definitions read endpoint now exists only to power the customer viewer’s summaries filter. For behavioral aggregation, use Behavioral Metrics instead.
See also: Summary Definitions concept and configuration for what this API powers, when to call it, and how it is configured.

Overview

Summary definitions control how raw interaction events are aggregated into daily/weekly/monthly buckets. Each definition specifies which dimensions to group by and which time windows to maintain.

List Summary Definitions

Returns all summary definitions for the current tenant, ordered by system definitions first, then alphabetically.

Response


Create Summary Definition

Request Body

Allowed Dimensions

Allowed Aggregates

Allowed Windows

Example

Response 201

Returns the created summary definition with id, isSystem: false, and timestamps.

Error codes


Update Summary Definition

Request Body

System summary definitions (those flagged isSystem: true) cannot have their dimensions changed. Attempting to change them returns a 400 error. You can update the name, description, aggregates, windows, and status.

Response 200

Returns the updated summary definition.

Error codes


Delete Summary Definition

Deletes a summary definition. System definitions cannot be deleted.

Query Parameters

Response

Error codes

Summary definitions are an inert config surface — no aggregation engine reads them (see the retired-feature note). Deleting one only removes the descriptive record; it does not start or stop any aggregation. For behavioral aggregation, use Behavioral Metrics.

Role requirements


System definitions

Summary definitions flagged isSystem: true are treated as protected system definitions. They:
  • Cannot have their dimensions changed (the API returns 400 if you try).
  • Cannot be deleted (the API returns 400).
  • Can have their name, description, aggregates, windows, and status updated normally.
  • Are listed first in GET responses (ordered by isSystem descending, then alphabetically by name).