/quay/organizations/repositories

POST /api/quay/organizations/repositories

Price: 1 credit

List the repositories published under one Quay.io namespace

How to use it

Walk every repository of a Quay.io namespace, organization or user alike — this is the way to enumerate a publisher, since repositories/search stops at 100 results. Rows here carry `popularity` and `last_modified_at` but no `daily_pulls`; call repositories with an `alias` from the answer when the pull series is needed. Only public repositories are visible, so a namespace that exists but publishes nothing publicly is indistinguishable from a typo and both return 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• namespace string required — Organization or user namespace, or its quay.io URL (examples: "prometheus", "coreos", "redhat"; minLength: 1)
• count integer required — Number of repositories to return (min: 1; max: 3000)

Response

• @type string (default: "QuayRepository")
• alias string required
• namespace string required
• name string required
• url string required
• kind string (default: "")
• state string (default: "")
• description string nullable
• is_public boolean (default: false)
• is_organization boolean nullable
• is_free_account boolean nullable
• trust_enabled boolean nullable
• tag_expiration_seconds integer nullable
• popularity number nullable
• last_modified_at integer nullable
• daily_pulls array (default: [])
  • @type string (default: "QuayRepositoryPullStat")
  • date string required
  • pull_count integer (default: 0)

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 — No public repositories under this namespace 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.