Jobs API endpoint
Returns a single Workday posting's full detail (description, location, req id). path is the externalPath from a board listing. tenant/datacenter/site as in the board endpoint.
/jobs/workday/jobQuery parameters:
tenant (required) — Workday tenant.datacenter (required) — Workday datacenter shard (wd1, wd3, wd5, ...).site (required) — Workday career site.path (required) — the job externalPath from a board listing (e.g. /job/US-CA/Engineer_JR123).Returns a single Job (provider, id, title, company, department, team, location, locations[], remote, workplace_type, employment_type, url, apply_url, req_id, posted_at, posted_age_text, description_html, description_text, compensation, compensation_min, compensation_max, compensation_currency, compensation_period) with description_html/description_text and a real posted_at date. An unknown path returns 404. Workday has no structured compensation field; the compensation_* fields are populated only when the description states an explicit pay figure near a salary/compensation keyword (many postings state no figure at all, in which case they stay empty).
company is the Workday hiringOrganization legal-entity name (e.g. 2100 NVIDIA USA); it falls back to the tenant slug on the rare payload missing that field.
| Field | In the sample | Value in the sample |
|---|---|---|
| provider | Has a value | “workday” |
| id | Has a value | |
| title | Has a value | “Chip Design Engineer” |
| company | Has a value | “IL00 Mellanox Technologies, Ltd.” |
| location | Has a value | “Israel, Tel Aviv” |
| employment_type | Has a value | “Full time” |
| url | Has a value | nvidia.wd5.myworkdayjobs.com |
| apply_url | Has a value | nvidia.wd5.myworkdayjobs.com |
| req_id | Has a value | |
| posted_at | Has a value | 2026-10-04 |
| posted_age_text | Has a value | “Posted 9 Days Ago” |
| description_html | Has a value | 1,993 characters |
| description_text | Has a value | 1,631 characters |
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| tenant | string | Yes | Workday tenant | nvidia | |
| datacenter | string | Yes | Workday datacenter shard | wd5 | |
| site | string | Yes | Workday career site | NVIDIAExternalCareerSite | |
| path | string | Yes | Job externalPath from a board listing | /job/Israel-Tel-Aviv/Chip-Design-Engineer_JR2016289 | |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/jobs/workday/job?tenant=nvidia&datacenter=wd5&site=NVIDIAExternalCareerSite&path=%2Fjob%2FIsrael-Tel-Aviv%2FChip-Design-Engineer_JR2016289" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"code": 200,
"msg": "OK",
"data": {
"provider": "workday",
"id": "/job/US-CA-Santa-Clara/Engineer_JR2020246",
"title": "Senior Engineer",
"company": "2100 NVIDIA USA",
"location": "US, CA, Santa Clara",
"employment_type": "Full time",
"req_id": "JR2020246",
"posted_at": "2026-07-10",
"posted_age_text": "Posted Today",
"url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/...",
"description_text": "NVIDIA is ..."
}
}Request schema
No body schema
Response schema
#/definitions/jobs.jobResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | jobs.Job | No | ||||
| data.ai_tools_mentioned | array | No | AITools lists canonical AI tool and platform names mentioned in the job title or description, such as "ChatGPT" or "GitHub Copilot". | |||
| data.apply_url | string | No | Link to the application page for the job. | |||
| data.benefits_mentioned | array | No | Benefits, Clearance, and Education contain canonical requirements and offerings mentioned in the job title or description. | |||
| data.company | string | No | Name of the hiring company. | |||
| data.company_logo_url | string | No | URL of the company's logo. | |||
| data.compensation | string | No | Compensation is the raw provider summary; the *Min/*Max/*Currency fields are parsed from it when the summary contains a recognizable pay range/amount. CompensationPeriod is the pay period ("hourly", "daily", "weekly", "monthly", "yearly") when the summary states one explicitly; empty when no period is stated (most single "$150K – $190K"-style ranges are implicitly annual but that is never asserted here). | |||
| data.compensation_currency | string | No | Currency code of the pay range, for example `USD`. | |||
| data.compensation_max | number | No | Upper end of the pay range stated in the posting. | |||
| data.compensation_min | number | No | Lower end of the pay range stated in the posting. | |||
| data.compensation_period | string | No | Pay period the posting states: `hourly`, `daily`, `weekly`, `monthly` or `yearly`. Omitted when the posting names none. | |||
| data.department | string | No | Department the job belongs to. | |||
| data.description_html | string | No | Job description as HTML. | |||
| data.description_text | string | No | Job description as plain text. | |||
| data.education_level_required | array | No | Education levels mentioned in the job title or description. | |||
| data.employment_type | string | No | Employment type the provider lists, such as full-time or contract. | |||
| data.id | string | No | Posting id within the provider. Use it with the provider's job endpoint. | |||
| data.location | string | No | Primary job location as the provider shows it. | |||
| data.location_city | string | No | LocationCity/State/Country are the structured components behind Location when the provider exposes them (or once the geo-enrich worker has resolved them from the free-text Location string) -- present only for the primary/first location, matching Location itself. | |||
| data.location_country | string | No | Country of the primary location. | |||
| data.location_state | string | No | State or region of the primary location. | |||
| data.locations | array | No | All locations listed for the job. | |||
| data.posted_age_text | string | No | Workday relative age ("Posted Today") | |||
| data.posted_at | string | No | RFC3339 / date when the provider gives one | |||
| data.provider | string | No | Applicant tracking system the posting comes from, for example `greenhouse` or `lever`. | |||
| data.remote | boolean | No | True when the posting is marked as remote. | |||
| data.req_id | string | No | Requisition id the company uses for the job. | |||
| data.security_clearance_required | array | No | Security clearances mentioned in the job title or description. | |||
| data.skills_mentioned | array | No | Skills lists canonical ESCO skill labels mentioned in the job title or description. | |||
| data.team | string | No | Team the job belongs to. | |||
| data.title | string | No | Job title as the company posted it. | |||
| data.url | string | No | Link to the job posting page. | |||
| data.workplace_type | string | No | Workplace arrangement the provider lists, such as remote, hybrid or on-site. | |||
| msg | string | No | OK |
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/jobs/workday/job?tenant=nvidia&datacenter=wd5&site=NVIDIAExternalCareerSite&path=%2Fjob%2FIsrael-Tel-Aviv%2FChip-Design-Engineer_JR2016289" \
-H "x-api-key: $CRAWLORA_API_KEY"