/jobstreet/companies/reviews

POST /api/jobstreet/companies/reviews

Price: 5 credits

Get employee reviews for a Jobstreet/JobsDB (SEEK South-East Asia) company by id or company URL across MY, SG, ID, PH, TH and HK markets: review title, pros and cons, job title, work location, overall rating, per-category ratings, salary summary, employment status, recommendation, helpful votes, review date and the employer reply when present.

How to use it

Fetch employee reviews for a Jobstreet/JobsDB company by numeric id (e.g. 168552725744507) or company URL. Set country to pick the market (MY/SG/ID/PH on jobstreet.com, TH/HK on jobsdb.com) which drives locale and currency labels, and sort to order by 'most recent' or 'most helpful'. Returns up to count items, each with title, pros, cons, job_title, work_location, overall_rating, ratings (per-category category + value), salary_summary, employment_status, is_recommended, has_been_flagged, helpful_count, created_date, and reply (employer response with author, text and created_at) when present.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Jobstreet/JobsDB company id or a company profile URL containing it (examples: "168552725744507", "https://my.jobstreet.com/companies/aeon-168552725744507"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• country string — Market: MY/SG/ID/PH on jobstreet.com, TH/HK on jobsdb.com (drives locale and currency) (default: "MY"; one of: "MY", "SG", "ID", "PH", "TH", "HK")
• sort string — Review ordering (default: "most_recent"; one of: "most_recent", "most_helpful")

Response

• @type string (default: "JobstreetCompanyReview")
• id string required
• company_id string nullable
• country string nullable
• pros string nullable
• cons string nullable
• overall_experience string nullable
• job_title string nullable
• work_location string nullable
• overall_rating number nullable
• salary_summary string nullable
• employment_status string nullable
• is_recommended boolean nullable
• has_been_flagged boolean nullable
• helpful_count integer nullable
• created_date string nullable
• ratings array (default: [])
  • @type string (default: "JobstreetCompanyReviewRating")
  • category string nullable
  • value number nullable
• reply object nullable
  • @type string (default: "JobstreetCompanyReviewReply")
  • author string nullable
  • text string nullable
  • created_at 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 — Company not found (well-formed but nonexistent company 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.