Skip to main content
GET
Get account queue status

Size a submission

A request’s task count must fit your available in-flight capacity as well as the service’s batch-size limit. Lowering concurrency does not reduce how many submitted tasks count against the cap. For example, a snapshot with cap: 25 and total: 20 suggests room for five tasks. Submit a small batch, then wait for capacity to free before sending the next one. Treat the snapshot as advisory: it is not a reservation, and the submission gate can still return QUEUE_FULL. The cap depends on the plan and service configuration. Read cap rather than hard-coding a number or assuming the 1,000-task request ceiling is your account limit. Node: client.browserAgentStatus(). Python: client.browser_agent_status() returns a dictionary. Service capacity is a separate endpoint and does not replace your account’s cap.

Errors

Each status has an example body in the response examples. See errors and retries.

Authorizations

Authorization
string
header
required

Your pre.dev workspace API key (pdk_...) from Integrations, Built-in tab: https://pre.dev/projects/integrations?tab=built-in

Response

Account queue snapshot.

running
integer
claimed
integer
pending
integer
total
integer

Current inflight count reported by the queue snapshot.

cap
integer

Current account inflight limit, resolved by tier. Treat this as a snapshot, not a reservation.