---
title: "Get fan profiles in bulk"
method: POST
path: "/insights/fans/profiles"
---

# Get fan profiles in bulk

`POST /insights/fans/profiles`

Returns profile data (handle, display name, avatar, nickname) for up to 100 fans in a single request, keyed by the input fan UUID.

This is intended for screens that render many fans at once (avatar + display name) without per-fan round trips — the profile counterpart to `POST /insights/fans/batch`.

A profile is returned only for fans connected to the creator (by subscription or follow) — the same fans `POST /insights/fans/batch` returns insights for. Per-key errors are reported inside the 200 response body so a single missing fan never collapses the whole request.

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

## Headers

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

## Request body

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

## Response `200`

Per-key profile 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 the fan's profile or a per-key error (forbidden, not_found, or internal). Profiles are returned for the same fans /insights/fans/batch returns insights for — fans connected to the creator by subscription or follow.

## 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)