Group and internal careers feeds in the Public Careers API
Fetch vacancies for a group of companies in one list, and read the internal vacancies that only your own staff should see.
Fetch vacancies for a group of companies in one list, and read the internal vacancies that only your own staff should see.
This guide is for web developers building a custom careers page for a group of companies, or an intranet vacancy board. You need your careers slug first. For the vacancy fields, filters and parameters these calls share with the standard list, read Listing vacancies with the Public Careers API. To set up the internal page itself, see Setting up an internal careers page.
Group careers feed
If your organisation runs several companies under one group, the group feed returns vacancies from all of them in one list, each marked with the company that owns it. The slug is always the parent company's.
GET /api/public/careers/{slug}/group/jobsGET /api/public/careers/{slug}/group/departmentsGET /api/public/careers/{slug}/group/facets
The jobs call takes the same parameters as the standard list. The response shape is different. data is a plain list, and the paging details are in a meta object beside it.
{
"success": true,
"data": [ ],
"meta": { "total": 42, "page": 1, "limit": 20, "totalPages": 3 }
}
A paging helper written for the standard list needs its own branch for this one.
Each vacancy has the usual list fields plus owningCompany, with its slug, name, logoUrl and brandColor. Link each vacancy to the owning company's page, /careers/{owningCompany.slug}/jobs/{id}, because the parent's slug will not find it. Group results do not include locationImageUrl. If the group feed is not set up, all three calls return 404 NOT_FOUND.
Internal careers page
The internal careers page shows vacancies to your own staff, including roles that are never advertised outside. Anyone who holds its private token can see it. The token is created under Internal Careers Page in the careers settings.
GET /api/public/careers/{slug}/internal/{token}GET /api/public/careers/{slug}/internal/{token}/departmentsGET /api/public/careers/{slug}/internal/{token}/facetsGET /api/public/careers/{slug}/internal/{token}/jobs
These match their external versions but follow the internal page's own hide switches.
For an internal only vacancy, send the token as internalToken on the job detail, application form and download calls, and in the body of the upload renewal, save draft and apply calls. Keep the token on your server, put the internal board behind your intranet login, and never place the token in browser code on a public page. A wrong or switched off token returns the same 404 NOT_FOUND as an unknown company.
A vacancy that is only on the internal careers page never appears in the public list, and it never triggers a public job alert. See Job alerts for who receives alerts.