/job104/companies

POST /api/job104/companies

Price: 5 credits

Get a 104 company profile: industry, capital, headcount, address, website, profile, products, benefits, management philosophy, milestones, photos, links and follower count

How to use it

Find company ids with job104/companies/search or on any job104 job; the numeric company number is accepted too. List its open jobs with job104/companies/jobs.

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", "22099131000")

Response

• @type string (default: "Job104Company")
• id string required
• url string nullable
• name string nullable
• image string nullable
• industry_code string nullable
• industry string nullable
• business string nullable
• capital integer nullable
• employee_count integer nullable
• website string nullable
• profile string nullable
• products string nullable
• benefits_text string nullable
• management_philosophy string nullable
• address string nullable
• city string nullable
• postal_code string nullable
• industrial_park string nullable
• latitude number nullable
• longitude number nullable
• phone string nullable
• fax string nullable
• contact_name string nullable
• news string nullable
• news_url string nullable
• zones array (default: [])
• links array (default: [])
  • @type string (default: "Job104Link")
  • url string required
• banners array (default: [])
  • @type string (default: "Job104Link")
  • url string required
• product_photos array (default: [])
  • @type string (default: "Job104CompanyPhoto")
  • url string required
  • thumbnail_url string nullable
  • description string nullable
  • is_cover boolean nullable
• environment_photos array (default: [])
  • @type string (default: "Job104CompanyPhoto")
  • url string required
  • thumbnail_url string nullable
  • description string nullable
  • is_cover boolean nullable
• benefit_tags array (default: [])
• legal_benefit_tags array (default: [])
• milestones array (default: [])
  • @type string (default: "Job104Milestone")
  • year integer nullable
  • month integer nullable
  • content string nullable
• follower_count 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 104 company 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.