/techcrunch/articles

POST /api/techcrunch/articles

Price: 1 credit

Get a full TechCrunch article by id, slug or URL: headline, subtitle, excerpt, the complete article body as plain text and as HTML, separate publish and update timestamps, word count and reading time, every credited author with job title and socials, the section and topic-tag taxonomies, region and storyline collections, and the featured image with its photo credit.

How to use it

Fetch a single TechCrunch article. Accepts the numeric post id, the bare slug, or the full article URL (https://techcrunch.com/YYYY/MM/DD/slug/). Returns one item with article_title, subtitle, social_title (the shorter headline the editors wrote for social cards, when they wrote one), excerpt, text (plain text body), html (original markup), published_at and updated_at as separate unix timestamps, word_count, comment_count, reading_time_minutes, authors[] (name, job_title, organization, description, socials, article_count), categories[]/tags[]/regions[]/storylines[] taxonomy terms, image plus featured_image with credit and copyright, apple_news_url and the is_brief/is_breaking/is_featured flags. Use techcrunch/articles/search to discover article ids.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — TechCrunch article id, slug or article URL (examples: "https://techcrunch.com/2020/06/01/self-driving-vehicle-startup-argo-ai-completes-2-6b-deal-with-volkswagen-expands-to-europe/", "remove-china-apps", "1997092"; minLength: 1)

Response

• @type string (default: "TechcrunchArticle")
• id integer required
• article_title string required
• alias string required
• web_url string required
• published_at integer nullable
• updated_at integer nullable
• excerpt string nullable
• subtitle string nullable
• social_title string nullable
• seo_description string nullable
• reading_time_minutes integer nullable
• is_brief boolean (default: false)
• is_breaking boolean (default: false)
• is_featured boolean (default: false)
• post_format string nullable
• image string nullable
• image_id integer nullable
• apple_news_url string nullable
• wp_author_id integer nullable
• authors array (default: [])
  • @type string (default: "TechcrunchArticleAuthor")
  • id integer required
  • name string required
  • alias string required
  • login string nullable
  • job_title string nullable
  • organization string nullable
  • description string nullable
  • profile_url string nullable
  • image string nullable
  • article_count integer nullable
  • guest_author_id integer nullable
  • twitter_url string nullable
  • linkedin_url string nullable
  • facebook_url string nullable
  • homepage_url string nullable
• categories array (default: [])
  • @type string (default: "TechcrunchTerm")
  • id integer required
  • name string required
  • alias string nullable
  • taxonomy string nullable
  • web_url string nullable
  • description string nullable
  • content_count integer nullable
  • parent_id integer nullable
• tags array (default: [])
  • @type string (default: "TechcrunchTerm")
  • id integer required
  • name string required
  • alias string nullable
  • taxonomy string nullable
  • web_url string nullable
  • description string nullable
  • content_count integer nullable
  • parent_id integer nullable
• regions array (default: [])
  • @type string (default: "TechcrunchTerm")
  • id integer required
  • name string required
  • alias string nullable
  • taxonomy string nullable
  • web_url string nullable
  • description string nullable
  • content_count integer nullable
  • parent_id integer nullable
• storylines array (default: [])
  • @type string (default: "TechcrunchTerm")
  • id integer required
  • name string required
  • alias string nullable
  • taxonomy string nullable
  • web_url string nullable
  • description string nullable
  • content_count integer nullable
  • parent_id integer nullable
• text string nullable
• html string nullable
• word_count integer nullable
• comment_count integer nullable
• language string nullable
• featured_image object nullable
  • @type string (default: "TechcrunchImage")
  • 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
  • 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
  • sizes array (default: [])
    • @type string (default: "TechcrunchImageSize")
    • 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 — Article not found (well-formed but nonexistent id, slug or URL) 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.