/careerbuilder/jobs/search

POST /api/careerbuilder/jobs/search

Price: 20 credits

Search CareerBuilder job postings

How to use it

Search CareerBuilder job postings by keyword, with optional location, search radius, posting recency, and employment type. Returns a list of jobs, each with title, the hiring company (name, logo, website, description, founding year, employee-count band, headquarters), job locations (city, state, country, coordinates), salary range with currency and pay unit (flagged when estimated rather than employer-stated), a short description summary, employment types, industry, the apply method and URL, posting status, and posting and update dates. For the full job description and extracted skills, fetch a result by its id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (job title, skill, or company) (examples: "software engineer"; minLength: 1)
• location string nullable — Location as "City, ST" or "remote" (examples: "Austin, TX")
• distance string nullable — Search radius in miles around the location (one of: "5", "10", "30", "50", "100")
• date_posted string nullable — Limit results by how recently the job was posted (one of: "today", "last_2_days", "last_week", "last_2_weeks", "last_month")
• employment_type string nullable — Filter by employment type (one of: "FULL_TIME", "PART_TIME", "CONTRACT", "INTERN", "REMOTE")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "CareerbuilderJob")
• id string required
• seo_id string nullable
• url string nullable
• status string nullable
• is_promoted boolean nullable
• job_type string nullable
• provider string nullable
• industry string nullable
• posted_at string nullable
• created_at string nullable
• modified_at string nullable
• posted_age string nullable
• description string nullable
• description_text string nullable
• short_description string nullable
• apply object nullable
  • @type string (default: "CareerbuilderApply")
  • type string nullable
  • url string nullable
• locations array (default: [])
  • @type string (default: "CareerbuilderLocation")
  • city string nullable
  • state string nullable
  • country string nullable
  • postal_code string nullable
  • latitude number nullable
  • longitude number nullable
• salary object nullable
  • @type string (default: "CareerbuilderJobSalary")
  • salary_min number nullable
  • salary_max number nullable
  • currency string nullable
  • unit string nullable
  • is_extracted boolean nullable
• normalized_salary object nullable
  • @type string (default: "CareerbuilderNormalizedSalary")
  • currency string nullable
  • base_type string nullable
• company object nullable
  • @type string (default: "CareerbuilderCompany")
  • name string nullable
  • image string nullable
  • website string nullable
  • description string nullable
  • founded_year string nullable
  • employee_count_band string nullable
  • city string nullable
  • region string nullable
  • country string nullable
• employment_types array (default: [])
• skills array (default: [])
• remote_type string nullable
• normalized_title string nullable
• occupational_category string nullable
• valid_through_at string nullable
• applicant_location_countries array (default: [])
• mesco_codes 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 — No job postings found for this search 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.