---
title: "Shared Cohort"
method: GET
path: "/api/v1/admin/users/{user_id}/shared-cohort"
tags: ["admin"]
---

# Shared Cohort

`GET /api/v1/admin/users/{user_id}/shared-cohort`

## Request

- Base URL: `https://api.peil.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.peil.app/api/v1/admin/users/{user_id}/shared-cohort`
- Auth: OAuth 2 (password, token URL `/api/v1/auth/jwt/login`)

Every account that registered from this account's signup address.

A preview, deliberately separate from the action. A shared address is *not*
proof of abuse — carrier CGNAT, coworking wifi and corporate NAT all put
unrelated people behind one IP, and at any real scale that will happen to
honest users. So the cohort is shown in full, with the activity counts that
actually distinguish a bot farm (nothing created, ever) from colleagues who
share an office, and nothing changes until it is confirmed against this list.

The address itself is never returned — it is resolved server-side, keeping
the country-only stance the deck already takes on location data.

## Path parameters

- `user_id` integer, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

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