/job104/jobs

POST /api/job104/jobs

Price: 1 credit

Get a 104 job: full description, salary, job categories, work conditions, location, required experience, education, languages, tools, skills and licenses, benefits, workplace photos, HR contact and applicant range

How to use it

Find job ids with job104/jobs/search or job104/companies/jobs; the numeric job number is accepted too.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — 104 job id or job URL (examples: "95mnd", "https://www.104.com.tw/job/95mnd", "15379177")

Response

• @type string (default: "Job104Job")
• id string required
• url string nullable
• description string nullable
• posted_date integer nullable
• close_date integer nullable
• company_id string nullable
• company_name string nullable
• company_url string nullable
• company_logo string nullable
• company_industry_code string nullable
• company_industry string nullable
• company_employee_count integer nullable
• is_china_funded boolean nullable
• job_categories array (default: [])
  • @type string (default: "Job104Category")
  • code string nullable
  • name string nullable
• salary string nullable
• salary_type string nullable
• salary_min integer nullable
• salary_max integer nullable
• employment_type string nullable
• hire_type_code integer nullable
• delegated_for_industry string nullable
• remote_work string nullable
• remote_work_note string nullable
• work_period_tag_codes array (default: [])
• part_time_periods array (default: [])
• openings string nullable
• start_date string nullable
• management string nullable
• business_trip string nullable
• working_hours string nullable
• shifts array (default: [])
• vacation_policy string nullable
• location_code string nullable
• city string nullable
• region string nullable
• address string nullable
• postal_code string nullable
• industrial_park string nullable
• landmark string nullable
• latitude number nullable
• longitude number nullable
• accepted_roles array (default: [])
• accepted_disabilities array (default: [])
  • @type string (default: "Job104Disability")
  • category string nullable
  • level integer nullable
• requires_disability_certificate boolean nullable
• experience string nullable
• education string nullable
• majors array (default: [])
• language_requirements array (default: [])
  • @type string (default: "Job104LanguageRequirement")
  • language string nullable
  • listening string nullable
  • speaking string nullable
  • reading string nullable
  • writing string nullable
• tools array (default: [])
• skills array (default: [])
• certificates array (default: [])
• driver_licenses array (default: [])
• other_requirements string nullable
• benefit_tags array (default: [])
• legal_benefit_tags array (default: [])
• benefits_text string nullable
• environment_photos array (default: [])
  • @type string (default: "Job104Photo")
  • url string required
  • thumbnail_url string nullable
  • description string nullable
• banner_images array (default: [])
• contact_name string nullable
• contact_phones array (default: [])
• contact_note string nullable
• visit_address string nullable
• reply_policy string nullable
• applicants_range string nullable
• employer_resume_activity string nullable
• employer_contact_activity string 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 — No 104 job under that id 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.