Livepush Developers

API reference

Usage

CDN bandwidth delivered, per hostname and per stream

Livepush records delivered bytes against the hostname they were served on, not against the stream directly. A stream therefore has a bandwidth figure of its own only when it has a hostname of its own. Streams without one deliver on the account's primary hostname, where their traffic is pooled with every other such stream and with anyone still using an older link.

Both endpoints report the same assignment on every row, and it is the field to read first:

assignment What the bytes mean
dedicated One stream on the hostname, so the figure is that stream's
shared Several streams on the hostname; the figure covers all of them
pooled The account's primary hostname; traffic cannot be split per stream
other Hostnames no longer configured, kept so the rows still sum to the account total

These are delivery figures for reporting, not billing. Allowance, quota and overage come from the account's subscription and are not returned here. Values are billable bytes as integers; the dashboard's GB is bytes divided by 1e9. Every date is a UTC day, ranges are inclusive at both ends and span at most 400 days, and a collector writes the rows periodically, so the current day is always partial and lastUpdated tells you how stale a figure is.

2 endpoints

Endpoints

MethodPathOperation
GET /usage/cdn/hostnames Get bandwidth by hostname Returns every delivery hostname on the account with its billable bytes for the range, which is how you split CDN bandwid
GET /usage/cdn/streams/{stream_id} Get bandwidth for a stream Returns the bandwidth recorded for one stream, resolved through the hostname it delivers on. Ranges work exactly as they