# More precise work mode and remote classification

jobdataapi.com v4.40 / API version 1.37

---

We’ve improved how `has_remote` and `work_mode` are detected. Workplace types published by employers and recruiters (hybrid, remote or on-site) are now used directly when a listing is imported, together with labelled workplace fields and recruiter workplace tags in job descriptions. Hybrid and remote roles are recognised more reliably, while on-site roles and descriptions that only mention remote or hybrid technology no longer set `has_remote=true`.

The two fields now follow one consistent rule. `work_mode` is only set for jobs with `has_remote=true`: `1` (Hybrid), `2` (Remote), `3` (Remote Anywhere), or `4` when a remote or hybrid signal exists but the exact mode is unclear. Jobs with `has_remote=false` (on-site or no stated work arrangement) have `work_mode=null`.

Existing open listings are being corrected to the same rules over the next days, so you may see `has_remote` and `work_mode` change for some jobs, mostly fewer `4` values on jobs without a remote signal. Field names, values, filters and access tiers are unchanged: the `work_mode` field and filter remain available to **API access pro** customers and higher.

See the [Jobs API Endpoint Documentation](/c/jobs-api-endpoint-documentation/) for details.