/quay/repositories

POST /api/quay/repositories

Price: 1 credit

Get a Quay.io repository with its 92-day daily pull history

How to use it

Resolve one Quay.io repository. Quay has no root namespace, so a bare image name will not resolve — pass 'namespace/name' or the repository URL. `daily_pulls` is a per-day pull series covering the last 92 days and is the only usage signal Quay publishes here; there is no lifetime pull total and no star count on this endpoint, so read `popularity` from repositories/search when a ranking value is needed. `description` is the raw README markdown.

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", "coreos/etcd", "https://quay.io/repository/keycloak/keycloak"; minLength: 1)

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 — 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.