/jobstreet/roles

POST /api/jobstreet/roles

Price: 1 credit

Get the career-insights profile for a role on Jobstreet/JobsDB (SEEK South-East Asia) across MY, SG, ID, PH, TH and HK markets: employee-rated job satisfaction and sub-scores (remuneration, employability, work-life balance, diversity of tasks, career progression), year-on-year demand growth, the number of live jobs for the role, and work-hours patterns (overtime, weekend, shift and late-night frequency).

How to use it

Fetch the career-insights profile for a role by alias or title (e.g. software-engineer or 'Data Analyst'). Set country to pick the market (MY/SG/ID/PH on jobstreet.com, TH/HK on jobsdb.com). Returns one item with review_count, job_satisfaction and the sub-scores remuneration, employability, work_life_balance, diversity_in_tasks and career_progression_opportunities (each rated out of 5), growth_percent with growth_start_year/growth_end_year, job_count and job_count_url, and the work-hours breakdown overtime, weekends, shift_work and late_nights (each a never/sometimes/often percentage split) plus work_hours_sample_count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• role string required — Role alias or title, e.g. software-engineer (examples: "software-engineer", "Data Analyst"; 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: "JobstreetRole")
• id string required
• country string nullable
• review_count integer nullable
• job_satisfaction number nullable
• remuneration number nullable
• employability number nullable
• work_life_balance number nullable
• diversity_in_tasks number nullable
• career_progression_opportunities number nullable
• growth_percent number nullable
• growth_start_year integer nullable
• growth_end_year integer nullable
• job_count integer nullable
• job_count_url string nullable
• overtime object nullable
  • @type string (default: "JobstreetRoleWorkHours")
  • never number nullable
  • sometimes number nullable
  • often number nullable
• weekends object nullable
  • @type string (default: "JobstreetRoleWorkHours")
  • never number nullable
  • sometimes number nullable
  • often number nullable
• shift_work object nullable
  • @type string (default: "JobstreetRoleWorkHours")
  • never number nullable
  • sometimes number nullable
  • often number nullable
• late_nights object nullable
  • @type string (default: "JobstreetRoleWorkHours")
  • never number nullable
  • sometimes number nullable
  • often number nullable
• work_hours_sample_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 — Role not found (no career-insights profile for the given role) 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.