Receivables Insights API
Measure exposure, aging, payment behavior, and recovery performance through Conduitt's insights domain.
The insights API separates operational intelligence from the resources that produce it.
Analytics
/v1/insights/analytics| Method | Path | Purpose |
|---|---|---|
GET | /v1/insights/analytics/dashboard | retrieve receivables control KPIs |
GET | /v1/insights/analytics/invoice-summary | summarize invoice state |
GET | /v1/insights/analytics/overdue | measure overdue exposure |
GET | /v1/insights/analytics/payment-trends | analyze payment behavior |
GET | /v1/insights/analytics/revenue | analyze collected revenue |
GET | /v1/insights/analytics/top-clients | find high-value client accounts |
Reports
/v1/insights/reportsReports include aging, profit and loss, revenue, repeat revenue, tax, activity summaries, and client revenue.
Search
Use /v1/insights/search for cross-resource discovery. Do not send separate large list requests against every receivables domain.
Query and Response Contracts
Analytics and report operations document their accepted period, date range, limit, and resource filters individually. Send ISO 8601 dates. Use the enumerated period values that each operation shows. Do not assume that every report supports the same window.
Responses contain server-calculated totals, counts, rates, series, breakdowns, or ranked records. Monetary aggregates use the exact string or numeric type that the response schema shows. Keep the filters that you sent with cached results. Your interface then never combines values from different periods or currencies.
Search responses include the type of each matched resource, its identifiers, display fields, and pagination metadata for the selected endpoint. Treat rank and derived display fields as point-in-time results. Fetch the source invoice or client before a mutation.