/smartrecruiters/jobs

POST /api/smartrecruiters/jobs

Price: 1 credit

Get a single SmartRecruiters job posting by company board handle and posting id: name, reference number, release date, location (city, region, country, remote/hybrid flags, coordinates), industry, function, department, type of employment, experience level, language, custom fields, structured job-ad sections (company description, job description, qualifications, additional information as HTML), creator, posting and apply URLs, active flag and visibility.

How to use it

Get full details of one job posting from a company's SmartRecruiters career board. Identity is (company, posting_id). company is the board handle (e.g. BoschGroup), case-insensitive; posting_id is the numeric posting id. Returns one item with name, ref_number, released_at, location, industry, function, department, type_of_employment, experience_level, language, custom_fields, job_ad sections, creator, posting_url, apply_url, active and visibility.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company career-board handle from the careers URL (jobs.smartrecruiters.com/{company}) (examples: "Binance"; minLength: 1)
• posting_id string required — Job posting identifier (examples: "743999734661211"; minLength: 1)

Response

• @type string (default: "SmartRecruitersJob")
• id string required
• name string nullable
• uuid string nullable
• ref_number string nullable
• released_at string nullable
• location object nullable
  • @type string (default: "SmartRecruitersLocation")
  • city string nullable
  • region string nullable
  • country string nullable
  • address string nullable
  • postal_code string nullable
  • remote boolean nullable
  • hybrid boolean nullable
  • hybrid_description string nullable
  • latitude string nullable
  • longitude string nullable
  • full_location string nullable
• industry object nullable
  • @type string (default: "SmartRecruitersLabel")
  • id string nullable
  • label string nullable
• function object nullable
  • @type string (default: "SmartRecruitersLabel")
  • id string nullable
  • label string nullable
• department object nullable
  • @type string (default: "SmartRecruitersLabel")
  • id string nullable
  • label string nullable
• type_of_employment object nullable
  • @type string (default: "SmartRecruitersLabel")
  • id string nullable
  • label string nullable
• experience_level object nullable
  • @type string (default: "SmartRecruitersLabel")
  • id string nullable
  • label string nullable
• language object nullable
  • @type string (default: "SmartRecruitersLanguage")
  • code string nullable
  • label string nullable
  • label_native string nullable
• custom_fields array (default: [])
  • @type string (default: "SmartRecruitersCustomField")
  • field_id string nullable
  • field_label string nullable
  • value_id string nullable
  • value_label string nullable
• job_ad object nullable
  • @type string (default: "SmartRecruitersJobAd")
  • company_description object nullable
    • @type string (default: "SmartRecruitersJobAdSection")
    • title string nullable
    • text string nullable
  • job_description object nullable
    • @type string (default: "SmartRecruitersJobAdSection")
    • title string nullable
    • text string nullable
  • qualifications object nullable
    • @type string (default: "SmartRecruitersJobAdSection")
    • title string nullable
    • text string nullable
  • additional_information object nullable
    • @type string (default: "SmartRecruitersJobAdSection")
    • title string nullable
    • text string nullable
• creator object nullable
  • @type string (default: "SmartRecruitersCreator")
  • name string nullable
  • image string nullable
• posting_url string nullable
• apply_url string nullable
• referral_url string nullable
• active boolean nullable
• visibility 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 — Company board or posting 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.