POST /api/job1111/companies/jobs
Price: 10 credits
List the open jobs of a 1111 company: title, description, location, salary, job type, requirements, benefits, applicant count, views and update time
An unknown company id returns an empty list.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)company string required — 1111 company id or company URL (examples: "290855", "https://www.1111.com.tw/corp/290855")count integer required — Max number of jobs to return (min: 1)sort string — Result ordering (default: "newest"; one of: "relevance", "newest", "salary", "experience", "region")@type string (default: "Job1111Job")id string requiredurl string nullabledescription string nullablecompany_id string nullablecompany_name string nullablecompany_url string nullablecompany_logo string nullableindustry_code string nullableindustry string nullablelocation_code string nullablelocation string nullablemrt_station_code string nullablemrt_distance_m integer nullablemrt_walk_seconds integer nullablejob_type string nullablesalary string nullablesalary_type string nullablesalary_min integer nullablesalary_max integer nullableis_paid_daily boolean nullableexperience_code string nullableeducation_levels array (default: [])major_codes array (default: [])driving_license_codes array (default: [])certificate_codes array (default: [])internship_codes array (default: [])reminder_codes array (default: [])benefit_codes array (default: [])highlighted_benefits array (default: [])@type string (default: "Job1111Benefit")code string nullablename string nullablecompany_tag_codes array (default: [])is_happy_company boolean nullableis_top boolean nullablehas_media boolean nullablereply_in_days integer nullableapplicant_count integer nullableapplicants_range string nullableview_count integer nullableupdated_at integer 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.