List runner labels
The catalog of available runner labels with their specs (cpu, memory, arch, price/min) so runs-on mapping and cost-savings hints reference concrete options. Static and identical for every caller — authenticated, but requires no resource scope.
/api/labelsAuthorization
bearerAuth Session token from sling login.
In: header
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/api/labels"{ "labels": [ { "label": "starsling-ubuntu-24.04-8", "cpu": 8, "memory_gb": 32, "arch": "x64", "price_per_min_usd": 0.016 } ]}Resolve an id or URL to a target POST
Polymorphic ID resolution: given a parsed descriptor (run/job/attempt id, a runner id, a bare id, or a GitHub Actions URL), resolve it against the CI facts store to the most specific target, or return a candidate list on ambiguity. A runner id resolves to the job/attempt target(s) that ran on that runner — or, with target=run, to the distinct run(s) it touched; several candidates when a runner is reused. Authenticated; scoped to the caller's orgs by membership.
Your user id GET
The authenticated user's id, and nothing else — the cheapest way to confirm a token works. Use /api/whoami for the full identity and credential details.