TechCrunch stories

GET https://api.api.sh/techcrunch/v1/posts
1 credit / call news try it in the playground →

TechCrunch stories with keyword, category, tag and date filters and five sorts: headline, excerpt, link, slug, publication and update times, authors, section, keywords, reading time, categories and tags (with their post counts) and image. Pass next_page back as page; null on the last page. Article bodies are not returned.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
q string Search words. Example: openai
category string Category slug, id or URL (e.g. artificial-intelligence, startups, venture, security, apps, hardware, fintech, climate, transportation).
tag string Tag slug, id or URL (e.g. openai, elon-musk).
after string Published after this date (YYYY-MM-DD).
before string Published before this date (YYYY-MM-DD).
sort newest | oldest | relevance | modified | title Order (default newest; relevance when q is given).
limit integer Stories per page (default 20, max 100).
page integer Page number (default 1).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/techcrunch/v1/posts?q=openai" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.