/jobstreet/companies/jobs

POST /api/jobstreet/companies/jobs

Price: 5 credits

List the active job ads posted by a single Jobstreet/JobsDB (SEEK South-East Asia) company across MY, SG, ID, PH, TH and HK markets, identified by its employer id (the employer_id returned in a job-search card). Returns the same job cards as the search endpoint: id, title, teaser, salary, company (name, id, profile url), classifications, work types and arrangements, locations, key bullet points, featured flag, listing date, and company logo.

How to use it

List the jobs currently posted by one Jobstreet/JobsDB (SEEK South-East Asia) company. Identify the company by its employer id (the employer_id field of a jobstreet/jobs/search card, e.g. 233750) — note this is the employer/company id, not the advertiser_id and not the big company-profile id used by jobstreet/companies. Set country to pick the market (MY/SG/ID/PH on jobstreet.com, TH/HK on jobsdb.com) which drives locale and currency. Each result has id, url, country, title, teaser, salary (local-currency label), company_name, company_id, company_url, advertiser_id, employer_id, role_id, classifications (industry + subclassification), work_types, work_arrangements, locations (label + area/region), bullet_points, is_featured, listing_date, and image (company logo). An unknown id or a company with no live ads returns an empty list.

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 (employer) id, as found in a job-search card's employer_id (examples: "233750"; minLength: 1)
• count integer required — Max result count (examples: 20; 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")

Response

• @type string (default: "JobstreetJobCard")
• id string required
• url string required
• country string nullable
• teaser string nullable
• salary string nullable
• company_name string nullable
• company_id string nullable
• company_url string nullable
• advertiser_id string nullable
• employer_id string nullable
• role_id string nullable
• classifications array (default: [])
  • @type string (default: "JobstreetSearchClassification")
  • classification string nullable
  • classification_id string nullable
  • subclassification string nullable
  • subclassification_id string nullable
• work_types array (default: [])
• work_arrangements array (default: [])
• locations array (default: [])
  • @type string (default: "JobstreetSearchLocation")
  • label string nullable
  • country_code string nullable
  • area string nullable
  • region string nullable
• bullet_points array (default: [])
• is_featured boolean nullable
• listing_date string nullable
• listing_date_display string nullable
• image 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.