Get fan profiles in bulk
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.
{ "error": "not_found" | "internal" }.read:fan— Access fan-related data and information within the platform.
Authorizations
OAuth 2.0 access token, presented as a JWT bearer token in the Authorization header. Obtain a token via the authorization-code flow; the scopes granted to the token determine which operations it may call.
Headers
API version to use for the request
"2025-06-26"
Body
Array of fan UUIDs to fetch profiles for (1-100)
1 - 100 elementsResponse
Per-key profile or error for each requested fan. Always 200 when the request itself is valid, even if every key fails.
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.
- Option 1
- Option 2