/techcrunch/authors

POST /api/techcrunch/authors

Price: 10 credits

Get a TechCrunch author profile by slug or author page URL: display name, job title, organization, biography, avatar, published article count, contact email and every linked social account (X/Twitter, Bluesky, Mastodon, LinkedIn, Facebook, personal site).

How to use it

Fetch a single TechCrunch author by slug (e.g. 'sarah-perez', taken from alias in an article's authors[]) or by the full author page URL. Returns one item with id, name, alias, job_title, organization, description (biography), profile_url, image (portrait), article_count, email, crunchbase_id and the social links twitter_url, bluesky_url, mastodon_url, linkedin_url, facebook_url and homepage_url. Use techcrunch/articles/search with authors=[alias] to list what this author wrote.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• author string required — TechCrunch author slug or author page URL (examples: "sarah-perez", "https://techcrunch.com/author/kirsten-korosec/"; minLength: 1)

Response

• @type string (default: "TechcrunchAuthorProfile")
• 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 required
• image string nullable
• article_count integer nullable
• guest_author_id integer nullable
• email string nullable
• twitter_url string nullable
• bluesky_url string nullable
• mastodon_url string nullable
• linkedin_url string nullable
• facebook_url string nullable
• homepage_url string nullable
• crunchbase_id 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 — Author not found (well-formed but nonexistent author slug) 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.