POST /api/vesa/adaptivesync/products
Price: 10 credits
List the displays VESA has certified under AdaptiveSync Display and MediaSync Display, the variable refresh rate programmes for gaming and for judder-free video. Narrows by programme and by a keyword matched against manufacturer and model. Returns the manufacturer, the certified model with the sibling SKUs the certificate also covers, screen size, native resolution, the maximum refresh rate at that resolution, whether the certificate is AdaptiveSync 1.1, and the vendor product page where the registry links one.
AdaptiveSync Display and MediaSync Display are separate certificates: the first sets a gaming refresh and latency bar, the second targets video playback, and a display can hold either or both. `is_v11` marks the stricter AdaptiveSync 1.1 revision. A single registry row often names several SKUs; the first is `model` and the rest are `aliases`, so match a part number against both. `max_refresh_rate` can name two figures for a dual-mode panel. The registry lists only what a vendor asked VESA to publish, so absence is not evidence a display is uncertified.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)program string nullable — Certification programme to return; omit for both (one of: "adaptivesync", "mediasync")search string nullable — Case-insensitive substring matched against the manufacturer and the model (examples: "Alienware", "AW2525HM", "ViewSonic"; minLength: 1)count integer required — Max number of results to return (min: 1; max: 1000)@type string (default: "VesaAdaptiveSyncProduct")certificate_id string nullablemanufacturer string nullablemodel string nullableprogram string nullableis_v11 boolean nullablescreen_size string nullablenative_resolution string nullablemax_refresh_rate string nullableproduct_url string nullablealiases array (default: [])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 — No certified display matched the programme and keyword 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.