Skip to main content
GET
Get sent-referral analytics

Authorizations

X-API-Key
string
header
required

Public API key: cxp_<hex> (firm-scoped) or cxpp_<hex> (provider-scoped). Required on every request.

Response

Sent-referral analytics

data
object
required

Sent-referral analytics object. Documented here (partially): warmTransfer; other sections (kpis, currentStageBreakdown, trend, trendStats, outcomesOfSent, outcomesOfSigned, referralLooksDistribution, signedCasesByReferralAttempt, topSigningFirms, topCaseTypeJurisdictions) are returned as-is. topSigningFirms ranks receiving firms by cases whose most recent referral is currently signed, in litigation or closing; since 2026-09-08 closed, won and lost cases are not counted. trendStats carries the same volume as the raw daily trend, regrouped into a dense day/week/month-bucketed series over [rangeStart, rangeEnd] whose bucket size follows the window span, plus the window total, the mean per bucket, the busiest bucket, and the immediately preceding same-length window's totals when a referral date range is active. An empty bucket carries a count of 0 (a real zero, unlike the duration trends' null). When no date range is requested and a run of volume sits stranded far from the rest of the data — a legacy import dated decades before everything else, which would otherwise stretch the axis across those decades — the range narrows to where the data lives and the stranded volume is reported in excluded instead: it stays in total but is out of trend, avgPerBucket and peak, so sum(trend) + excluded.count === total. excluded is null in the normal case, and an explicitly requested range is never narrowed.

meta
object
required