/displayspecifications/models

POST /api/displayspecifications/models

Price: 5 credits

Return the full DisplaySpecifications sheet for one desktop monitor or TV: brand, series, model and aliases, announcement year, size, official image, and every specification row the source publishes, grouped by section and carrying the source's own glossary text for each field, plus the other models of the same series.

How to use it

Monitors and TVs share one id space and one endpoint; `is_tv` tells them apart, and TVs carry extra sections the monitors do not have such as the tuner, the system-on-chip and the supported file formats. The section set varies per model, so read `specs` rather than expecting a fixed field set — each row keeps the source's own label and glossary sentence, and `values` splits a multi-unit measurement into one entry per unit. `locale` translates section names, labels, glossary text and word-valued fields; numbers and their unit lists are identical in every language. Ids are opaque hexadecimal, so take them from the search, finder or brand endpoints instead of constructing them.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• model string required — Model page URL or the bare hexadecimal model id (examples: "ae334bd0", "https://www.displayspecifications.com/en/model/4f824b74"; minLength: 1)
• locale string — Language of the section names, field labels, glossary text and word-valued fields (default: "en"; one of: "en", "de", "es", "fr", "ru", "bg")

Response

• @type string (default: "DisplayspecificationsModel")
• id string required
• url string required
• locale string required
• name string required
• brand string nullable
• brand_id string nullable
• series string nullable
• model string nullable
• aliases array (default: [])
• year integer nullable
• size_inches number nullable
• is_tv boolean (default: false)
• image string nullable
• summary string nullable
• sections array (default: [])
• specs array (default: [])
  • @type string (default: "DisplayspecificationsSpec")
  • section string required
  • section_description string nullable
  • label string nullable
  • description string nullable
  • value string required
  • values array (default: [])
• series_models array (default: [])
  • @type string (default: "DisplayspecificationsSeriesModel")
  • id string required
  • url string required
  • name string required
  • size_inches number nullable
  • summary string 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 — No model exists under this id on DisplaySpecifications. 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.