/jobstreet/companies

POST /api/jobstreet/companies

Price: 10 credits

Get a full Jobstreet/JobsDB (SEEK South-East Asia) company profile by id or company URL across MY, SG, ID, PH, TH and HK markets: name, claimed status, website, company size, industry, primary location, specialities, description, mission statement, perks and benefits, photo gallery, logo and cover images, featured highlight, and the full employee-review rating breakdown (overall, per-category, star distribution, recommended percentage and salary-fairness percentages).

How to use it

Fetch a single Jobstreet/JobsDB company profile 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. Returns one item with name, is_claimed, organisation_id, website_url/website_name, size, industry/industry_id, primary_location, specialities, description, mission_statement, custom_statement_title/custom_statement, image (logo)/cover, brand_id, gallery (photo URLs), perks_and_benefits (title + description), featured (title/description/image/video_url), and rating (overall, review_count, recommended_percent, per-category ratings perks_and_benefits/career_opportunity/work_life_balance/work_environment/executive_management/diversity, salary_*_percent, and one_star_count through five_star_count).

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)
• 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")

Response

• @type string (default: "JobstreetCompany")
• id string required
• url string required
• country string nullable
• name string nullable
• is_claimed boolean nullable
• organisation_id string nullable
• website_url string nullable
• website_name string nullable
• size string nullable
• industry string nullable
• industry_id string nullable
• primary_location string nullable
• specialities array (default: [])
• description string nullable
• mission_statement string nullable
• custom_statement_title string nullable
• custom_statement string nullable
• image string nullable
• cover string nullable
• brand_id string nullable
• gallery array (default: [])
• perks_and_benefits array (default: [])
  • @type string (default: "JobstreetCompanyPerk")
  • description string nullable
• featured object nullable
  • @type string (default: "JobstreetCompanyFeatured")
  • description string nullable
  • image string nullable
  • video_url string nullable
• rating object nullable
  • @type string (default: "JobstreetCompanyRating")
  • overall number nullable
  • review_count integer nullable
  • recommended_percent number nullable
  • perks_and_benefits number nullable
  • career_opportunity number nullable
  • work_life_balance number nullable
  • work_environment number nullable
  • executive_management number nullable
  • diversity number nullable
  • salary_poor_percent number nullable
  • salary_fair_percent number nullable
  • salary_generous_percent number nullable
  • one_star_count integer nullable
  • two_star_count integer nullable
  • three_star_count integer nullable
  • four_star_count integer nullable
  • five_star_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 — 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.