Sign in

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.

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>

post/insights/fans/batch

Headers

X-Fanvue-API-Versionstring required
Example:2025-06-26

API version to use for the request

Request body

userUuidsstring[] required

Array of fan UUIDs to fetch insights for (1-100)

Response

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

object required

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

Changes

Changed in 1 of the 5 revisions of this API.7

  • dce5621fe5897See the full diff
    • ○

      added the required property /// to the response with the status

      response-required-property-added

    • ○

      added the required property ///// to the response with the status

      response-required-property-added

    • ○

      added the required property ///// to the response with the status

      response-required-property-added

    • ○

      added the required property ///// to the response with the status

      response-required-property-added

    • ○

      added the required property ///// to the response with the status

      response-required-property-added

    • ○

      added the required property ///// to the response with the status

      response-required-property-added

    • ○

      added the required property //// to the response with the status

      response-required-property-added