# /vesa/displayhdr/products

`POST /api/vesa/displayhdr/products`

Price: 10 credits

List the displays VESA has certified under DisplayHDR, across all ten tiers from DisplayHDR 400 to DisplayHDR 1400 and the True Black tiers for emissive panels. Narrows by tier, by a keyword matched against the model name and its family model numbers, and by the Compliance Test Specification version. Returns the certified model, its tier, the CTS version and every family model number the certification also covers.

## How to use it

The registry carries no manufacturer column: the brand is the first word of `model` ('AOC AG275UXM2'), so search by brand with `search` rather than expecting a vendor field. A tier and a True Black tier of the same number are different certifications — True Black is the emissive-panel programme — and both are separate `tier` values. `aliases` is the list of family model numbers the same certificate covers, which is where a regional SKU appears. The registry lists only what a vendor asked VESA to publish, so absence is not evidence a display is uncertified.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `tier` (array, nullable) — Certification tiers to return; omit for every tier (one of: "displayhdr_400", "displayhdr_500", "displayhdr_600", "displayhdr_1000", "displayhdr_1400", "true_black_400", "true_black_500", "true_black_600", "true_black_1000", "true_black_1400")
- `search` (string, nullable) — Case-insensitive substring matched against the model name and the family model numbers (examples: "ASUS", "PG32UQX", "Samsung"; minLength: 1)
- `cts_version` (string, nullable) — Compliance Test Specification version the certification was granted under (examples: "1.0", "1.1", "1.2")
- `count` (integer, required) — Max number of results to return (min: 1; max: 3000)

## Response

### 200 — Successful Response

- `@type` (string) (default: "VesaDisplayHdrProduct")
- `certificate_id` (string, nullable)
- `model` (string, nullable)
- `tier` (string, nullable)
- `tier_label` (string, nullable)
- `cts_version` (string, nullable)
- `aliases` (array) (default: [])

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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 certified display matched the tier, keyword and CTS version combination

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.