Report an answer you believe is wrong (support portal intake)

Files one support report: a verdict, normalization or lookup that looks wrong, a docs page that disagrees with the API, an outdated release, or a question. Every report is rerun against the live API and the IPD-IMGT/HLA reference data, and a person confirms any error before it is published; a confirmed error is fixed and listed with the release that fixed it. Returns an id to follow it with GET /v1/report/{id} or at https://hlaverify.com/support?id=... . Do not include patient identifiers of any kind, names included: obvious ones (record-number and DOB labels, SSNs, US-format dates) are refused with 422 and nothing is stored, and a name cannot be detected. Stores what you send plus a timestamp, CF-IPCountry and the live release, and no IP address, in a store separate from API keys. At most 20 reports a day per IP. Not billable against the daily quota, but rate limited like every other /v1/ route (60 requests/minute per IP without a key).

post/v1/report

Request

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

Request body

kind'wrong_result' | 'docs_mismatch' | 'outdated_release' | 'question' | 'other'
endpointstring
inputstring required

The HLA names or request you sent. No patient identifiers.

receivedstring

What the API answered.

expectedstring required

What you expected instead.

detailsstring
emailstring

Optional; where we reply.

request_idstring
sourcestring

Free-text hint: site, mcp, docs.

Example request

{
  "endpoint": "/v1/verify",
  "input": "B*07:02",
  "expected": "a valid allele, not flagged",
  "email": "you@lab.example"
}

Response

recorded

okboolean required
idstring required
status'received' required
status_urlstring required
messagestring required
releasestring required

Changes

No recorded changes to this operation across all 1 revision of this API.