/anaconda/packages

POST /api/anaconda/packages

Price: 20 credits

Get conda package metadata by channel and name, 'channel/name', or anaconda.org package URL

How to use it

Get full metadata of a conda package on Anaconda.org by channel and name (a package name is unique only within a channel, so both are needed; channel defaults to conda-forge). Accepts a plain name, a 'channel/name' reference, or an anaconda.org package URL. Returns name, channel, summary, description, package types, homepage, latest version, the full version list, per-platform latest versions, license, development/documentation/source links, total download count, watcher and upvote counts, owner channel details, and created/modified timestamps. Use the files endpoint for a version's downloadable artifacts and the releases endpoint for the per-version history.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• name string required — Package name, 'channel/name' reference, or anaconda.org package URL (examples: "numpy", "bioconda/samtools", "https://anaconda.org/conda-forge/pytest"; minLength: 1)
• channel string — Channel (owner) that hosts the package (default: "conda-forge"; examples: "conda-forge", "bioconda", "main")

Response

• @type string (default: "AnacondaPackage")
• name string required
• channel string required
• full_name string (default: "")
• summary string nullable
• description string nullable
• package_types array (default: [])
• homepage string nullable
• latest_version string nullable
• versions array (default: [])
• version_count integer (default: 0)
• platforms object (default: {})
  • * string
• conda_platforms array (default: [])
• license string nullable
• license_url string nullable
• dev_url string nullable
• doc_url string nullable
• source_git_url string nullable
• source_git_tag string nullable
• revision integer (default: 0)
• is_public boolean (default: true)
• access string nullable
• download_count integer (default: 0)
• watcher_count integer (default: 0)
• upvote_count integer (default: 0)
• build_count integer (default: 0)
• created_at integer nullable
• modified_at integer nullable
• owner object nullable
  • @type string (default: "AnacondaChannel")
  • login string required
  • name string nullable
  • company string nullable
  • location string nullable
  • description string nullable
  • user_type string nullable
  • created_at integer nullable
  • web_url string (default: "")
• web_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 — Package not found 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.