Get fan insights in bulk (POST 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.
{ "error": "forbidden" | "not_found" | "internal" }.read:insights— Access analytics, metrics, and insights data for performance tracking.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 insights for (1-100)
1 - 100 elementsResponse
Per-key insights 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 insights or a per-key error (forbidden, not_found, or internal).
- Option 1
- Option 2