Events & ExportError-tracking weekly digest

Error-tracking weekly digest

Everything needed for a "weekly digest" error-tracking email in one call. Returns a summary block with the current window's totals and the week-over-week change_pct versus the equal-length window immediately before it — total_exceptions, total_sessions, and crash_free_sessions (the fraction of sessions with no $exception, as a 0–1 rate). daily_exceptions is the current window's per-day counts, zero-filled across every day in the range so the bar chart always has one bar per day. top_issues are this window's issues sorted by occurrences; new_issues are issues first seen in this window — i.e. not seen in the new_lookback_days before it — also sorted by occurrences. Both lists carry the same fields as GET /exceptions/issues rows.

Time window: defaults to the last 7 full UTC days; pass date_from/date_to (YYYY-MM-DD) to override. Segment scoping: pass segment_id / exclude_segment_id to scope the whole digest.

curl -X GET "https://mythic-analytics.gulp.workers.dev/client/v1/data/exceptions/digest?location_id=example_string&date_from=2024-12-25&date_to=2024-12-25&top_limit=5&new_limit=5&new_lookback_days=90&segment_id=123e4567-e89b-12d3-a456-426614174000&exclude_segment_id=123e4567-e89b-12d3-a456-426614174000" \
  -H "Content-Type: application/json" \
  -H "X-Location-Id: example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "success": true,
  "data": {
    "range": {
      "date_from": "2026-07-13",
      "date_to": "2026-07-19"
    },
    "summary": {
      "total_exceptions": {
        "current": 473,
        "previous": 119,
        "change_pct": 297
      },
      "total_sessions": {
        "current": 473,
        "previous": 119,
        "change_pct": 297
      },
      "crash_free_sessions": {
        "current": 473,
        "previous": 119,
        "change_pct": 297
      }
    },
    "daily_exceptions": [
      {
        "date": "2026-07-17",
        "count": 10
      }
    ],
    "top_issues": [
      {
        "issue_id": "v1:1d908dc6145bd8dc7982aff9366b5042",
        "exception_type": "TypeError",
        "message": "Cannot read properties of null (reading 'addEventListener')",
        "culprit": "handler in app.js",
        "first_seen": "2024-12-25T10:00:00Z",
        "last_seen": "2024-12-25T10:00:00Z",
        "occurrences": 366,
        "sessions": 204,
        "users": 183,
        "volume_series": [
          {
            "bucket": "2024-12-25T10:00:00Z",
            "count": 10
          }
        ]
      }
    ],
    "new_issues": [
      {
        "issue_id": "v1:1d908dc6145bd8dc7982aff9366b5042",
        "exception_type": "TypeError",
        "message": "Cannot read properties of null (reading 'addEventListener')",
        "culprit": "handler in app.js",
        "first_seen": "2024-12-25T10:00:00Z",
        "last_seen": "2024-12-25T10:00:00Z",
        "occurrences": 366,
        "sessions": 204,
        "users": 183,
        "volume_series": [
          {
            "bucket": "2024-12-25T10:00:00Z",
            "count": 10
          }
        ]
      }
    ]
  }
}
GET
/exceptions/digest
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need the read scope of the family the route belongs to (people, events, sessions, replays, exceptions, heatmaps or bigquery_export). See Using an mcp_ key over HTTP.

Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need the read scope of the family the route belongs to (people, events, sessions, replays, exceptions, heatmaps or bigquery_export). See Using an mcp_ key over HTTP.
query
location_idstring

Alternative to the X-Location-Id header for agency (ak_) keys. Ignored for secret (sk_) keys.

query
date_fromstring

Start date (YYYY-MM-DD).

Format: date
query
date_tostring

End date (YYYY-MM-DD).

Format: date
query
top_limitinteger

Max top-issue rows. Default 5, min 1, max 25.

Min: 1 • Max: 25
query
new_limitinteger

Max new-issue rows. Default 5, min 1, max 25.

Min: 1 • Max: 25
query
new_lookback_daysinteger

How far back (before date_from) an issue must be absent to count as "new this window". Default 90, min 1, max 365.

Min: 1 • Max: 365
query
segment_idstring

Scope results to members of a saved segment (created via the Segments API). Two independent time filters apply: the segment decides WHICH PEOPLE qualify (a live definition, evaluated at query time — not stored membership), and date_from/date_to decides WHICH OF THEIR ROWS are returned. A person who qualifies today contributes all their sessions/events inside the date window — including ones unrelated to how they qualified; there is no "only rows from while they were a member". For first/last attribution scopes membership runs through the identity graph (a row counts when its distinct_id maps to a matching person); a segment with attribution: "session" instead matches visitors directly against the sessions store ("ever had a session that arrived via X"), with no identity-graph dependency. Composable with all other filters. Unknown or foreign id → 404 segment_not_found.

Format: uuid
query
exclude_segment_idstring

Scope results OUT — exclude rows from members of a saved segment (the inverse of segment_id, evaluated the same live way). Fully composable with segment_id: scope to one segment and exclude another simultaneously. The primary use is stripping your own QA/test traffic — which is often anonymous, so a rule-based segment (email domain, known ids) catches it with no SDK changes on the client's site. Unknown or foreign id → 404 exclude_segment_not_found.

Format: uuid
header
X-Location-Idstring

Location to scope the request to. Required for agency (ak_) keys on the event routes. Ignored for secret (sk_) keys, which resolve their own location, and not used by /export.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need the read scope of the family the route belongs to (people, events, sessions, replays, exceptions, heatmaps or bigquery_export). See Using an mcp_ key over HTTP.

Query Parameters

location_idstring

Alternative to the X-Location-Id header for agency (ak_) keys. Ignored for secret (sk_) keys.

date_fromstring

Start date (YYYY-MM-DD).

date_tostring

End date (YYYY-MM-DD).

top_limitinteger

Max top-issue rows. Default 5, min 1, max 25.

new_limitinteger

Max new-issue rows. Default 5, min 1, max 25.

new_lookback_daysinteger

How far back (before date_from) an issue must be absent to count as "new this window". Default 90, min 1, max 365.

segment_idstring

Scope results to members of a saved segment (created via the Segments API). Two independent time filters apply: the segment decides WHICH PEOPLE qualify (a live definition, evaluated at query time — not stored membership), and date_from/date_to decides WHICH OF THEIR ROWS are returned. A person who qualifies today contributes all their sessions/events inside the date window — including ones unrelated to how they qualified; there is no "only rows from while they were a member". For first/last attribution scopes membership runs through the identity graph (a row counts when its distinct_id maps to a matching person); a segment with attribution: "session" instead matches visitors directly against the sessions store ("ever had a session that arrived via X"), with no identity-graph dependency. Composable with all other filters. Unknown or foreign id → 404 segment_not_found.

exclude_segment_idstring

Scope results OUT — exclude rows from members of a saved segment (the inverse of segment_id, evaluated the same live way). Fully composable with segment_id: scope to one segment and exclude another simultaneously. The primary use is stripping your own QA/test traffic — which is often anonymous, so a rule-based segment (email domain, known ids) catches it with no SDK changes on the client's site. Unknown or foreign id → 404 exclude_segment_not_found.

Headers

X-Location-Idstring

Location to scope the request to. Required for agency (ak_) keys on the event routes. Ignored for secret (sk_) keys, which resolve their own location, and not used by /export.

Responses

successboolean
dataobject