Board checked
linear
Listed jobs
32
Response
448,777 bytes
Envelope
{ jobs, apiVersion }

The public request

Insert the slug from jobs.ashbyhq.com/{board} into the posting endpoint. No key, bearer token or cookie is needed.

shell
curl -i \
+  -A "Mozilla/5.0" \
+  https://api.ashbyhq.com/posting-api/job-board/linear

Trimmed live response

json
{
  "id": "d3bc1ced-3ce4-4086-a050-555055dbb1ff",
  "title": "Senior / Staff Fullstack Engineer",
  "department": "Product",
  "team": "Engineering",
  "employmentType": "FullTime",
  "location": "Europe",
  "workplaceType": "Remote",
  "jobUrl": "https://jobs.ashbyhq.com/linear/d3bc1ced-3ce4-4086-a050-555055dbb1ff"
}

Fields suited to a careers page

FieldShapeImplementation note
idUUID stringPosting identity
titlestringVisible role title
department / teamstringTeam is a useful fallback
locationstringPrimary display location
secondaryLocationsarrayAdditional valid locations
workplaceTypeenum stringRemote, Hybrid or OnSite
employmentTypeenum stringNormalize labels for visitors
jobUrl / applyUrlHTTPS URLsHosted detail and direct apply links

The response included id, title, department, team, employmentType, location, secondaryLocations, publishedAt, isListed, isRemote, workplaceType, address, jobUrl, applyUrl, descriptionHtml, descriptionPlain. Use isListed to exclude hidden records, publishedAt for ordering, and both location collections when a role has alternatives.

CORS and user-agent behavior

GET returned Access-Control-Allow-Origin: *. OPTIONS returned 204 and advertised GET. Browsers worked, but some script-default user agents received Cloudflare HTTP 403 error 1010; send a normal browser user agent from command-line or server-side probes.

Payload and error shape

Linear’s 32-job response measured 448,777 bytes because description HTML and plain text are included. A wrong slug returned HTTP 404 as text/plain with the body Not Found, not a JSON error object.

Client mapping

Prefer jobUrl for the hosted job page, use applyUrl only for a direct application action, and render description HTML only after a deliberate sanitization policy. RoleWall ignores descriptions for the list and maps the safer scalar fields shown in the live Ashby integration.

Live probe: November 19, 2026, origin https://rolewall.com.