/techcrunch/tags/search

POST /api/techcrunch/tags/search

Price: 1 credit

Browse the TechCrunch topic-tag catalogue — tens of thousands of machine-readable entity tags for companies, products and people. Each tag carries its slug, display name, description, usage count and archive URL, and the slug is the value accepted by the tags filter of techcrunch/articles/search.

How to use it

Look up TechCrunch topic tags. Set count for how many to return and keyword to match a tag name (e.g. 'openai' returns openai, openai board, ...). hide_empty=true drops tags with no articles. Each item has id, name, alias (slug), content_count and web_url. Pass alias into the tags filter of techcrunch/articles/search to list everything written about that company or product; content_count also counts non-article TechCrunch items such as Startup Battlefield profiles and live-blog updates, so it can exceed the number of articles that search returns.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Only tags whose name matches this text (examples: "openai")
• hide_empty boolean nullable — Drop tags that have no published articles
• offset integer — Skip this many matching tags before collecting (default: 0; min: 0)
• count integer required — Max number of tags to return (min: 1)

Response

• @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

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 — The entity was not found, or a precondition failed 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.