POST /api/builtin/articles
Price: 10 credits
Get a Built In article by its URL, slug, `<topic>/<slug>` or `/<slug>` alias: title, subtitle, summary, description, image, publish and update dates, author, editor and reviewer, topics and tags, the full text, the Built In companies it links to and its FAQ.
Get one Built In article by its URL, slug, `<topic>/<slug>` or `/<slug>` alias (the alias builtin/articles/search returns; a leading slash marks a single-segment topic page), with its full plain text. company_aliases are Built In company slugs the article links to, usable with builtin/companies.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)article string required — Built In article URL, the bare slug of an /articles/ page, `<topic>/<slug>` for a topic-path page, or `/<slug>` for a single-segment topic page (examples: "https://builtin.com/articles/ai-agent-security-gates", "https://builtin.com/software-engineering-perspectives/digital-public-infrastructure", "ai-agent-security-gates", "software-engineering-perspectives/digital-public-infrastructure"; minLength: 1)@type string (default: "BuiltinArticle")id integer nullablealias string requiredurl string requiredcanonical_url string nullabletitle string nullablesubtitle string nullabledescription string nullablesummary string nullableimage string nullablepublished_at integer nullableupdated_at integer nullableauthor object nullable@type string (default: "BuiltinArticlePerson")name string requiredurl string nullableimage string nullablejob_title string nullabledescription string nullablealumni_of string nullableknows_about string nullableprofile_links array (default: [])updated_by object nullable@type string (default: "BuiltinArticlePerson")name string requiredurl string nullableimage string nullablejob_title string nullabledescription string nullablealumni_of string nullableknows_about string nullableprofile_links array (default: [])reviewed_by object nullable@type string (default: "BuiltinArticlePerson")name string requiredurl string nullableimage string nullablejob_title string nullabledescription string nullablealumni_of string nullableknows_about string nullableprofile_links array (default: [])topics array (default: [])tags array (default: [])@type string (default: "BuiltinArticleTag")name string requiredalias string requiredtext string nullablecompany_aliases array (default: [])faqs array (default: [])@type string (default: "BuiltinArticleFaq")question string requiredanswer 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 — Article not found 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.