Get fan insights

Returns detailed insights about a specific fan for the authenticated creator, including spending statistics, subscription status, and fan engagement metrics.

Each money field comes as a gross value and a net one, net meaning refunded and charged-back purchases removed: total and netTotal, count and netCount, average and netAverage. spending.total.total has always been net of reversals, so the gross per-source figures can add up to more than it and the gap is exactly the reversals, which are not returned as a source of their own; the per-source netTotal values add up to spending.total.netTotal. spending.maxSinglePayment drops reversed purchases entirely, which is why it carries no net variant.

A reversal is normally a separate invoice for the full original amount: there are no partial refunds, and the original payment is never rewritten, so the original still appears on /insights/earnings. Pair the two through reversedTransactionOrderId on the refund/chargeback rows of that endpoint. A payment marked refunded or charged back without a linked reversal invoice is the exception: there is no negative row for spending.total.total to subtract so it does not come down, while every net figure drops the purchase. That is why the net total is aggregated over the surviving purchases rather than derived from the gross one.

Every figure here is computed on each request with no caching — the spending fields from live invoice data, status and the subscription block from the subscription, follow and payment-method records — so two reads seconds apart can legitimately differ.