/workday/jobs

POST /api/workday/jobs

Price: 1 credit

Get a single Workday job posting by its full career-board URL. Returns the job title, full HTML description, requisition id, posting id, primary and additional locations, requisition location with country, remote type, time type, posting date, start date, posted and apply availability flags, hiring organization and the public job URL.

How to use it

Get full details of one job posting hosted on a company's Workday career board (*.myworkdayjobs.com). Pass the full job posting URL. Returns one item with title, description (HTML), req_id, posting_id, location, additional_locations, requisition_location, country, remote_type, time_type, posted_on, start_date, is_posted, can_apply, hiring_organization and url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• url string required — Full job posting URL from a Workday career board, e.g. https://{tenant}.{dc}.myworkdayjobs.com/{site}/job/{location}/{slug}_{reqId} (examples: "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Senior-Platform-and-EngOps-Engineer---Cluster-Operations_JR2014633"; minLength: 1)

Response

• @type string (default: "WorkdayJob")
• id string required
• req_id string nullable
• posting_id string nullable
• description string nullable
• location string nullable
• additional_locations array (default: [])
• requisition_location object nullable
  • @type string (default: "WorkdayRequisitionLocation")
  • name string nullable
  • country object nullable
    • @type string (default: "WorkdayCountry")
    • id string nullable
    • name string nullable
    • alpha2_code string nullable
• country object nullable
  • @type string (default: "WorkdayCountry")
  • id string nullable
  • name string nullable
  • alpha2_code string nullable
• remote_type string nullable
• time_type string nullable
• posted_on string nullable
• start_date string nullable
• end_date string nullable
• is_posted boolean nullable
• can_apply boolean nullable
• site string nullable
• hiring_organization object nullable
  • @type string (default: "WorkdayHiringOrganization")
  • name string nullable
  • url string nullable
• url string 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 — Job posting not found 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.