/ghcr/organizations/packages

POST /api/ghcr/organizations/packages

Price: 1 credit

List the container packages published under one GitHub namespace

How to use it

Enumerate every ghcr.io container package a GitHub organization publishes — the way to inventory a publisher, since packages/search stops at 1,000 results. Individual users have no such listing and return 412; reach a user's package by name through the packages endpoint, which does accept user namespaces. `published_at` is when the package first appeared, not its last release, and `download_count_approx` is the rounded figure GitHub prints on the card ('186M') — call packages with an `alias` for the exact total.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• namespace string required — GitHub organization login that publishes the packages (examples: "home-assistant", "goauthentik", "nginxinc"; minLength: 1)
• count integer required — Number of packages to return (min: 1; max: 1000)
• query string nullable — Keep only packages whose name matches this text (examples: "hassio", "nginx")

Response

• @type string (default: "GhcrNamespacePackage")
• alias string required
• namespace string required
• name string required
• url string required
• pull_reference string required
• owner_name string (default: "")
• published_at integer nullable
• download_count_approx integer nullable
• source_repository string (default: "")
• source_repository_url string (default: "")

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 organization packages listing for this namespace, or it publishes none publicly 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.