/workable/jobs/finder

POST /api/workable/jobs/finder

Price: 10 credits

Search jobs across all Workable company boards (cross-company job finder)

How to use it

Search jobs across every company's Workable board at once, without knowing a specific board handle. Filter by keyword, location (city or country), workplace (on-site/hybrid/remote), employment type, experience level, and recency. Returns each job with title, hiring company (name, website, logo, description), description, requirements and benefits (HTML), employment type, workplace, location(s), 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)
• count integer required — Number of jobs to return (min: 1)
• query string — Job title or keyword (default: "")
• location string — City or country to filter by (default: ""; examples: "London", "United Kingdom")
• workplace array — Filter by workplace type(s) (default: []; one of: "on_site", "hybrid", "remote"; examples: ["remote"])
• employment_type array — Filter by employment type(s) (default: []; one of: "Full-time", "Part-time", "Contract", "Temporary"; examples: ["Full-time"])
• experience array — Filter by experience level(s) (default: []; one of: "internship", "entry_level", "associate", "mid_senior_level", "director", "executive"; examples: ["mid_senior_level"])
• day_range integer nullable — Only jobs posted within this many past days (examples: 7, 30; min: 1)

Response

• @type string (default: "WorkableFinderJob")
• id string required
• company object nullable
  • @type string (default: "WorkableFinderCompany")
  • id string nullable
  • website string nullable
  • image string nullable
  • description string nullable
  • web_url string nullable
• description string nullable
• requirements string nullable
• benefits string nullable
• employment_type string nullable
• workplace string nullable
• department string nullable
• location object nullable
  • @type string (default: "WorkableFinderLocation")
  • city string nullable
  • region string nullable
  • country string nullable
• locations array (default: [])
• language string nullable
• state string nullable
• is_featured boolean (default: false)
• published_at string nullable
• updated_at 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 — The entity was not found, or a precondition failed 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.