/rikunabi/jobs

POST /api/rikunabi/jobs

Price: 5 credits

Get Rikunabi NEXT job details by job key

How to use it

Get full details of a Rikunabi NEXT (リクナビNEXT) job posting by its job key. Returns the job title and catchphrase, the hiring company, employment types, the full job overview, job description, and required qualifications, salary (summary, base, task-based, detailed breakdown, and structured min/max), work hours and style, holidays, probationary period, insurance and welfare benefits, work environment, commute info, office name and address, application process, the employer's appeal message, headcount, preference tags, job photos, a short work-location summary, structured job location, an AI company research brief (markdown summary with cited sources), the employer profile (CEO, address, phone, business details, website), and publication date.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Rikunabi NEXT job key, or a job URL containing it (examples: "jk0c94088037a11455", "https://next.rikunabi.com/viewjob/jk0c94088037a11455/"; minLength: 1)

Response

• @type string (default: "RikunabiJob")
• id string required
• url string required
• sub_title string nullable
• company_name string nullable
• company_id string nullable
• employment_types array (default: [])
• job_overview string nullable
• job_description string nullable
• qualification string nullable
• salary_summary string nullable
• base_salary string nullable
• task_based_salary string nullable
• salary_info string nullable
• salary_example string nullable
• salary object nullable
  • @type string (default: "RikunabiJobSalary")
  • min integer nullable
  • max integer nullable
  • currency string nullable
  • unit string nullable
• work_hours string nullable
• work_style string nullable
• holidays string nullable
• probationary_period string nullable
• welfare_insurance string nullable
• welfare_benefit string nullable
• work_environment string nullable
• work_location string nullable
• work_location_notes string nullable
• commute_info string nullable
• office_name string nullable
• office_address string nullable
• apply_info string nullable
• employer_message string nullable
• position_count string nullable
• other string nullable
• industry string nullable
• is_full_remote boolean nullable
• published_at string nullable
• preference_tags array (default: [])
• images array (default: [])
• image string nullable
• location object nullable
  • @type string (default: "RikunabiJobLocation")
  • street_address string nullable
  • address_locality string nullable
  • address_region string nullable
  • postal_code string nullable
• company_research object nullable
  • @type string (default: "RikunabiCompanyResearch")
  • summary string nullable
  • citations array (default: [])
    • @type string (default: "RikunabiResearchCitation")
    • id string nullable
    • url string nullable
    • favicon_url string nullable
  • updated_at string nullable
• employer object nullable
  • @type string (default: "RikunabiJobEmployer")
  • name string nullable
  • ceo_name string nullable
  • address string nullable
  • phone string nullable
  • business_details string nullable
  • web_url string nullable
• favorite_count integer nullable
• apply_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 — Job 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.