Jobs API endpoint
Lists a company's public Workday (CXS) postings, paged via limit/offset. tenant, datacenter (wd1/wd3/wd5/...), and site all come from the careers URL https://{tenant}.wd5.myworkdayjobs.com/{site}.
/jobs/workday/boardQuery parameters:
tenant (required) — Workday tenant (e.g. nvidia).datacenter (required) — Workday datacenter shard, e.g. wd1, wd3, wd5 (from the careers URL host).site (required) — Workday career site (e.g. NVIDIAExternalCareerSite).search (optional) — free-text search.limit (optional, default 20, max 20) — page size (Workday caps a page at 20).offset (optional, default 0) — page offset.Returns provider, company, count, total (whole-board size), and jobs[] (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; the list carries posted_age_text such as Posted Today rather than an absolute date) plus source_url. Each job's company is the tenant slug (the board listing doesn't expose the full legal-entity name — call /jobs/workday/job for that). employment_type on the list is populated when the tenant's Workday configuration includes it on the board endpoint; it is always present on /jobs/workday/job. Use each job's id (its externalPath) with /jobs/workday/job for full detail. The list carries no description, so compensation/compensation_min/compensation_max/compensation_currency/compensation_period are never populated on the board listing — call /jobs/workday/job for a posting's compensation, when the tenant states a pay figure in the description.
| Field | Filled in, of 20 checked | Values in the sample |
|---|---|---|
| provider | 20 | workday in all 20 |
| id | 19 | |
| title | 19 | “Hardware Validation Engineer” and 18 other values |
| company | 20 | Nvidia in all 20 |
| location | 19 | “Israel, Yokneam” and 9 other values |
| url | 20 | nvidia.wd5.myworkdayjobs.com |
| req_id | 20 | |
| posted_age_text | 19 | Posted Today in all 19 |
| remote | 1 | true in 1 of 1 |
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| tenant | string | Yes | Workday tenant | nvidia | |
| datacenter | string | Yes | Workday datacenter shard (wd1, wd3, wd5, ...) | wd5 | |
| site | string | Yes | Workday career site | NVIDIAExternalCareerSite | |
| search | string | No | Free-text search | ||
| limit | integer | No | Page size, default 20, max 20 | ||
| offset | integer | No | Page offset, default 0 | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/jobs/workday/board?tenant=nvidia&datacenter=wd5&site=NVIDIAExternalCareerSite&limit=10" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"code": 200,
"msg": "OK",
"data": {
"provider": "workday",
"company": "nvidia",
"count": 20,
"total": 2000,
"jobs": [
{
"provider": "workday",
"id": "/job/US-CA-Santa-Clara/Engineer_JR2020246",
"title": "Senior Engineer",
"company": "nvidia",
"location": "4 Locations",
"employment_type": "Full time",
"posted_age_text": "Posted Today",
"req_id": "JR2020246",
"url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Engineer_JR2020246"
}
],
"source_url": "https://nvidia.wd5.myworkdayjobs.com/wday/cxs/nvidia/NVIDIAExternalCareerSite/jobs"
}
}Request schema
No body schema
Response schema
#/definitions/jobs.boardResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | jobs.BoardResponse | No | ||||
| data.company | string | No | Company or board name the postings belong to. | |||
| data.count | integer | No | Number of jobs returned in this response. | |||
| data.jobs | array | No | Job postings on the board, one item per posting. | |||
| data.jobs[].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.jobs[].apply_url | string | No | Link to the application page for the job. | |||
| data.jobs[].benefits_mentioned | array | No | Benefits, Clearance, and Education contain canonical requirements and offerings mentioned in the job title or description. | |||
| data.jobs[].company | string | No | Name of the hiring company. | |||
| data.jobs[].company_logo_url | string | No | URL of the company's logo. | |||
| data.jobs[].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.jobs[].compensation_currency | string | No | Currency code of the pay range, for example `USD`. | |||
| data.jobs[].compensation_max | number | No | Upper end of the pay range stated in the posting. | |||
| data.jobs[].compensation_min | number | No | Lower end of the pay range stated in the posting. | |||
| data.jobs[].compensation_period | string | No | Pay period the posting states: `hourly`, `daily`, `weekly`, `monthly` or `yearly`. Omitted when the posting names none. | |||
| data.jobs[].department | string | No | Department the job belongs to. | |||
| data.jobs[].description_html | string | No | Job description as HTML. | |||
| data.jobs[].description_text | string | No | Job description as plain text. | |||
| data.jobs[].education_level_required | array | No | Education levels mentioned in the job title or description. | |||
| data.jobs[].employment_type | string | No | Employment type the provider lists, such as full-time or contract. | |||
| data.jobs[].id | string | No | Posting id within the provider. Use it with the provider's job endpoint. | |||
| data.jobs[].location | string | No | Primary job location as the provider shows it. | |||
| data.jobs[].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.jobs[].location_country | string | No | Country of the primary location. | |||
| data.jobs[].location_state | string | No | State or region of the primary location. | |||
| data.jobs[].locations | array | No | All locations listed for the job. | |||
| data.jobs[].posted_age_text | string | No | Workday relative age ("Posted Today") | |||
| data.jobs[].posted_at | string | No | RFC3339 / date when the provider gives one | |||
| data.jobs[].provider | string | No | Applicant tracking system the posting comes from, for example `greenhouse` or `lever`. | |||
| data.jobs[].remote | boolean | No | True when the posting is marked as remote. | |||
| data.jobs[].req_id | string | No | Requisition id the company uses for the job. | |||
| data.jobs[].security_clearance_required | array | No | Security clearances mentioned in the job title or description. | |||
| data.jobs[].skills_mentioned | array | No | Skills lists canonical ESCO skill labels mentioned in the job title or description. | |||
| data.jobs[].team | string | No | Team the job belongs to. | |||
| data.jobs[].title | string | No | Job title as the company posted it. | |||
| data.jobs[].url | string | No | Link to the job posting page. | |||
| data.jobs[].workplace_type | string | No | Workplace arrangement the provider lists, such as remote, hybrid or on-site. | |||
| data.provider | string | No | Applicant tracking system the board was read from, for example `greenhouse` or `lever`. | |||
| data.source_url | string | No | URL the data was read from. | |||
| data.total | integer | No | Total number of open postings on the board, when the provider reports it. | |||
| msg | string | No | OK |
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/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/board?tenant=nvidia&datacenter=wd5&site=NVIDIAExternalCareerSite&limit=10" \
-H "x-api-key: $CRAWLORA_API_KEY"