Get Selection Digest
Changed onWho 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.
Request
- Base URLhttps://api.minro.com (the document declares no server; this is the origin it was published from)
- URLhttps://api.minro.com/api/v1/agents/selection/digest
- Authnone declared
Query parameters
Headers
Bearer <token>
Response
Successful Response
Changes
- info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- info
- info
the
response's property default value{"request_id":"","timestamp":"2026-09-16T23:27:36.856600"}was removed for the status - info
the
response's property default value2026-09-16T23:27:36.856600was removed for the status
- info