Skip to main content
GET
Error

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
campaignId
string<uuid>
required

Response

Success

Campaign money and campaign-level totals. Per-channel audience facts live on CampaignPlacement, not here. spent + reserved + remaining always equals budget, where spent is what actually left the account (PAID and every status after it), reserved is committed on approval but not yet paid out, and remaining is the uncommitted budget a further approval can still spend.

​
budget
string
required
Pattern: ^-?\d+(\.\d{1,6})?$
Example:

"125.500000"

​
spent
string
required
Pattern: ^-?\d+(\.\d{1,6})?$
Example:

"125.500000"

​
reserved
string
required
Pattern: ^-?\d+(\.\d{1,6})?$
Example:

"125.500000"

​
remaining
string
required
Pattern: ^-?\d+(\.\d{1,6})?$
Example:

"125.500000"

​
currency
string
required
​
perChannel
object[]
required
​
performance
object
required

What the campaign delivered, against what it was forecast to deliver. views and reactions are measured by the parser on the posts that were actually published: they converge to the figure reached roughly 48h after each post went up and then stop growing, because tracking retention ends there and the placement completes — this is a settled result, not a live counter. clicks are measured on our own redirect: every link in a published post points at go.aflux.ai first, so following it is counted before the reader is sent on to the advertiser. Those two clocks do NOT run together, and ctr is the field that suffers for it — views stop at ~48h while clicks keep accruing for as long as the post stays up, so a campaign's ctr drifts DOWNWARD over the weeks after it finishes and is only comparable between campaigns of similar age. targetViews is the only forecast here (summed from the channels' statistics before the campaign ran); everything else is measured.