/jobtalk/jobs/search

POST /api/jobtalk/jobs/search

Price: 10 credits

Search job postings on Jobtalk (転職会議) by keyword, prefecture, city, job category, industry, employment type, minimum annual salary and working conditions: title, summary, annual salary range, locations and the hiring company with its Jobtalk rating and review count

How to use it

Results come grouped by company, every matching posting of one company before the next. Pass a returned id to jobtalk/jobs for the full posting and company_id to jobtalk/companies for the employer's reviews.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Free-text keyword (examples: "エンジニア", "経理"; minLength: 1)
• prefecture_ids array nullable — Work location prefectures, JIS prefecture codes (examples: [13], [13,14])
• city_codes array nullable — Work location cities, six-digit local government codes (examples: ["131016"])
• job_category_ids array nullable — Jobtalk job category ids (examples: [1,2])
• industry_ids array nullable — Jobtalk industry ids (examples: [4])
• employment_types array nullable — Employment types (one of: "full_time", "contract", "part_time", "other"; examples: ["full_time"])
• min_annual_salary integer nullable — Minimum annual salary in yen (examples: 6000000; min: 10000)
• exclude_undisclosed_salary boolean — Leave out postings that do not state a salary (default: false)
• inexperienced_welcome boolean — Only postings open to applicants without experience (default: false)
• new_only boolean — Only recently posted jobs (default: false)
• closing_soon boolean — Only postings that close soon (default: false)
• conditions array nullable — Required working conditions (one of: "no_education_requirement", "no_age_limit", "two_days_off_weekly"; examples: ["two_days_off_weekly"])
• count integer required — Max number of results (min: 1; max: 1000)

Response

• @type string (default: "JobtalkJobSearchResult")
• id string required
• url string required
• description string nullable
• annual_salary_min number nullable
• annual_salary_max number nullable
• salary_text string nullable
• prefectures array (default: [])
• other_location_count integer nullable
• job_category string nullable
• is_new boolean nullable
• is_closing_soon boolean nullable
• company_id string required
• company_name string nullable
• company_url string required
• company_rating number nullable
• company_review_count integer nullable
• company_industry string nullable
• company_prefecture string nullable
• company_job_count integer 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.