/quay/repositories/manifests

POST /api/quay/repositories/manifests

Price: 1 credit

Get one manifest of a Quay.io repository with its layers or its per-platform children

How to use it

Resolve a manifest inside one repository. A digest belongs to the repository it was pulled from, so a digest from another repository returns 412 even though it is a valid digest. Two different shapes come back: `is_manifest_list` true means the image is multi-arch and the answer carries `platforms` (one child digest per os/architecture) with `layers` empty — re-request a child digest to get its layers. Children with `is_attestation` true are build provenance rather than runnable images, and the scan endpoints skip them.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• repo string required — Repository as 'namespace/name' or its quay.io URL (examples: "prometheus/prometheus", "keycloak/keycloak"; minLength: 1)
• digest string required — Manifest digest, as returned by repositories/tags in `manifest_digest` or `child_manifests[].digest` (examples: "sha256:0d34886ea2a8f3fd93b00f0b706b352bd8a1d377dbe660140bc2bd30d886b6cd"; minLength: 1)

Response

• @type string (default: "QuayManifest")
• digest string required
• repository string required
• url string required
• is_manifest_list boolean (default: false)
• media_type string (default: "")
• schema_version integer nullable
• config_media_type string nullable
• config_digest string (default: "")
• config_size integer nullable
• layers_compressed_size integer nullable
• layer_count integer (default: 0)
• annotations object (default: {})
  • * string
• layers array (default: [])
  • @type string (default: "QuayManifestLayer")
  • index integer required
  • blob_digest string (default: "")
  • command array (default: [])
  • comment string nullable
  • author string nullable
  • compressed_size integer nullable
  • created_at integer nullable
  • is_remote boolean (default: false)
  • urls array (default: [])
• platforms array (default: [])
  • @type string (default: "QuayManifestPlatform")
  • digest string required
  • media_type string (default: "")
  • os string (default: "")
  • architecture string (default: "")
  • variant string nullable
  • size integer nullable
  • is_attestation boolean (default: false)
  • attestation_for_digest string (default: "")
  • annotations object (default: {})
    • * string

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Repository not found, or the digest does not exist in this repository Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.