POST /api/doda/jobs
Price: 5 credits
Get full Doda (デューダ) job posting details by job id (or job URL): title, hiring company (name, business content, address, establishment, capital, representative, employee count, website), job category and industry breadcrumb, employment type, job content, target requirements, salary, annual income range, estimated income model, bonus/raise/incentive/probation, benefits and company perks, team structure, gender ratio and age composition, holidays (annual count, weekly pattern and the full paid/national/summer/golden-week/new-year/maternity/childcare/family-care matrix with explanations), working hours and overtime, application method and selection flow, PR highlights, editorial interview report, publishing period, work locations and image.
Fetch a single Doda (デューダ) job posting by numeric job id (e.g. '3015172411') or a full job URL. Returns one job with title, tags (feature badges, e.g. 正社員/新着/転勤なし/5名以上採用), company (name/business_content/address/establish_year/establishment_date/capital/sales/representative/employee_count/average_age/web_url), job_category_large/medium/small, industry_large/small, employment_type, job_content_outline/job_content, target_member_outline/target_member, selection_point, salary + salary_examples + annual_income_lower/upper (in 万円) + estimated_annual_incomes, raise_description/number_of_salary_increases, bonus/number_of_bonuses, incentive, probation_period, treatment_and_welfare + company_benefits, team_structure, organization_category, gender_ratio, age_composition, retention_rate, age_limit_display, holiday + annual_holiday(+explanation) + holiday_week(+explanation) and the has_* holiday flags (paid/national/summer/golden_week/new_year/condolence/maternity/childcare/family_care) each with their *_holiday_explanation, work_time, average_overtime_hours(+explanation), application_method, selection_process + selection_flows, pr_spaces, article_summary, interview (title/text/rewarding/difficult/image), publishing_start_date/end_date, locations (address + nearest station) and image.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)job string required — Doda job as a numeric job id or a full job URL (examples: "3015172411", "https://doda.jp/DodaFront/View/JobSearchDetail/j_jid__3015172411/"; minLength: 1)@type string (default: "DodaJob")id string requiredurl string requiredcompany object nullable@type string (default: "DodaJobCompany")id string nullablename string nullablegroup_name string nullablebusiness_content string nullableaddress string nullableestablish_year string nullableestablishment_date string nullablecapital string nullablesales string nullablerepresentative string nullableemployee_count string nullableaverage_age string nullableaverage_age_explanation string nullableweb_url string nullablejob_category_large string nullablejob_category_medium string nullablejob_category_small string nullableindustry_large string nullableindustry_small string nullableemployment_type string nullablejob_content_outline string nullablejob_content string nullabletarget_member_outline string nullabletarget_member string nullableselection_point string nullablework_location_text string nullablework_time string nullablesalary string nullablesalary_examples array (default: [])annual_income_lower integer nullableannual_income_upper integer nullableestimated_annual_incomes array (default: [])@type string (default: "DodaEstimatedIncome")income string nullableexplanation string nullableraise_description string nullablenumber_of_salary_increases string nullablebonus string nullablenumber_of_bonuses string nullableincentive string nullableprobation_period string nullabletreatment_and_welfare string nullablecompany_benefits string nullableteam_structure string nullableorganization_category string nullablegender_ratio string nullableage_composition string nullableretention_rate string nullableage_limit_display string nullableholiday string nullableannual_holiday integer nullableannual_holiday_explanation string nullableholiday_week string nullableholiday_week_explanation string nullablehas_paid_holidays boolean nullablepaid_holidays_explanation string nullablehas_national_holiday boolean nullablenational_holiday_explanation string nullablehas_summer_holiday boolean nullablesummer_holiday_explanation string nullablehas_golden_week_holiday boolean nullablegolden_week_holiday_explanation string nullablehas_new_year_holiday boolean nullablenew_year_holiday_explanation string nullablehas_condolence_holiday boolean nullablecondolence_holiday_explanation string nullablehas_maternity_holiday boolean nullablematernity_holiday_explanation string nullablehas_childcare_holiday boolean nullablechildcare_holiday_explanation string nullablehas_family_care_holiday boolean nullablefamily_care_holiday_explanation string nullableaverage_overtime_hours string nullableaverage_overtime_hours_explanation string nullableapplication_method string nullableselection_process string nullableselection_flows array (default: [])pr_spaces array (default: [])@type string (default: "DodaPrSpace")heading string nullabletext string nullablearticle_summary array (default: [])tags array (default: [])interview object nullable@type string (default: "DodaInterview")text string nullablerewarding string nullabledifficult string nullableimage string nullableimage_caption string nullablepublishing_start_date string nullablepublishing_end_date string nullableimage string nullablelocations array (default: [])@type string (default: "DodaJobLocation")address string nullablestation 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 — Job not found (well-formed job id but the posting does not exist or has expired) 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.