Skip to content

Get a pool's session queue โ€‹

GET /v1/admin/runtime/queue

  • Operation ID: getRuntimeQueue
  • Tags: Runtime sessions
  • Base URL: http://localhost:8787

Queued sessions waiting for capacity in the given pool. If the runtime is unreachable the response is still 200 with { available: false }. Authenticates with a Platform staff JWT and permission, like every admin route; the backend calls the separate Runtime service on the caller's behalf (no Runtime API key is ever exposed or accepted).

Workflow: Integration guide.

Authentication: staff Bearer JWT with permission runtime.read.

Authentication โ€‹

  • Auth: staff Bearer JWT (Authorization: Bearer <access_token>) with the permissions below.
  • Required permissions: runtime.read

Parameters โ€‹

NameInTypeRequiredDescription
poolIdquerystringyesMin length: 1. Max length: 200

Responses โ€‹

200 โ€‹

Pool queue.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object | object (RuntimeUnavailable)

FieldTypeRequiredDescription
(variant 1).availablebooleanyesOne of: true
(variant 1).dataobject (RuntimeQueue)yes-
(variant 1).data.itemsobject[]yesQueued session entries, opaque runtime records.
(variant 1).data.totalintegeryes-
(variant 2).availablebooleanyesOne of: false

Errors โ€‹

400 โ€‹

Request validation failed.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ValidationErrorBody)

FieldTypeRequiredDescription
successbooleanyesOne of: false
errorobjectyes-
error.namestringyesOne of: "ZodError"
error.issuesobject[]yes-
error.issues[].codestringyes-
error.issues[].path(string | number)[]yes-
error.issues[].messagestringyes-

Request validation

json
{
  "success": false,
  "error": {
    "name": "ZodError",
    "issues": [
      {
        "code": "custom",
        "path": [
          "field"
        ],
        "message": "Invalid value"
      }
    ]
  }
}

401 โ€‹

Missing, malformed, expired or wrong-audience Bearer token (missing_token, invalid_token, invalid_audience).

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody)

FieldTypeRequiredDescription
errorstringyesStable machine-readable error code, e.g. forbidden, not_found.
detailsanynoOptional structured context. For 403 it is { perm }.

Error response

json
{
  "error": "missing_token"
}

403 โ€‹

Authenticated but lacking the required permission. details.perm lists the accepted permission keys.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "forbidden",
  "details": {
    "perm": "runtime.read"
  }
}

500 โ€‹

Unexpected server error (internal). No details are returned.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "internal"
}

Examples โ€‹

curl โ€‹

bash
curl -X GET 'http://localhost:8787/v1/admin/runtime/queue?poolId=3f6c2a1e-8b4d-4e7a-9c1f-2d5b6a7e8f90' \
  -H "Authorization: Bearer $ACCESS_TOKEN"

TypeScript โ€‹

ts
const accessToken = process.env.ACCESS_TOKEN; // user JWT from your sign-in flow

const response = await fetch("http://localhost:8787/v1/admin/runtime/queue?poolId=3f6c2a1e-8b4d-4e7a-9c1f-2d5b6a7e8f90", {
  method: "GET",
  headers: {
    "Authorization": `Bearer ${accessToken}`,
  },
});
if (!response.ok) throw new Error(`HTTP ${response.status}: ${await response.text()}`);
const data = response.status === 204 || response.status === 205
  ? undefined
  : response.headers.get("content-type")?.includes("json")
    ? await response.json()
    : await response.text();

Try this endpoint

Requests go directly from your browser to the API. Send request executes this endpoint against the selected server.

GET/v1/admin/runtime/queue

Your token stays in this tab's memory and is sent only when you press Send request.

Parameters

Built for developers. Ready for agents.