/job104/companies/jobs

POST /api/job104/companies/jobs

Price: 10 credits

List the open jobs of a 104 company, filtered by keyword, area, job category and employment type: title, description, location, experience, education, salary, applicant range and posting date

How to use it

Pass a returned id to job104/jobs for the full job; featured jobs come first in company order.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — 104 company id or company URL (examples: "a5h92m0", "https://www.104.com.tw/company/a5h92m0")
• count integer required — Max number of jobs to return (min: 1)
• sort string — Result ordering (default: "company_order"; one of: "company_order", "newest", "oldest")
• keyword string nullable — Only jobs matching this keyword (examples: "engineer"; minLength: 1)
• area_codes array nullable — 104 area codes, city or district (examples: ["6001006000"], ["6001001001"])
• job_category_codes array nullable — 104 job category codes (examples: ["2008000000"], ["2008001023"])
• employment_type string nullable — Employment type (one of: "full_time", "part_time", "senior")

Response

• @type string (default: "Job104CompanyJob")
• id string required
• url string nullable
• company_id string required
• description string nullable
• location string nullable
• postal_code string nullable
• experience string nullable
• education string nullable
• salary string nullable
• applicants_range string nullable
• is_featured boolean nullable
• employer_resume_activity string nullable
• employer_contact_activity string nullable
• posted_date 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.