/displayspecifications/search

POST /api/displayspecifications/search

Price: 1 credit

Search DisplaySpecifications by brand and model name and return the matching monitors and TVs with their id, page URL, name, screen size and thumbnail.

How to use it

Turn a monitor or TV name into the opaque id the other DisplaySpecifications endpoints take. The match is on brand and model names only, not on specifications — to find models by panel, size or refresh rate use the model search. Monitors and TVs come back mixed in one list. A single character answers 200 with an empty list — the source itself treats it as too short to search — and the source returns only the strongest matches, so give it a distinctive part of the model name rather than a broad word.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Search text matched against brand and model names (examples: "odyssey", "XV270U", "OLED55"; minLength: 1)
• count integer required — Max number of models to return (min: 1; max: 10)

Response

• @type string (default: "DisplayspecificationsSearchHit")
• id string required
• url string required
• name string required
• size_inches number nullable
• image string nullable

Errors

• 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 — The entity was not found, or a precondition failed 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.

Response 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.