/displayspecifications/brands/models

POST /api/displayspecifications/brands/models

Price: 20 credits

Return every model DisplaySpecifications lists for one manufacturer, grouped as the source groups them by product type and announcement year. Each row carries the model id, page URL, name, screen size, image, the hover spec summary and the heading of the group it belongs to.

How to use it

This is the only way to enumerate a manufacturer's whole catalogue — the finder returns a sample instead. One brand covers both monitors and TVs, and `group` is the source's own heading naming the product type and the announcement year, so read it to separate them and to date a model. Pass the brand id from the brands endpoint; an id that is not a brand answers 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• brand string required — Brand page URL or the bare hexadecimal brand id (examples: "f652d", "https://www.displayspecifications.com/en/brand/08cd6"; minLength: 1)
• count integer required — Max number of models to return (min: 1)
• locale string — Language of the group headings; model titles do not translate (default: "en"; one of: "en", "de", "es", "fr", "ru", "bg")

Response

• @type string (default: "DisplayspecificationsBrandModel")
• id string required
• url string required
• name string required
• brand_id string required
• size_inches number nullable
• image string nullable
• summary string nullable
• summary_fields object (default: {})
  • * string
• group string nullable
• group_description 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 brand 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.