Skip to main content
GET
Answer the question “my build has been distributing for an hour, is that normal?”. The endpoint reads the region’s build queue and the build machines’ heartbeats and returns one state, a plain-language verdict and an action.
Scope: read. Other customers’ builds share the regional queue; they are counted in ahead and totalInQueue but never identified.

How a build moves

Each region has one build queue, processed in order by that region’s build machine. A build waits its turn, is downloaded, scanned and saved, and once set active is copied to every streaming server in the region. Approved means it is on every server and serving sessions.

States

Path parameters

string
required
The project the build belongs to.
string
required
The build id (uploadId from Upload File, id from List Builds).

Headers

string
required
Your Streampixel API key.

Response

string
One of the states above.
boolean
true when the wait is not a normal queue wait and something should be done.
string
One or two sentences explaining state, written for the project owner.
string | null
What to do, or null when nothing is needed.
string
Raw pipeline status of the build.
string
The status as a stable word (see List Builds).
string
What the current status means.
string | null
ISO 8601 time the status last changed.
number | null
Minutes since then.
boolean
Whether this build is the one currently served.
object
The build entry, as in List Builds.
object
object
The region’s build machines from their heartbeats: total, online (reported within three minutes), busy, idle, lastReportAt, redisTrouble.
string
When this answer was computed.

Errors

Poll every 30 to 60 seconds. Distribution of a multi-gigabyte build to a region takes tens of minutes; the verdict tells you when polling is pointless.