Skip to main content
Date range differences and how the Transactions Report aggregates multi-part transactions can both create apparent mismatches with the API.
Applies to: Transactions API

​
Answer

If you regularly upload Signal File Uploads for past call records, manual corrections on those records may not appear in an API request if you’re pulling a different date range than the one you’re viewing in the Invoca UI Reports — keep this in mind when comparing the two. Another key factor: the Transactions Report aggregates certain transaction types into a single record, while the Transactions API keeps them separate. A common example is calls that route through multiple Invoca campaigns — often with Bundled Campaigns — where each campaign the call passes through creates a separate transaction in Invoca, all rolled into one record in the Transactions Report but remaining separate in the API. Performance Networks using payouts show a similar pattern: payouts applied after a call ends are their own transaction in Invoca, combined into a single UI record but returned as separate records via the API.

​
Where to go next

Last modified on September 25, 2026