Core concepts & data model
The Reporting API is organized around a hierarchy of aggregation: instance → campaign → (networks, creators, posts). Each operation in the API Reference reads at one level (or provides a time-series view at instance level).
Hierarchy (ASCII)
Instance (workspace in Later Influence)
└── Campaign (marketing initiative)
├── Networks — metrics by social network (e.g. instagram, tiktok)
├── Creators — metrics per creator
└── Posts — metrics per content item
Which endpoint should I use?
| Business question | Endpoint |
|---|---|
| List instance IDs I can query | GET /instances |
| Executive KPIs for the whole workspace | GET /instances/performance |
| KPI trends over time | GET /instances/performance-over-time |
| Campaign roster without metrics | GET /campaigns |
| Compare campaigns on ROI, spend, affiliate | GET /campaigns/performance |
| Channel mix / platform comparison | GET /networks/performance |
| EMV-style ROI breakdown by network | GET /networks/return-on-investment |
| Leaderboards / creator benchmarks | GET /creators/performance |
| Content-level analysis | GET /posts/performance |
| Instance-level question | Endpoint |
|---|---|
| “Total impressions across everything we track?” | GET /instances/performance |
| “How did weekly impressions trend for six months?” | GET /instances/performance-over-time with startDate and endDate spanning those six months and granularity=week. |
| “What instances can I use?” | GET /instances |
| Campaign-level question | Endpoint |
|---|---|
| “Rank campaigns by estimated ROI.” | GET /campaigns/performance (see API Reference for sortProperty / sortDirection). |
| “Campaign names for a dropdown.” | GET /campaigns |
| Network-level question | Endpoint |
|---|---|
| “Average engagement rate per social network?” | GET /networks/performance |
| “Value of impressions vs comments per network?” | GET /networks/return-on-investment |
| Creator-level question | Endpoint |
|---|---|
| “Top creators by affiliate sales?” | GET /creators/performance |
| “Who posted most in this campaign?” | GET /creators/performance |
| Post-level question | Endpoint |
|---|---|
| “Highest impression posts this month?” | GET /posts/performance |
| “Paid vs organic on one asset?” | GET /posts/performance — compare organic fields vs paid* fields |
Metric namespacing
Organic vs paid vs links: Plain names (impressions, engagements, cpm, …) describe organic activity. Paid fields use the paid prefix (paidImpressions, paidEngagementRate, …). Tracking and affiliate metrics use trackingLinks* and affiliateLinks*. impressions is not the same as paidImpressions.
null vs 0
| Value | Meaning |
|---|---|
null |
The metric is not available for this row. |
0 |
The metric is defined for this row and the value is zero. |
Response envelope
Successful reads return:
{
"data": {},
"pagination": null
}
pagination includes page, pageSize, totalPages, and totalItems when the operation is paginated; it may be null for summaries such as GET /instances/performance.
Data freshness & consistency
Reporting numbers reflect what is already stored in the Later Influence platform. When creator content is collected and bound to your program, it appears in the product; from there, reporting aggregates are updated on about an hourly cadence. Two identical queries within that window may differ slightly while updates propagate.
Eventually consistent: A refresh inside the update window can show different totals for the same date range. If your UI presents live-looking numbers, consider showing a last updated indicator.