/rikunabi/jobs/search

POST /api/rikunabi/jobs/search

Price: 20 credits

Search Rikunabi NEXT jobs by keyword and filters

How to use it

Search Rikunabi NEXT (リクナビNEXT) job postings. At least one search condition is required (keyword, location, job_category, annual_salary, employment_type, preference or new_only) — restrict by work location prefecture, job category, minimum annual salary, employment type, and any combination of refined condition tags (remote-OK, no-relocation, weekend-holidays, no-overtime, and many more); order by relevance or newest, and optionally limit to newly posted jobs. Each result carries the job key and URL, title and catchphrase, hiring company, location with coordinates, employment types, salary (text and structured min/max), a qualification preview, preference tags, job photo, and publication timestamp.

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 search keyword (minLength: 1)
• count integer required — Max number of jobs to return (min: 1)
• location string nullable — Work location prefecture (one of: "area-hokkaido", "area-aomori", "area-iwate", "area-miyagi", "area-akita", "area-yamagata", "area-fukushima", "area-tokyo", "area-kanagawa", "area-saitama", "area-chiba", "area-ibaraki", "area-tochigi", "area-gunma", "area-niigata", "area-toyama", "area-ishikawa", "area-fukui", "area-yamanashi", "area-nagano", "area-aichi", "area-shizuoka", "area-gifu", "area-mie", "area-osaka", "area-kyoto", "area-hyogo", "area-nara", "area-shiga", "area-wakayama", "area-tottori", "area-shimane", "area-okayama", "area-hiroshima", "area-yamaguchi", "area-tokushima", "area-kagawa", "area-ehime", "area-kochi", "area-fukuoka", "area-saga", "area-nagasaki", "area-kumamoto", "area-oita", "area-miyazaki", "area-kagoshima", "area-okinawa")
• job_category string nullable — Job category group (one of: "oc-selling", "oc-promotion", "oc-corporatestaff", "oc-scm", "oc-administration", "oc-retail", "oc-hospitality", "oc-foodservice", "oc-consulting", "oc-technology", "oc-design", "oc-building", "oc-realestate", "oc-electronic", "oc-chemicals", "oc-consumergoods", "oc-pharmaceuticals", "oc-medicaldevices", "oc-medical", "oc-financial", "oc-culinary", "oc-broadcasting", "oc-infrastructure", "oc-transportation", "oc-recruitment", "oc-instruction", "oc-executive", "oc-analysis", "oc-publicsector")
• annual_salary string nullable — Minimum annual salary threshold (one of: "sal-over200", "sal-over300", "sal-over400", "sal-over500", "sal-over600", "sal-over700", "sal-over800", "sal-over900", "sal-over1000")
• employment_type string nullable — Employment type (one of: "emp-permanent", "emp-temporary", "emp-contractor", "emp-contract")
• preference array nullable — Refined condition tags (multi-select) (one of: "prf-001", "prf-002", "prf-003", "prf-004", "prf-005", "prf-006", "prf-007", "prf-008", "prf-009", "prf-010", "prf-011", "prf-012", "prf-013", "prf-014", "prf-015", "prf-017", "prf-018", "prf-019", "prf-020", "prf-021", "prf-022", "prf-023", "prf-024", "prf-025", "prf-026", "prf-027", "prf-028", "prf-029", "prf-030", "prf-031", "prf-032", "prf-033", "prf-034", "prf-035", "prf-036", "prf-037", "prf-038", "prf-039", "prf-040", "prf-041", "prf-042", "prf-043", "prf-044", "prf-045", "prf-046", "prf-047", "prf-048", "prf-049", "prf-050", "prf-051", "prf-052", "prf-053", "prf-054", "prf-055", "prf-056", "prf-057", "prf-058", "prf-059", "prf-060", "prf-061", "prf-062", "prf-063", "prf-064", "prf-065")
• sort string — Result ordering (default: "relevance"; one of: "relevance", "newest")
• new_only boolean — Only newly posted jobs (default: false)

Response

• @type string (default: "RikunabiJobCard")
• id string required
• url string required
• title_pr string nullable
• company_name string nullable
• company_id string nullable
• location string nullable
• lat number nullable
• lon number nullable
• employment_types array (default: [])
• salary_text string nullable
• salary object nullable
  • @type string (default: "RikunabiCardSalary")
  • min integer nullable
  • max integer nullable
  • currency string nullable
  • unit string nullable
• qualification string nullable
• preference_tags array (default: [])
• image string nullable
• is_new_arrival boolean nullable
• published_at 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.