Skip to main content
POST
/
api
/
workday
/
jobs
/
search
/workday/jobs/search
curl --request POST \
  --url https://api.anysite.io/api/workday/jobs/search \
  --header 'Content-Type: application/json' \
  --header 'access-token: <api-key>' \
  --data '
{
  "career_site_url": "<string>",
  "count": 2,
  "timeout": 300,
  "search_text": "engineer",
  "applied_facets": {
    "timeType": [
      "5509c0b5959810ac0029943377d47364"
    ]
  }
}
'
[
  {
    "@type": "@workday_job_listing",
    "title": "<string>",
    "req_id": "<string>",
    "location": "<string>",
    "posted_on": "<string>",
    "time_type": "<string>",
    "external_path": "<string>",
    "url": "<string>"
  }
]

Authorizations

​
access-token
string
header
required

API token from the dashboard

Headers

​
access-token
string
required

Body

application/json
​
career_site_url
string
required

Career-board URL of a Workday-powered company, e.g. https://{tenant}.{dc}.myworkdayjobs.com/{site}

Minimum string length: 1
Example:

"https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"

​
count
integer
required

Max number of job postings to return

Required range: x >= 1
​
timeout
integer
default:300

Max scrapping execution timeout (in seconds)

Required range: 20 <= x <= 1500
​
search_text
string | null

Full-text keyword query

Example:

"engineer"

​
applied_facets
Applied Facets · object

Facet filters as {facetParameter: [valueId, ...]}. Common facetParameters include jobFamilyGroup (job category), timeType (full/part time), workerSubType (job type), locationCountry, locationHierarchy1 and locations. Value ids are the ids exposed by the board's own facet list.

Example:
{
  "timeType": ["5509c0b5959810ac0029943377d47364"]
}

Response

Successful Response

​
@type
string
default:@workday_job_listing
​
title
string | null
​
req_id
string | null
​
location
string | null
​
posted_on
string | null
​
time_type
string | null
​
external_path
string | null
​
url
string | null