POST /api/techcrunch/images
Price: 1 credit
Get a TechCrunch image by its media id: original file url and every rendition size, alt text, caption, photo credit and copyright holder, capture timestamp, camera and exposure settings, pixel dimensions, file size and the article it is attached to.
Fetch a single TechCrunch image by the numeric media id found in image_id of techcrunch/articles or techcrunch/articles/search. Returns one item with image (original url), sizes[] (name, image, width, height), alt, caption, description, credit (photo agency such as Getty Images), copyright (photographer), keywords, camera, aperture, focal_length, iso, shutter_speed, taken_at, width/height, file_size, uploaded_at/updated_at and post_id. Use it when you need the attribution line for an article photo.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)image integer required — TechCrunch media id, as returned in image_id of an article (examples: 2850313, 3150141; >: 0)@type string (default: "TechcrunchImage")id integer requiredimage string requiredimage_title string nullablealias string nullableweb_url string nullablealt string nullablecaption string nullabledescription string nullablecredit string nullablecopyright string nullablekeywords array (default: [])camera string nullableaperture number nullablefocal_length number nullableiso integer nullableshutter_speed number nullabletaken_at integer nullablewidth integer nullableheight integer nullablefile_size integer nullablemedia_type string nullablemime_type string nullableuploaded_at integer nullableupdated_at integer nullablepost_id integer nullablesizes array (default: [])@type string (default: "TechcrunchImageSize")name string requiredimage string requiredwidth integer nullableheight integer nullablemime_type string nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.