---
title: "Get fan insights in bulk (POST batch)"
method: POST
path: "/insights/fans/batch"
---

# Get fan insights in bulk (POST batch)

`POST /insights/fans/batch`

Returns detailed insights for up to 100 fans in a single request, keyed by the input fan UUID.

This is the high-cap, JSON-body counterpart to `GET /insights/fans` (capped at 20 via query string). It is intended for initial-sync flows that need to hydrate many fans without per-fan round trips.

Per-key errors are reported inside the 200 response body so a single forbidden or missing fan never collapses the whole request — consumers can keep partial results and only retry the failing keys.

<Note>Maximum 100 fan UUIDs per request. Failed keys are reported as `{ "error": "forbidden" | "not_found" | "internal" }`.</Note>

## Headers

- `X-Fanvue-API-Version` string, required

## Request body

- object
  - `userUuids` string[], required — Array of fan UUIDs to fetch insights for (1-100)

## Response `200`

Per-key insights or error for each requested fan. Always 200 when the request itself is valid, even if every key fails.

- object — Map of input fan UUID to insights or a per-key error (forbidden, not_found, or internal).

## Other responses

- `400` — Bad Request - API version not supported OR validation failed
- `401` — Unauthorized Response
- `403` — Unauthorized Response
- `410` — API version no longer supported (sunset)
- `429` — Too many requests - rate limit exceeded

---

[API](https://skmtc.net/fanvue/apis/fanvue-api.md) · [All operations](https://skmtc.net/fanvue/apis/fanvue-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fanvue/fanvue-api/revisions/c5ddcd5c7e72/schema)