List a repository's Actions cache entries
GET/api/repos/{owner}/{repo}/actions/caches
listRepositoryActionsCaches
One page of the repo's `actions/cache` entries in key order (keyset on `after`), the whole cache's totals, and 7-day usage from the repo's runs: per-entry hits, restore outcomes and the compile cache. Every 7-day aggregate is `null` when nothing reported it — absence, not zero. `can_delete` is the viewer's repo-write decision.
Authentication optional — this operation also accepts anonymous requests. When authenticating, use a bearer token or a session cookie.
curl
curl -X GET 'https://neosource.dev/api/repos/OWNER/REPO/actions/caches' \
-H 'Authorization: Bearer $NEOSOURCE_TOKEN'fetch
fetch("https://neosource.dev/api/repos/OWNER/REPO/actions/caches", {
method: "GET",
headers: {
Authorization: "Bearer $NEOSOURCE_TOKEN",
},
});Path parameters
ownerrequiredRepository owner or organization slug.
reporequiredRepository name.
Query parameters
afterKeyset cursor: the previous page's `next_cursor` (a cache key). Entries are ordered by key, so this returns keys strictly after it.
limitPage size; default 100, 1–100.
Responses
200Cache entries
application/json
Standard errors
Bodies documented once for the whole API — see standard errors.
- 400Bad Request — one of: invalid_input
- 403Forbidden — one of: forbidden
- 404Not Found — one of: not_found
- 423Locked — one of: busy
- 429Rate limited — retry after the `Retry-After` header
- 500Internal server error
- 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
- 504Gateway timeout — the request exceeded the server's handling budget