List jobs for a specific re-run attempt of a GitHub Actions workflow run
domain: api.github.com · 4 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Determine the attempt_number (1 = the original run; 2, 3, ... = successive re-runs).
GET https://api.github.com/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs with `Authorization: Bearer <TOKEN>` and `Accept: application/vnd.github+json`.
The response shape matches the list-jobs-for-a-run endpoint: jobs[] with id, name, status, conclusion, steps[].
Paginate with `per_page` (max 100) and `page` for large attempts.
Known gotchas
attempt_number is required and 1-indexed; a request for a non-existent attempt returns 404.
Read access required; private repos need `repo` scope or `actions:read` for GitHub Apps.
The most recent attempt is also retrievable via the run's `run_attempt` field from the run detail endpoint.
Give your agent this knowledge — and 16,700+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?