/builtin/jobs

POST /api/builtin/jobs

Price: 5 credits

Get full details of a Built In job posting by its id or URL: title, full description, summary, company, locations, remote/hybrid/on-site flags, seniority, salary range, industries, required skills, requirements, employment type, benefits, the external apply link, and posting dates.

How to use it

Get a single Built In tech job posting by its numeric id or full job URL. Returns one item with id, alias, title, description, summary, company, company_id, company_alias, company_image, company_size, location_text, locations (city/state/country/coordinates), is_remote, is_hybrid, is_on_site, seniority, category_id, salary (min_value/max_value/period), industries, skills, requirements, employment_type (FULL_TIME/PART_TIME/CONTRACTOR/INTERN), benefits (human-readable perks like health insurance / 401(K)), is_easy_apply, apply_url (external application link), apply_count, external_source, created_at, valid_through and url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Job id or Built In job URL (examples: "9314763", "https://builtin.com/job/cybersecurity-manager/9314763"; minLength: 1)

Response

• @type string (default: "BuiltinJob")
• id string required
• alias string nullable
• description string nullable
• summary string nullable
• company string nullable
• company_id integer nullable
• company_alias string nullable
• company_image string nullable
• company_size integer nullable
• location_text string nullable
• locations array (default: [])
  • @type string (default: "BuiltinJobLocation")
  • city string nullable
  • state string nullable
  • country string nullable
  • name string nullable
  • latitude number nullable
  • longitude number nullable
• is_remote boolean nullable
• is_hybrid boolean nullable
• is_on_site boolean nullable
• seniority string nullable
• category_id integer nullable
• salary object nullable
  • @type string (default: "BuiltinJobSalary")
  • min_value integer nullable
  • max_value integer nullable
  • period string nullable
• industries array (default: [])
• skills array (default: [])
• requirements array (default: [])
• employment_type string nullable
• is_easy_apply boolean nullable
• apply_url string nullable
• apply_count integer nullable
• external_source string nullable
• created_at string nullable
• valid_through string nullable
• url string nullable
• benefits array (default: [])

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 — Job 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.

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.