Board checked
gitlab
Open jobs
248
Slim response
174,733 bytes
Department response
188,640 bytes

Public endpoints

RequestUseMeasured size
/jobsFast list; no department field174,733 bytes
/jobs?content=trueFull description HTML, departments and offices3.89 MB
/departmentsDepartments with nested slim jobs188,640 bytes
shell
curl -i https://boards-api.greenhouse.io/v1/boards/gitlab/jobs
curl -i https://boards-api.greenhouse.io/v1/boards/gitlab/departments

Trimmed live response

json
{
  "id": 8638232002,
  "title": "AI Transformation Owner, CRO",
  "location": {
    "name": "Remote, United States"
  },
  "absolute_url": "https://job-boards.greenhouse.io/gitlab/jobs/8638232002",
  "first_published": "2026-07-22T13:38:40-04:00"
}

Fields and department join

FieldShapeImplementation note
idnumberStable join and de-duplication key
titlestringTrim whitespace before rendering
location.namestringFree text; may contain several places
absolute_urlHTTPS URLPublic job or custom board URL
first_publishedISO date or nullPreferred newest-first value
meta.totalnumberPublished job count
departments[].parent_idnumber or nullConnects nested departments

The slim job keys observed were absolute_url, data_compliance, internal_job_id, location, metadata, id, updated_at, requisition_id, title, company_name, first_published, language, application_deadline. No department key is present. Fetch /departments and map each nested job id to its department name.

Authentication and CORS

No authentication is required. The GET response sent Access-Control-Allow-Origin: *, Allow-Methods: GET and Max-Age: 7200. OPTIONS returned an HTML 404, so keep browser requests simple; a normal GET succeeds without preflight.

Errors and performance choice

An unknown token returned HTTP 404 JSON: {"status":404,"error":"Job not found"}. For a filterable careers index, combining slim jobs with departments transfers roughly 363 KB on this board instead of 3.89 MB of descriptions.

Use it on a site

Fetch from Webflow, Framer or a client-rendered Next.js component, then create DOM nodes with textContent and allow only trusted HTTPS job URLs. For a complete no-iframe implementation, follow the Greenhouse careers-page tutorial or inspect the live Greenhouse integration.

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