/jobtalk/jobs

POST /api/jobtalk/jobs

Price: 10 credits

Get one job posting from Jobtalk (転職会議): title, posting period, annual salary range, duties, requirements, working hours, holidays, work location, how to apply, the apply link, employees' ratings of this occupation at the company with average salary and overtime, and the hiring company's profile

How to use it

Job ids come from jobtalk/jobs/search; company_id opens the employer on jobtalk/companies.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Jobtalk job id or job URL (examples: "p12719762", "https://jobtalk.jp/jobs/p12719762"; minLength: 1)

Response

• @type string (default: "JobtalkJob")
• id string required
• url string required
• tags array (default: [])
• published_at integer nullable
• expires_at integer nullable
• updated_at integer nullable
• pr_headline string nullable
• pr_text string nullable
• annual_salary_min number nullable
• annual_salary_max number nullable
• salary_text string nullable
• locations_text string nullable
• job_description string nullable
• employment_type string nullable
• requirements string nullable
• working_hours string nullable
• salary string nullable
• holidays string nullable
• work_location string nullable
• how_to_apply string nullable
• other_details array (default: [])
  • @type string (default: "JobtalkJobDetail")
  • section string nullable
  • label string required
  • text string required
• images array (default: [])
• apply_url string nullable
• provider string nullable
• occupation_rating number nullable
• occupation_average_rating number nullable
• occupation_review_count integer nullable
• occupation_ratings array (default: [])
  • @type string (default: "JobtalkJobRating")
  • label string required
  • rating number required
• average_annual_salary number nullable
• occupation_average_annual_salary number nullable
• average_monthly_overtime_hours number nullable
• occupation_average_monthly_overtime_hours number nullable
• company_id string nullable
• company_url string nullable
• company_name string nullable
• company_image string nullable
• company_established string nullable
• company_representative string nullable
• company_capital string nullable
• company_revenue string nullable
• company_average_age string nullable
• company_industry string nullable
• company_employees string nullable
• company_address string nullable
• company_business string nullable

Errors

• 422 — job is not a Jobtalk job id or URL 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 posting 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.