GitDocs
Versioned API schema

GitHub REST API dependency graph SBOM export accepted job status asynchronous 202 response

An integration expects an immediate SBOM body but receives an accepted/job-style response.

GitHubGitHub platformVersioned API schemagh_deprecations

Agent Quick Fix

Repair against the current GitHub contract, then keep the change narrow and source-backed.

Product: GitHub
Current-contract area: Synchronous dependency-graph SBOM endpoint replaced by asynchronous flow
Likely root cause: An integration expects an immediate SBOM body but receives an accepted/job-style response.
Repair direction: Verifier exercises the changed field/status/enum plus an unaffected endpoint to prevent a brittle one-off patch. Verify the supported asynchronous/current path and preserve idempotency.

Symptom

An integration expects an immediate SBOM body but receives an accepted/job-style response.

Why This Happens

Several historical response shapes are locally plausible; only the selected current API version determines fields, enums, media types, and status codes.

Common Wrong Fixes

  • Changing local code without checking the current external contract.
  • Retrying the same install, build, or API call with no version/source change.
  • Applying a broad unsafe bypass when a narrow compatibility fix is available.

Codex Search Keywords

These are the search terms observed in a neutral Codex validation run for this failure shape.

GitHub REST API dependency graph SBOM export accepted job status asynchronous 202 response
site:docs.github.com REST API dependency graph export SBOM GitHub
"/dependency-graph/sbom" "202" GitHub
GitHub REST Dependency Graph SBOM endpoint docs
https://docs.github.com/en/rest/dependency-graph/sboms?apiVersion=2022-11-28

Source Trail

GitHub source file/reference: