/job1111/jobs

POST /api/job1111/jobs

Price: 1 credit

Get a 1111 job by id: title, description, company, location, salary, job type, requirements, benefits, applicant count, views and update time

How to use it

Find job ids with job1111/jobs/search or job1111/companies/jobs.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "Job1111Job")
• id string required
• url string nullable
• description string nullable
• company_id string nullable
• company_name string nullable
• company_url string nullable
• company_logo string nullable
• industry_code string nullable
• industry string nullable
• location_code string nullable
• location string nullable
• mrt_station_code string nullable
• mrt_distance_m integer nullable
• mrt_walk_seconds integer nullable
• job_type string nullable
• salary string nullable
• salary_type string nullable
• salary_min integer nullable
• salary_max integer nullable
• is_paid_daily boolean nullable
• experience_code string nullable
• education_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 nullable
  • name string nullable
• company_tag_codes array (default: [])
• is_happy_company boolean nullable
• is_top boolean nullable
• has_media boolean nullable
• reply_in_days integer nullable
• applicant_count integer nullable
• applicants_range string nullable
• view_count integer nullable
• updated_at 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 — No 1111 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.