Get fan insights in bulk (POST batch)
Changed onReturns 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.
Every field carries the same meaning as on GET /insights/fans/{userUuid}, including which money fields are net of reversals and which are gross, and the same absence of caching.
<Note>Maximum 100 fan UUIDs per request. Failed keys are reported as { "error": "forbidden" | "not_found" | "internal" }.</Note>
Request
- Base URLhttps://api.fanvue.com
- URLhttps://api.fanvue.com/insights/fans/batch
- AuthOAuth 2Authorization code: https://auth.fanvue.com/oauth2/authToken URL: https://auth.fanvue.com/oauth2/token scopes: read:insights, read:fan
Headers
API version to use for the request
Request body
Response
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).
Changes
- info
added the required property
///to the response with the status - info
added the required property
/////to the response with the status - info
added the required property
/////to the response with the status - info
added the required property
/////to the response with the status - info
added the required property
/////to the response with the status - info
added the required property
/////to the response with the status - info
added the required property
////to the response with the status
- info