Monthly rollup, one entry per currency

Causes sorted by lost_revenue_minor descending within each currency (R14 — money order is the point of this feature), plus totals, unknown-revenue count, and the delta against the prior month’s total. Served entirely from the precomputed rollup (R12) — never aggregated from raw entries at read time. Gated at the analytics tier (Concierge/Scale) — the worker writes for every tier regardless, so an upgrading merchant’s backlog is already there.

currency is optional. Given, the response is a one-element list scoped to that currency. Omitted, the response holds one element per currency the merchant actually has a rollup for that month — read directly from the ledger’s own data, not derived from store configuration, so the caller never has to enumerate stores/ currencies itself and call this endpoint once per currency. Currencies are never summed together either way (R9): each element is independently computed, exactly as the single-currency form already returns it.

curl -X GET "https://api.sarvex.example.com/v1/ledger/summary" \
  -H "Authorization: Bearer YOUR_TOKEN"

const response = await fetch("https://api.sarvex.example.com/v1/ledger/summary", {
  method: "GET",
  headers: {
    "Authorization": "Bearer YOUR_TOKEN"
  }
});

import requests

response = requests.get(
    "https://api.sarvex.example.com/v1/ledger/summary",
    headers={
        "Authorization": "Bearer YOUR_TOKEN"
    },
)

{
  "data": [
    {
      "month": "2026-08",
      "currency": "USD",
      "causes": [
        {
          "cause": "payment_handler",
          "count": 0,
          "lost_revenue_minor": 0
        }
      ],
      "total_count": 0,
      "total_lost_revenue_minor": 0,
      "entries_with_unknown_revenue": 0,
      "prior_month_delta_minor": 0
    }
  ]
}

{
  "error": {
    "code": "string",
    "message": "string",
    "details": {}
  }
}

{
  "error": {
    "code": "string",
    "message": "string",
    "details": {}
  }
}