POST /api/doda/jobs/search
Price: 20 credits
Search Doda (デューダ) job postings by free-text keyword, job category, prefecture, industry, employment type, minimum annual income and work-style/condition facets (e.g. full two-day weekend, flex time, overtime under 20h, no relocation, inexperienced welcome, listed/foreign company, women active, qualification support, English/Chinese). Returns job cards with title, company, business content, job content outline and detail, target requirements, work location, salary and salary examples, and image.
Search Doda (デューダ) jobs. Provide any of keyword (free text); job_category (sales/planning_management/office_assistant/sales_service/consulting/finance_specialist/public_education/engineer_se_infra_web/engineer_machine_electric/engineer_embedded/engineer_construction/engineer_chemistry/engineer_food/medical_specialist/creative); location (prefecture, e.g. tokyo/osaka/aichi); industry (it_telecom/finance/retail/...); employment_type (full_time/contract/other); salary_min (minimum annual income in 万円: 200/300/400/.../1000); work_styles (a list, e.g. full_two_day_weekend, flex_time, overtime_under_20, no_relocation, inexperienced_job, listed_company, women_active, english). Each result has id, url, title, company_name, business_content, job_content_outline/job_content, target_member_outline, work_location_text, salary + salary_examples and image.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)keyword string nullable — Free-text keyword to search across job content (minLength: 1)job_category string nullable — Job category to filter by (one of: "sales", "planning_management", "office_assistant", "sales_service", "consulting", "finance_specialist", "public_education", "engineer_se_infra_web", "engineer_machine_electric", "engineer_embedded", "engineer_construction", "engineer_chemistry", "engineer_food", "medical_specialist", "creative")location string nullable — Prefecture to filter by (one of: "hokkaido", "aomori", "iwate", "miyagi", "akita", "yamagata", "fukushima", "ibaraki", "tochigi", "gunma", "saitama", "chiba", "tokyo", "kanagawa", "niigata", "toyama", "ishikawa", "fukui", "yamanashi", "nagano", "gifu", "shizuoka", "aichi", "mie", "shiga", "kyoto", "osaka", "hyogo", "nara", "wakayama", "tottori", "shimane", "okayama", "hiroshima", "yamaguchi", "tokushima", "kagawa", "ehime", "kochi", "fukuoka", "saga", "nagasaki", "kumamoto", "oita", "miyazaki", "kagoshima", "okinawa", "overseas")industry string nullable — Industry to filter by (one of: "it_telecom", "internet_advertising_media", "maker_machine_electric", "maker_materials_chemistry_food", "trading", "medical_pharma", "finance", "construction_realestate", "consulting_research", "hr_outsourcing", "retail", "food_service", "transport_logistics", "energy", "travel_leisure", "security_cleaning", "beauty", "education", "agriculture_mining", "public_research", "ceremony", "other")employment_type string nullable — Employment type to filter by (one of: "full_time", "contract", "other")salary_min string nullable — Minimum desired annual income in 万円 (e.g. '400' = 400万円) (one of: "200", "250", "300", "350", "400", "450", "500", "550", "600", "650", "700", "800", "900", "1000")work_styles array — Work-style and condition facets to require (all of) (default: []; one of: "new_arrival", "near_deadline", "urgent", "full_two_day_weekend", "weekend_holiday", "annual_holiday_120", "consecutive_leave_5days", "flex_time", "overtime_under_20", "leave_on_time", "maternity_childcare_record", "no_relocation", "no_job_change_after_joining", "inexperienced_job", "inexperienced_industry", "no_education_requirement", "second_new_grad", "hire_5_or_more", "experience_10_years_welcome", "listed_company", "foreign_company", "retention_95", "women_active", "casual_dress", "car_commute_ok", "overseas_business_trip", "average_age_20s", "average_age_30s", "average_age_40s", "average_age_50s_plus", "retirement_allowance", "housing_support", "uiturn_support", "fixed_salary_250k", "fixed_salary_350k", "qualification_support", "training_support", "childcare_support", "english", "chinese", "management")count integer required — Max number of results to return (min: 1)@type string (default: "DodaJobCard")id string requiredurl string requiredcompany_name string nullablebusiness_content string nullablejob_content_outline string nullablejob_content string nullabletarget_member_outline string nullablework_location_text string nullablesalary string nullablesalary_examples array (default: [])image string nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.