GitHub Public Workflow Run State Evidence API

Observe public GitHub Actions workflow runs for a known repository watchlist. One GET /repos/owner/repo/actions/runs per repository, at most3 repositories and first1..5 runs each. Retain run/workflow IDs, attempt and run numbers, state/conclusion, declared head SHA and created/updated times. Returned repository identity/public flag and run provenance URL are checked. A failed CI run still produces a successful billed metadata observation; a null conclusion remains unknown/pending, not success.

Source total_count is surfaced and additional pages are not followed. This is a small recent run slice, not complete history, security scanning or a proof that builds passed correctly. No token, private repo, user/actor details, commit message, pull request details, jobs, logs, artifact download, cancelling or starting a workflow. Anonymous GitHub requests share a60/hour primary quota; depleted rate headers,403/429 or retry instructions stop remaining requests without retries. Reduce calls and respect cache headers; a user may encounter a shared-IP limit even with a small input. Source revision/conclusion are declarations, not reproduction of the build.

Quick start

{"repositories": ["actions/setup-python"], "maxRunsPerRepository": 2}

Pricing and budget

0.001 USD per emitted workflow run observation (1 USD per1000), plus0.005 USD startup at default256MB. Higher memory can multiply startup events; check effective Store pricing. Failed/empty sources do not emit result charges; startup can still apply. At zero result budget, input validation occurs but no upstream request is sent, and rowsAvailable is null (unknown). A positive budget can request the bounded source set before output; emission stops at the result cap and complete=false/PARTIAL_BUDGET reports truncation.

Snapshot, integration and limits

Use dataset rows together with OUTPUT and SNAPSHOT. Pass SNAPSHOT.previousHashes as previousHashes in a later run. NO_BASELINE/FIRST_SEEN/UNCHANGED/CHANGED compare only selected metadata including itemKey and sourceUrl; missing records are not deletions. FIRST_SEEN means absent from the supplied baseline. There is no persistent hidden state or automatic polling. Export JSON/CSV/Excel through the default dataset.

API example: POST https://api.apify.com/v2/actors/soilair~github-public-workflow-run-state-evidence-api/runs with your Apify Authorization header and the JSON input above. Poll the returned run; read dataset items and OUTPUT/SNAPSHOT records using its store IDs. Do not place tokens or confidential data in input. No upstream key is needed. Results live in Apify run storage according to retention; no separate analytics service.

Only fixed HTTPS provider endpoints are constructed from validated identifiers. Public-IP DNS validation, pinned connections, TLS hostname verification,2MiB decoded responses, approximately95 seconds of network budget, at most5 same-provider redirects. Official API calls are distinct from website crawling; no arbitrary URLs or HTML pages. No linked documents/files are fetched. Queries are sequential with1-second spacing. Provider403/429 or Retry-After stops later calls; retry instructions are reported and no retry/proxy/circumvention is attempted. Shared IP limits and changes to upstream services can still block runs. Caller must respect provider headers and cache/reduce repeated requests. Text is data and should not be executed.

Developed with AI assistance. Tests and live/cloud comparisons qualify the selected-field contract; they do not prove commercial demand, provider uptime or a legal/license determination. Support: share a run ID and expected fields, without credentials or private material.

References: https://docs.github.com/en/rest/actions/workflow-runs · https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api