/bizreach/jobs

POST /api/bizreach/jobs

Price: 5 credits

Get one job posting on BizReach (bizreach.jp): title, salary range, job categories, industries, locations, tags, the job description, working conditions, required and preferred qualifications, workplace facts, the hiring company (its profile on company-posted jobs) or the headhunter handling it, and related jobs

How to use it

Find job ids with bizreach/jobs/search or bizreach/jobs/latest. On headhunter jobs the hiring company's name is not shown, so company is limited to its size.

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 URL (examples: "7959146", "https://www.bizreach.jp/jobs/10553858/"; minLength: 1)

Response

• @type string (default: "BizreachJob")
• id string required
• url string required
• job_title string nullable
• recruitment_type string nullable
• updated_date integer nullable
• salary string nullable
• salary_min number nullable
• salary_max number nullable
• salary_currency string nullable
• job_categories array (default: [])
• industries array (default: [])
• locations array (default: [])
• tags array (default: [])
• text string nullable
• working_conditions string nullable
• required_qualifications string nullable
• preferred_qualifications string nullable
• appeal_points array (default: [])
• is_remote_work_allowed boolean nullable
• smoking_policy string nullable
• workplace_details array (default: [])
  • @type string (default: "BizreachJobDetailItem")
  • name string required
  • value string nullable
• other_sections array (default: [])
  • @type string (default: "BizreachJobSection")
  • heading string required
  • text string nullable
• company object nullable
  • @type string (default: "BizreachJobCompany")
  • id string nullable
  • url string nullable
  • name string nullable
  • image string nullable
  • industries array (default: [])
  • prefecture string nullable
  • capital number nullable
  • capital_text string nullable
  • employee_count_range string nullable
  • description string nullable
• headhunter object nullable
  • @type string (default: "BizreachHeadhunter")
  • image string nullable
  • rank string nullable
  • score number nullable
  • specialties array (default: [])
  • comment string nullable
  • comment_date integer nullable
• related_jobs array (default: [])
  • @type string (default: "BizreachJobCard")
  • id string required
  • url string required
  • job_title string nullable
  • salary string nullable
  • salary_min number nullable
  • salary_max number nullable
  • salary_currency string nullable
  • job_categories array (default: [])
  • industries array (default: [])
  • locations array (default: [])
  • tags array (default: [])
  • is_new boolean nullable
  • company object nullable
    • @type string (default: "BizreachCompanyRef")
    • id string nullable
    • url string nullable
    • name string nullable
    • image 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 — No job under that id 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.