/builtin/jobs/search

POST /api/builtin/jobs/search

Price: 20 credits

Search Built In tech jobs by keyword and/or filters (category, experience level, remote policy, industry, location, skill, posting recency). Each result carries id, title, company, location, remote policy, salary, seniority, industries, a short summary, top skills and the job url.

How to use it

Search Built In tech jobs by a keyword and/or filters: category, experience (internship/entry-level/junior/mid-level/senior/expert-leader), remote (remote/hybrid/on-site), industry (alias e.g. fintech), location (city alias e.g. austin), skill (e.g. Python) and posted_within (days). At least a keyword or one filter is required; count is how many jobs to return. Each item has id, alias, title, company, company_alias, location_text, remote_policy, salary_text, seniority, posted_text, industries, summary, skills and url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Keyword to search jobs by title, company or text (examples: "python"; minLength: 1)
• category string nullable — Filter by job category (one of: "ai-machine-learning", "consultant", "customer-success-experience", "cyber-security", "data-analytics", "designer", "engineering", "finance", "hr-recruiting", "legal", "marketing", "operations-support", "product-management", "program-project-management", "sales", "supply-chain-procurement")
• experience string nullable — Filter by experience / seniority level (one of: "internship", "entry-level", "junior", "mid-level", "senior", "expert-leader")
• remote string nullable — Filter by remote work policy (one of: "remote", "hybrid", "office")
• industry string nullable — Filter by industry alias (e.g. fintech, healthtech) (minLength: 1)
• location string nullable — Filter by city alias (e.g. austin, chicago) (minLength: 1)
• skill string nullable — Filter by required skill (e.g. Python) (minLength: 1)
• posted_within string nullable — Only jobs posted within this many days (one of: "1", "3", "7", "30")
• count integer required — Max number of jobs to return (min: 1)

Response

• @type string (default: "BuiltinJobSearchResult")
• id string required
• alias string nullable
• company string nullable
• company_alias string nullable
• location_text string nullable
• remote_policy string nullable
• salary_text string nullable
• seniority string nullable
• posted_text string nullable
• industries array (default: [])
• summary string nullable
• skills array (default: [])
• url 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 — 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.