---
title: "Get Selection Digest"
method: GET
path: "/api/v1/agents/selection/digest"
tags: ["experiments"]
---

# Get Selection Digest

`GET /api/v1/agents/selection/digest`

Who is being messaged, who is being skipped, and which gate skipped them.

The disagreement rate says how often poll order and the selector differ. This says
what is actually happening, which is the question you have while WATCHING a rollout -
and the one that catches a bad one. A disagreement rate can look perfectly healthy
while every push in the workspace is being dropped for a single reason.

Read ``skips_by_reason`` first. A spike in no_channel_token is an integration problem,
a spike in frequency_cap is a budget problem, and a spike in premise_gone means people
are coming back on their own, which is the outcome you wanted.

## Query parameters

- `days` integer
- `limit` integer

## Headers

- `authorization` string, nullable — Bearer <token>

## Response `200`

Successful Response

- EnvelopeDict
  - `data` object, required
  - `meta` Meta
    - `request_id` string
    - `timestamp` string, date-time
    - `total` integer, nullable
    - `truncated` boolean, nullable

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/minro/apis/minro-cs-platform.md) · [All operations](https://skmtc.dev/minro/apis/minro-cs-platform/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/minro/minro-cs-platform/revisions/eb854265cf29/schema)
