/quay/repositories/tags

POST /api/quay/repositories/tags

Price: 10 credits

List tags of a Quay.io repository, optionally including expired and superseded ones

How to use it

List the tags of one Quay.io repository. With `only_active` false the same tag name comes back once per revision, each with its own `started_at`/`ended_at` window — that is the tag history view, and the only way to see what a tag pointed at before it moved. On a multi-arch repository `size` is null and the per-platform digests are in `child_manifests`; feed one of those digests to repositories/manifests, not `manifest_digest`, to get layers.

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)
• count integer required — Number of tags to return (min: 1; max: 6000)
• only_active boolean — Return only tags that currently point at a manifest. Set to false to include expired tags and superseded revisions, which carry `ended_at` (default: true)
• name string nullable — Return only the tag with exactly this name (examples: "latest", "v3.13.3")
• name_contains string nullable — Return only tags whose name contains this substring (examples: "v3", "-distroless")

Response

• @type string (default: "QuayTag")
• alias string required
• name string required
• repository string required
• url string required
• manifest_digest string (default: "")
• is_manifest_list boolean (default: false)
• is_sparse boolean (default: false)
• is_reversion boolean (default: false)
• size integer nullable
• started_at integer nullable
• ended_at integer nullable
• child_manifest_count integer (default: 0)
• present_child_count integer (default: 0)
• child_manifests array (default: [])
  • @type string (default: "QuayTagChildManifest")
  • digest string required
  • is_present boolean (default: false)

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 not public 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.