# /vesa/displayport/products/search `POST /api/vesa/displayport/products/search` Price: 20 credits Search VESA's DisplayPort certification registry — the monitors, TVs, cables, adapters, docks, graphics cards, notebooks, phones and headsets VESA has certified for DisplayPort. Narrows by product-name keyword, registry section, certifying vendor and certification class. Returns each product's registry id, the alias and address of its registry page where the card links to one, the manufacturer, the model, the certification classes it is filed under and the certified flag the registry prints on it. A broad query is answered with the first part of its matches rather than the whole set, so narrowing by section, vendor or class is what makes an answer complete. ## How to use it The registry lists only what a vendor asked VESA to publish, so absence is not evidence a product is uncertified. Several `manufacturers` widen the result set to their union, while `search`, `category` and `product_types` narrow it. `product_types` are section-specific — DP80 cable classes live under cables-adaptors, panel classes under monitors-tvs — so pass the matching `category` or the call is rejected. Pass a returned `alias` to /vesa/displayport/products for the family model and part numbers the same certification covers, which the cards do not carry. About a fifth of the cards link to the vendor's own site rather than to the registry page, so their `url` is off displayport.org and their `alias` is null; pass those rows' numeric `id` instead — every row carries one and it resolves to the registry page. A query broader than one answer comes back truncated and repeating it returns the same products, so reach the rest by splitting the query across sections, vendors and classes rather than by asking again. ## Parameters - `access-token` (string, required) ## Request body - `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500) - `search` (string, nullable) — Keyword the registry matches against the product name (examples: "Samsung", "39GX90SB", "cable"; minLength: 1) - `category` (string, nullable) — Registry section to search inside; omit to search the whole registry (one of: "monitors-tvs", "cables-adaptors", "computing", "upgrades-accessories", "mobile", "misc", "ar-vr-wearables") - `manufacturers` (array, nullable) — Certifying vendors; several values widen the result set to their union (one of: "accell", "acer", "aces_electronics_co_ltd", "acon", "act", "action-star", "aevoe-moshi", "amd", "amphenol", "aoc", "aopen", "artmu", "asrock", "astron-connectivity-corp", "asus", "aten", "beihai-bolide-science-and-technology-co", "beihai-century-joint-innovation-technology", "belkin", "benq", "biamp", "bizlink", "blaze", "boe", "bridgee_technologies_co_ltd", "cable-matters", "ce-link-ltd", "chang-yang-electronics-company-ltd", "christie-digital", "chrontel", "club-3d", "cratree-group-ltd", "crestron", "dell", "delock", "dongguan-arin-electronics-technology-co-ltd", "dongguan-fei-tai", "dongguan-fenfei-electronic", "dongguan-kelta-electro", "dongguan-neith-electronic-industry-co", "dongguan-posh-shine-electronic-technology-co-ltd", "dongguan-ult-unite-electronic-technology-co", "dongguan-xingkejiexin-electronics", "eizo", "elecom", "elka-international", "etseinri", "everpro-technologies-co", "farreach-electronic", "foxconn-interconnect-technology", "fujitsu", "fullink", "getac", "gigabyte", "glenfly", "glory-mark", "gold-cable-viet-nam-company-ltd", "gopod", "greatland-electronics", "guangdongmingji", "guangxicenturyinnovationdisplayelectronics", "guangzhou-little-snowman-information-technology-co-ltd", "hisense", "hisetec-electronic-co-ltd", "hitachi", "hkc", "hongkong-freeport-electronics", "hotron-precision-electronic-industrial-co-ltd", "hp-inc", "huawei", "huizhou-bohui-connection-technology", "hunan-linming-technology-co-ltd", "hwasung-elecom", "i-o-data-device-inc", "iiyama", "insignia", "intel", "jce", "ji-haw-industrial", "jupiter-systems", "jvc-kenwood", "kabeldirekt", "kaicap-investments-ltd", "kaijet-technology-international-corporation", "kandoubussa", "kunshan-delikang-electronics-technology-co-ltd", "l-com", "lenovo", "lg-electronics", "liangang-optoelectronic", "linkup-technology-inc", "lintes-technology-co-ltd", "luxshare-ict", "mediatek", "meilu-electronics-shenzhen-co-ltd", "microsoft", "molex", "monoprice", "monster", "msi", "msl", "nec", "ningbo-deemway", "ningbo-prime-electronic", "ningbo-scpl-electronics", "onko", "paugge", "philips", "pixio", "plugable", "quanta-storage-inc", "quotech", "razer", "samsung", "sceptre", "sensible-micro-corporation", "sharp", "shenglan-technology-co-ltd", "shenzhen-benfei-trade", "shenzhen-dns-industries", "shenzhen-euroway-technology", "shenzhen-g-cinda-power-solution-co-ltd", "shenzhen-lian-hong-sheng-technology-co-ltd", "shenzhen-samzhe-foundation-technology", "shenzhen-shuangrun-information-technology-co", "shenzhen-velocity-technology-innovations-co-ltd", "shenzhen-xingwanlian-electronics-co-ltd", "shenzhen-xinmingyi-electronic-co-ltd", "shenzhen-yuanrui-technology-co-ltd", "shenzhen-zhongchuang-xunda-technology", "shenzhen-zongyi-technology", "shenzhenktctechnology", "shenzhenmtc", "silkland", "simula-technology-inc", "singatron-technology", "skycable-enterprise-co-ltd", "sniokco", "sony", "startech-com", "stouchi", "sumitomo-electric-industries-ltd", "surefireelectricalcorp", "synopsys", "t-conn-precision", "targus", "top-victory-investments-ltd", "toshiba", "tte-corp", "uantin", "ubluker", "ugreen", "vcom-international", "viewsonic", "wacom", "wentronic-holding-gmbh", "wieson-technologies", "wuhan-junjia-technology-co-ltd", "xiaomi-communications-co", "yudu-eason-electronic-co-ltd", "zeskit", "zhaoxin", "zhejiang-quzhou-gelinte-wire-cable-co-ltd", "zhongshan-kabel-technology-co", "zhongshanlijie", "zong-cable-technology-co-ltd") - `product_types` (array, nullable) — Certification classes inside a section. Each value belongs to exactly one category, so a value from another section is rejected rather than silently ignored (one of: "4k-dp-displays", "4k-dp-displays-type-c", "5k-dp-displays", "8k-cables", "8k-cables-consumer", "8k-dp-displays", "adapters", "all-in-one", "cables-connectors", "collaboration-system", "desktop-computers", "digital-signage", "dockshubsaccessories", "dp-displays-type-c", "dp40-certified-cables", "dp54-certified-cables", "dp80-certified-cables", "graphics-cards", "lttpr", "motherboards", "notebook-computers", "pc-digital-displays", "pc-digital-displays-multi-stream", "phone", "projectors", "tablet", "thin-client", "usb-c") - `count` (integer, required) — Max number of results to return (min: 1; max: 400) ## Response ### 200 — Successful Response - `@type` (string) (default: "VesaDisplayPortProduct") - `id` (string, nullable) - `alias` (string, nullable) - `url` (string, nullable) - `listing_name` (string, nullable) - `manufacturer` (string, nullable) - `manufacturer_alias` (string, nullable) - `model` (string, nullable) - `categories` (array) (default: []) - `product_types` (array) (default: []) - `product_type_label` (string, nullable) - `is_certified` (boolean, nullable) - `alias_label` (string, nullable) - `aliases` (array) (default: []) ## Errors ### 422 — Validation Error A product type does not exist under the chosen category, or no category was given with one 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 product matched the keyword, section, vendor and class 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.