---
title: "Get First Week Holdout Cohorts"
method: GET
path: "/api/v1/agents/first-week/holdout/cohorts"
tags: ["experiments"]
---

# Get First Week Holdout Cohorts

`GET /api/v1/agents/first-week/holdout/cohorts`

## Request

- Base URL: `https://api.minro.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.minro.com/api/v1/agents/first-week/holdout/cohorts`
- Auth: none declared

The same comparison, split by signup week, so a trend is visible rather than one
pooled figure.

A single number hides the two things worth seeing: whether the gap is opening or
closing, and whether either arm is drifting for reasons that have nothing to do with
the programme (a change in acquisition mix moves both arms together, and pooling makes
that look like a stable effect).

Same eligibility as the pooled readout, for the same reasons: durable arm labels
rather than a recomputed hash, and closed windows only. Weeks with an empty arm are
returned with nulls rather than dropped, because a gap in the series is information -
it says the holdout was not running then.

## Query parameters

- `weeks` 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
    - `reply_total` integer, nullable
    - `metric_total` integer, nullable
    - `people_total` integer, nullable
    - `coverage` object, nullable
    - `event_scope` string, nullable

## Other responses

- `422`: Validation Error

## Changes

- **2026-09-20** `299da1f7604a`: 2 info
  - added the optional property `meta/coverage` to the response with the `200` status
  - added the optional property `meta/event_scope` to the response with the `200` status
- **2026-09-17** `2eae594b5490`: 2 info
  - the `meta` response's property default value `{"request_id":"","timestamp":"2026-09-16T23:27:36.856600"}` was removed for the status `200`
  - the `timestamp` response's property default value `2026-09-16T23:27:36.856600` was removed for the status `200`
- **2026-09-17** `8131eed4a6f3`: 2 info
  - the `meta` response's property default value changed from `{"request_id":"","timestamp":"2026-09-15T22:32:06.598396"}` to `{"request_id":"","timestamp":"2026-09-16T23:27:36.856600"}` for the status `200`
  - the `timestamp` response's property default value changed from `2026-09-15T22:32:06.598396` to `2026-09-16T23:27:36.856600` for the status `200`
- **2026-09-16** `ae15f6a99d1d`: 2 info
  - the `meta` response's property default value changed from `{"request_id":"","timestamp":"2026-09-11T07:11:59.155802"}` to `{"request_id":"","timestamp":"2026-09-15T22:32:06.598396"}` for the status `200`
  - the `timestamp` response's property default value changed from `2026-09-11T07:11:59.155802` to `2026-09-15T22:32:06.598396` for the status `200`
- …earlier changes not shown

[Operation history](https://skmtc.dev/minro/apis/minro-cs-platform/changes/api/v1/agents/first-week/holdout/cohorts/get.md)

---

[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.dev/minro/apis/minro-cs-platform/revisions/89cf17ffbb6a?raw)
