/workable/jobs

POST /api/workable/jobs

Price: 1 credit

Get a Workable job posting by company board handle and job shortcode

How to use it

Get the full details of a single job posting on a company's Workable board, identified by the board handle (Workable subdomain) and the job shortcode (or a full job URL). Returns title, full description, requirements and benefits (HTML), employment type, workplace (on-site/hybrid/remote), department, location(s), language, state, published date, and the job URL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• account string required — Company board handle (the Workable subdomain, e.g. 'careers') (examples: "careers", "netguru"; minLength: 1)
• shortcode string required — Job shortcode, or a full job URL (examples: "9FA20A268C", "https://apply.workable.com/careers/j/9FA20A268C/"; minLength: 1)

Response

• @type string (default: "WorkableJob")
• id integer required
• shortcode string required
• description string nullable
• requirements string nullable
• benefits string nullable
• code string nullable
• employment_type string nullable
• is_remote boolean (default: false)
• workplace string nullable
• department array (default: [])
• language string nullable
• state string nullable
• approval_status string nullable
• is_internal boolean (default: false)
• published_at string nullable
• account_uid string nullable
• location object nullable
  • @type string (default: "WorkableJobLocation")
  • country string nullable
  • country_code string nullable
  • region string nullable
  • city string nullable
• locations array (default: [])
  • @type string (default: "WorkableJobLocation")
  • country string nullable
  • country_code string nullable
  • region string nullable
  • city string nullable
• web_url string (default: "")

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 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.