Docs menu

Jobs API endpoint

Workable Single Posting API

Returns a single Workable posting with its full HTML/text description. The id is the posting shortcode from a listing.

GETapiKey1 credit/requestJobsjobs.jobResponseDoc/jobs/workable/posting

Endpoint facts

Method: GET
API path: /jobs/workable/posting
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: Jobs
Response schema: #/definitions/jobs.jobResponseDoc

Job Boards API Try Workable Single Posting API in Playground Jobs API documentation

How this endpoint behaves

Query parameters:

company (required) — the Workable account slug (e.g. zego).
id (required) — the posting shortcode from a listing (e.g. DBB0F9D146).

Returns a single Job: provider, id, title, company, department, location, locations[], remote, workplace_type, employment_type, url, apply_url, req_id, posted_at, description_html, description_text, compensation, compensation_min, compensation_max, compensation_currency, compensation_period. An unknown shortcode returns 404. Workable has no structured compensation field; the compensation_* fields are populated only when the description states an explicit pay figure near a salary/compensation keyword (many postings state no figure at all, in which case they stay empty).

Sampled response

Request, 14 Oct 2026: GET /jobs/workable/posting?company=huggingface&id=DB4D7C0EC8
Fields returned with a value: 16

Field	In the sample	Value in the sample
provider	Has a value	“workable”
id	Has a value
title	Has a value	“Senior Open-Source Python Engineer, ML Developer Tools - EM…”
company	Has a value	“Huggingface”
department	Has a value	“Product”
location	Has a value	“FR”
locations	Has a value	1 entry
location_country	Has a value	“FR”
remote	Has a value	true
workplace_type	Has a value	“remote”
employment_type	Has a value	“Full-time”
url	Has a value	apply.workable.com
apply_url	Has a value	apply.workable.com
posted_at	Has a value	2026-09-21
description_html	Has a value	7,008 characters
description_text	Has a value	5,704 characters

Request parameters

Parameter	Type	Required	Description	Example
company	string	Yes	Workable account slug	zego
id	string	Yes	Workable posting shortcode	DBB0F9D146
x-api-key (header)	string	Yes	API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/jobs/workable/posting?company=zego&id=DBB0F9D146" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "provider": "workable",
    "id": "DBB0F9D146",
    "title": "Customer Motor Claims Handler",
    "company": "zego",
    "department": "Claims and Fraud",
    "location": "Halifax, England, United Kingdom",
    "remote": false,
    "workplace_type": "hybrid",
    "employment_type": "Full-time",
    "url": "https://apply.workable.com/zego/j/DBB0F9D146/",
    "apply_url": "https://apply.workable.com/zego/j/DBB0F9D146/apply/",
    "posted_at": "2026-07-15T00:00:00Z",
    "description_html": "<p>…</p>",
    "description_text": "…"
  }
}

Request schema

No body schema

Response schema

#/definitions/jobs.jobResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	jobs.Job	No
data.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.apply_url	string	No		Link to the application page for the job.
data.benefits_mentioned	array	No		Benefits, Clearance, and Education contain canonical requirements and offerings mentioned in the job title or description.
data.company	string	No		Name of the hiring company.
data.company_logo_url	string	No		URL of the company's logo.
data.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.compensation_currency	string	No		Currency code of the pay range, for example `USD`.
data.compensation_max	number	No		Upper end of the pay range stated in the posting.
data.compensation_min	number	No		Lower end of the pay range stated in the posting.
data.compensation_period	string	No		Pay period the posting states: `hourly`, `daily`, `weekly`, `monthly` or `yearly`. Omitted when the posting names none.
data.department	string	No		Department the job belongs to.
data.description_html	string	No		Job description as HTML.
data.description_text	string	No		Job description as plain text.
data.education_level_required	array	No		Education levels mentioned in the job title or description.
data.employment_type	string	No		Employment type the provider lists, such as full-time or contract.
data.id	string	No		Posting id within the provider. Use it with the provider's job endpoint.
data.location	string	No		Primary job location as the provider shows it.
data.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.location_country	string	No		Country of the primary location.
data.location_state	string	No		State or region of the primary location.
data.locations	array	No		All locations listed for the job.
data.posted_age_text	string	No		Workday relative age ("Posted Today")
data.posted_at	string	No		RFC3339 / date when the provider gives one
data.provider	string	No		Applicant tracking system the posting comes from, for example `greenhouse` or `lever`.
data.remote	boolean	No		True when the posting is marked as remote.
data.req_id	string	No		Requisition id the company uses for the job.
data.security_clearance_required	array	No		Security clearances mentioned in the job title or description.
data.skills_mentioned	array	No		Skills lists canonical ESCO skill labels mentioned in the job title or description.
data.team	string	No		Team the job belongs to.
data.title	string	No		Job title as the company posted it.
data.url	string	No		Link to the job posting page.
data.workplace_type	string	No		Workplace arrangement the provider lists, such as remote, hybrid or on-site.
msg	string	No	OK

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
404	Not Found	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/jobs/workable/posting?company=zego&id=DBB0F9D146" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More Jobs endpoint docs Job Boards API Ashby Board Listing API documentation Cross-Provider Company Search API documentation Eightfold Board Listing API documentation Eightfold Single Position API documentation Gem Board Listing API documentation Greenhouse Board Listing API documentation

Open in Playground Back to group

Docs menu

Jobs API endpoint

Workable Single Posting API

Returns a single Workable posting with its full HTML/text description. The id is the posting shortcode from a listing.

GETapiKey1 credit/requestJobsjobs.jobResponseDoc/jobs/workable/posting

Endpoint facts

Method: GET
API path: /jobs/workable/posting
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: Jobs
Response schema: #/definitions/jobs.jobResponseDoc

Job Boards API Try Workable Single Posting API in Playground Jobs API documentation

How this endpoint behaves

Query parameters:

company (required) — the Workable account slug (e.g. zego).
id (required) — the posting shortcode from a listing (e.g. DBB0F9D146).

Sampled response

Request, 14 Oct 2026: GET /jobs/workable/posting?company=huggingface&id=DB4D7C0EC8
Fields returned with a value: 16

Field	In the sample	Value in the sample
provider	Has a value	“workable”
id	Has a value
title	Has a value	“Senior Open-Source Python Engineer, ML Developer Tools - EM…”
company	Has a value	“Huggingface”
department	Has a value	“Product”
location	Has a value	“FR”
locations	Has a value	1 entry
location_country	Has a value	“FR”
remote	Has a value	true
workplace_type	Has a value	“remote”
employment_type	Has a value	“Full-time”
url	Has a value	apply.workable.com
apply_url	Has a value	apply.workable.com
posted_at	Has a value	2026-09-21
description_html	Has a value	7,008 characters
description_text	Has a value	5,704 characters

Request parameters

Parameter	Type	Required	Description	Example
company	string	Yes	Workable account slug	zego
id	string	Yes	Workable posting shortcode	DBB0F9D146
x-api-key (header)	string	Yes	API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/jobs/workable/posting?company=zego&id=DBB0F9D146" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "provider": "workable",
    "id": "DBB0F9D146",
    "title": "Customer Motor Claims Handler",
    "company": "zego",
    "department": "Claims and Fraud",
    "location": "Halifax, England, United Kingdom",
    "remote": false,
    "workplace_type": "hybrid",
    "employment_type": "Full-time",
    "url": "https://apply.workable.com/zego/j/DBB0F9D146/",
    "apply_url": "https://apply.workable.com/zego/j/DBB0F9D146/apply/",
    "posted_at": "2026-07-15T00:00:00Z",
    "description_html": "<p>…</p>",
    "description_text": "…"
  }
}

Request schema

No body schema

Response schema

#/definitions/jobs.jobResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	jobs.Job	No
data.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.apply_url	string	No		Link to the application page for the job.
data.benefits_mentioned	array	No		Benefits, Clearance, and Education contain canonical requirements and offerings mentioned in the job title or description.
data.company	string	No		Name of the hiring company.
data.company_logo_url	string	No		URL of the company's logo.
data.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.compensation_currency	string	No		Currency code of the pay range, for example `USD`.
data.compensation_max	number	No		Upper end of the pay range stated in the posting.
data.compensation_min	number	No		Lower end of the pay range stated in the posting.
data.compensation_period	string	No		Pay period the posting states: `hourly`, `daily`, `weekly`, `monthly` or `yearly`. Omitted when the posting names none.
data.department	string	No		Department the job belongs to.
data.description_html	string	No		Job description as HTML.
data.description_text	string	No		Job description as plain text.
data.education_level_required	array	No		Education levels mentioned in the job title or description.
data.employment_type	string	No		Employment type the provider lists, such as full-time or contract.
data.id	string	No		Posting id within the provider. Use it with the provider's job endpoint.
data.location	string	No		Primary job location as the provider shows it.
data.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.location_country	string	No		Country of the primary location.
data.location_state	string	No		State or region of the primary location.
data.locations	array	No		All locations listed for the job.
data.posted_age_text	string	No		Workday relative age ("Posted Today")
data.posted_at	string	No		RFC3339 / date when the provider gives one
data.provider	string	No		Applicant tracking system the posting comes from, for example `greenhouse` or `lever`.
data.remote	boolean	No		True when the posting is marked as remote.
data.req_id	string	No		Requisition id the company uses for the job.
data.security_clearance_required	array	No		Security clearances mentioned in the job title or description.
data.skills_mentioned	array	No		Skills lists canonical ESCO skill labels mentioned in the job title or description.
data.team	string	No		Team the job belongs to.
data.title	string	No		Job title as the company posted it.
data.url	string	No		Link to the job posting page.
data.workplace_type	string	No		Workplace arrangement the provider lists, such as remote, hybrid or on-site.
msg	string	No	OK

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
404	Not Found	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/jobs/workable/posting?company=zego&id=DBB0F9D146" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

Open in Playground Back to group

Workable Single Posting API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

Workable Single Posting API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related