/arstechnica/images

POST /api/arstechnica/images

Price: 1 credit

Get an Ars Technica image by its media id: original file url and every rendition size, alt text, caption, photo credit and copyright holder, the title and caption baked into the file by the photo agency, capture timestamp, camera and exposure settings, pixel dimensions, file size and the article it is attached to.

How to use it

Fetch a single Ars Technica image by the numeric media id found in image_id of arstechnica/articles or arstechnica/articles/search. Returns one item with image (original url), sizes[] (name, image, width, height, mime_type), alt, caption, description, credit (photo agency such as Getty Images), copyright (photographer), embedded_title and embedded_caption (the agency's own IPTC strings), keywords, camera, aperture, focal_length, iso, shutter_speed, taken_at, width/height, file_size, uploaded_at/updated_at, post_id and wp_author_id. Use it when you need the attribution line for an article photo.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• image integer required — Ars Technica media id, as returned in image_id of an article (examples: 2167297, 2167477; >: 0)

Response

• @type string (default: "ArstechnicaImage")
• id integer required
• image string required
• image_title string nullable
• alias string nullable
• web_url string nullable
• alt string nullable
• caption string nullable
• description string nullable
• credit string nullable
• copyright string nullable
• embedded_title string nullable
• embedded_caption string nullable
• keywords array (default: [])
• camera string nullable
• aperture number nullable
• focal_length number nullable
• iso integer nullable
• shutter_speed number nullable
• taken_at integer nullable
• width integer nullable
• height integer nullable
• file_size integer nullable
• media_type string nullable
• mime_type string nullable
• uploaded_at integer nullable
• updated_at integer nullable
• post_id integer nullable
• wp_author_id integer nullable
• sizes array (default: [])
  • @type string (default: "ArstechnicaImageSize")
  • name string required
  • image string required
  • width integer nullable
  • height integer nullable
  • mime_type 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 — Image not found (well-formed but nonexistent media id) 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.