healthcare.dev docs
API referenceDatasets

List RAG snapshots

GET /v1/datasets/{dataset}/snapshots

GET https://api.healthcare.dev/v1/datasets/{dataset}/snapshots

Team plan (403 plan-upgrade-required below Team); never counts as a billable call. A dataset's RAG snapshots, newest first: each release as citable text chunks (chunks.jsonl.gz) plus a precomputed vector per chunk (embeddings.f32), with LICENSE.txt and a manifest listing every file's size and SHA-256. A snapshot is built when a release publishes; the newest three are kept. Get download links with /v1/datasets/{dataset}/snapshots/{version}. Only datasets whose terms allow redistribution have snapshots.

Requires an API key: Authorization: Bearer hdev_live_.... See Authentication.

Path parameters

NameTypeRequiredDescriptionExample
datasetstringyesDataset id: one of hcpcs, icd10cm, icd10pcs, ndc, rxnormicd10cm

Examples

curl

curl "https://api.healthcare.dev/v1/datasets/icd10cm/snapshots" \
  -H "Authorization: Bearer $HDEV_API_KEY"

TypeScript

const res = await fetch("https://api.healthcare.dev/v1/datasets/icd10cm/snapshots", {
  headers: { Authorization: `Bearer ${process.env.HDEV_API_KEY}` },
});
const { data, meta } = await res.json();

Python

import os
import requests

res = requests.get("https://api.healthcare.dev/v1/datasets/icd10cm/snapshots", headers={"Authorization": f"Bearer {os.environ['HDEV_API_KEY']}"})
body = res.json()

Try it

GEThttps://api.healthcare.dev/v1/datasets/icd10cm/snapshots
Get a free key
Copy as curl
curl "https://api.healthcare.dev/v1/datasets/icd10cm/snapshots" \
  -H "Authorization: Bearer $HDEV_API_KEY"

Response

Snapshots, newest first

{
  "data": [
    {
      "format": "hdev-rag-snapshot/1",
      "dataset": "string",
      "name": "string",
      "version": "string",
      "effective_date": "2026-10-01",
      "published_at": "2026-10-24T12:00:00Z",
      "created_at": "2026-10-24T12:00:00Z",
      "records": 0,
      "chunks": 0,
      "embedding": {
        "id": "string",
        "dims": 1,
        "dtype": "float32",
        "byte_order": "little-endian",
        "normalized": true,
        "metric": "cosine",
        "file": "string",
        "rows": 0
      },
      "files": [
        {
          "path": null,
          "bytes": null,
          "sha256": null,
          "content_type": null,
          "gzip": null
        }
      ],
      "source": {
        "source": "string",
        "source_url": "string",
        "source_sha256": "string",
        "pipeline_version": "string"
      },
      "license": {
        "license": "string",
        "terms": {
          "display": null,
          "attribution": null,
          "url": null
        },
        "file": "string"
      },
      "latest": true
    }
  ],
  "meta": {
    "source": "cms-icd10",
    "data_version": "2026.1",
    "retrieved_at": "2026-10-24T12:00:00Z",
    "license": "Public domain (CMS). Reference data, not medical advice."
  },
  "links": {
    "self": "/v1/datasets/icd10cm/snapshots",
    "next": "/v1/datasets/icd10cm/snapshots?cursor=eyJrIjoiRTExLjkifQ"
  }
}

Fields

FieldTypeAlways presentDescription
format"hdev-rag-snapshot/1"yes
datasetstringyesDataset id, e.g. icd10cm
namestringyesDataset name
versionstringyesThe release (data_version)
effective_datestring | null (date)yesWhen the release takes effect
published_atstring (date-time)yesWhen we published the release
created_atstring (date-time)yesWhen the snapshot was built
recordsintegeryesActive records in the release (retired records are left out)
chunksintegeryesLines in the chunks file: one per active record with text
embeddingSnapshotEmbeddingyes
filesSnapshotFile[]yesEvery file except the manifest itself, with its size and SHA-256
sourceobjectyesWhere the release came from, as in each response's meta
licenseobjectyesWhat you may do with the data; the same text is in LICENSE.txt
latestbooleanyesTrue for the newest snapshot of the dataset

Errors

Errors are application/problem+json (RFC 9457). Branch on type, not on title. See Errors.

StatustypeWhen
400invalid-requestA parameter or the body failed validation; errors lists each field.
401unauthorizedMissing, malformed or revoked API key.
403plan-upgrade-requiredThe plan doesn't include this feature; required_plan names the plan that does.
404not-foundNo record with that id (retired records are still returned).
429rate-limited / quota-exceededToo many requests per second (retry after Retry-After), or the monthly quota is used up.
503dataset-unavailable / unavailableThe dataset has no published version yet, or the service is degraded.

On this page