---
title: "Which drugs an HLA typing carries a published pharmacogenomic association for (names normalized first)"
method: POST
path: "/v1/pgx/screen"
---

# Which drugs an HLA typing carries a published pharmacogenomic association for (names normalized first)

`POST /v1/pgx/screen`

## Request

- Base URL: `https://api.hlaverify.com`
- URL: `https://api.hlaverify.com/v1/pgx/screen`
- Auth: one of:
  - none
  - API key in header `X-API-Key`

Exactly one of typing or alleles. Each name is normalized as /v1/normalize does, then joined to the table on its two-field form; summary.actionable is the CPIC level-A, allele-positive subset. Billable like /v1/normalize. Guideline lookup over published CPIC and PharmGKB associations, keyed by two-field HLA allele. Decision support only; not a medical device. After an allogeneic transplant the recipient's blood carries the donor's genome, and which genome should drive an HLA-mediated drug alert is an open question (NCT06856226); this lookup reports both and decides nothing.

## Request body

- object
  - `typing` Typing: locus -> up to 4 reported allele names. Allele strings only: never patient names, medical record numbers, dates of birth, or accession or case identifiers.
  - `alleles` string[]

## Response `200`

release, pgx_snapshot, scope, alleles[] (reported, current_name, allele_2field, flags, associations[]), summary, license, attribution

## Other responses

- `422`: invalid input
- `503`: table not available on this deployment

---

[API](https://skmtc.dev/hlaverify/apis/hla-verify.md) · [All operations](https://skmtc.dev/hlaverify/apis/hla-verify/llms.txt) · [OpenAPI document](https://skmtc.dev/hlaverify/apis/hla-verify/revisions/40cd5e7d134d?raw)