---
title: "Get Sequence Routing Summary"
method: GET
path: "/sequences/{sequence_id}/routing-summary"
tags: ["Sequences"]
---

# Get Sequence Routing Summary

`GET /sequences/{sequence_id}/routing-summary`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/sequences/{sequence_id}/routing-summary`
- Auth: HTTP bearer

Which providers this sequence's recipients sit behind, and what is suppressed.

Two properties that change how the answer should be read:

  * APPROXIMATE - it scans up to 10,000 recipients, not all of them.
  * FAIL-OPEN - on any error every count is zero, so an all-zero summary
    means "could not compute" just as much as "nothing matched". Do not
    render it as a confident zero.

Each recipient lands in exactly ONE bucket, suppression beating routing
(bounce > seg > personal), so the buckets partition the scanned set rather
than overlapping.

## Path parameters

- `sequence_id` string, required: Sequence id.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Response `200`

Successful Response

- ApiResponseSequenceRoutingSummary
  - `data` SequenceRoutingSummary, required: Approximate provider-routing and suppression breakdown for the list. Two properties a caller must not lose: * APPROXIMATE - computed by scanning up to 10,000 recipients, not all of them. * FAIL-OPEN - on any error every count is zero, so an all-zero summary means "could not compute" just as much as "nothing matched". Do not render it as a confident zero. Each recipient counts toward exactly ONE bucket, suppression taking precedence over routing (bounce > seg > personal), so the buckets are a partition and must not be summed alongside each other as if they overlap.
    - `m365_count` integer
    - `google_count` integer
    - `other_count` integer
    - `bounce_suppressed_count` integer
    - `seg_suppressed_count` integer
    - `personal_suppressed_count` integer
    - `scanned_count` integer, nullable: How many recipients were actually scanned (capped at 10,000).
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)