/yourator/companies/search

POST /api/yourator/companies/search

Price: 1 credit

List the companies hiring on Yourator (yourator.co), optionally by industry, city or tag. Each company carries its short description, industry, tags, city, country, badges, logo and banner.

How to use it

Pass a company alias to yourator/companies for the full profile or yourator/companies/jobs for its 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: 300)
• categories array nullable — Industries (one of: "網路", "社會企業", "教育 / 線上課程", "電商 / O2O", "FinTech / 區塊鏈", "設計 / 文創", "行銷 / 媒體 / 廣告", "物聯網 / 硬體", "旅遊", "VR / 動畫 / 遊戲", "軟體開發", "SaaS / 商務服務", "實體零售", "娛樂媒體", "半導體", "金融", "生物 / 醫療科技", "服務 / 物業管理", "運動 / 健康", "資訊安全")
• areas array nullable — City or county codes, or oversea (one of: "TPE", "NWT", "TAO", "TXG", "TNN", "KHH", "KEE", "HSZ", "HSQ", "MIA", "YUN", "CHA", "NAN", "CYI", "CYQ", "ILA", "HUA", "TTT", "PIF", "PEN", "KIN", "LIE", "oversea")
• tags array nullable — Company tags (examples: ["SaaS"], ["AI"])

Response

• @type string (default: "YouratorCompanySummary")
• id string required
• alias string required
• url string required
• name string nullable
• short_description string nullable
• category string nullable
• tags array (default: [])
• area_code string nullable
• city string nullable
• country_code string nullable
• country string nullable
• badges array (default: [])
• image string nullable
• banner string 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.