/job104/companies/search

POST /api/job104/companies/search

Price: 5 credits

Search 104 companies by keyword with area, industry, job category, headcount, benefit, company type, science park and hiring filters: company cards with industry, capital, headcount, profile, open job count, rating and benefit tags

How to use it

104 serves at most the first 100 result pages of a query, so narrow with filters to reach more. Pass a returned id to job104/companies for the full profile or to job104/companies/jobs for its open jobs.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of companies to return (min: 1; max: 1800)
• keyword string nullable — Company search keyword (examples: "科技"; minLength: 1)
• sort string — Result ordering (default: "relevance"; one of: "relevance", "capital", "employees")
• area_codes array nullable — 104 area codes (examples: ["6001001000"])
• industry_codes array nullable — 104 industry codes (examples: ["1001001000"])
• job_category_codes array nullable — 104 job category codes of the company's open jobs (examples: ["2007000000"])
• size string nullable — Headcount band (one of: "up_to_4", "5_to_9", "10_to_29", "30_to_49", "50_to_99", "100_to_249", "250_to_499", "500_plus")
• benefits array nullable — Benefits the company offers (one of: "year_end_bonus", "holiday_bonus", "employee_travel", "profit_sharing", "allowances", "flexible_hours", "health_checkup", "group_insurance", "more_annual_leave_than_law", "paid_sick_leave", "birthday_leave", "new_hire_leave", "dormitory", "transport_allowance", "parking", "shuttle_bus", "rent_allowance", "childcare_center", "pets_allowed", "children_education_allowance", "family_day", "free_snacks", "staff_canteen", "employee_discount", "team_dinners", "clubs", "education_allowance", "certificate_bonus", "language_learning_allowance", "gym", "counseling", "massage", "idle_shift_allowance"; examples: ["year_end_bonus"])
• all_benefits boolean — Require every listed benefit instead of any one (default: true)
• company_type string nullable — Listed or foreign companies only (one of: "listed", "foreign")
• science_park string nullable — Science park the company is in (one of: "hsinchu", "central_taiwan", "southern_taiwan", "neihu", "nangang", "xizhi")
• hiring_only boolean — Only companies with open jobs (default: false)

Response

• @type string (default: "Job104CompanyCard")
• id string required
• url string nullable
• name string nullable
• image string nullable
• location string nullable
• industry_code string nullable
• industry string nullable
• capital integer nullable
• employee_count integer nullable
• profile string nullable
• open_job_count integer nullable
• rating number nullable
• zones array (default: [])
• benefit_tags array (default: [])
• job_categories array (default: [])
• has_employer_brand_badge boolean 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.