LinkedIn job feed integration
Your open roles published as an XML feed LinkedIn can ingest, so a job posted once in SignHR reaches LinkedIn without being retyped.
SignHR exposes your open roles as an XML feed at a public URL. LinkedIn's job ingestion reads that feed on its own schedule, so a role you open in SignHR appears on LinkedIn without anyone retyping it, and a role you close stops being advertised. The same public careers API also lets you embed live listings on your own website.
How it works
- 1
Publish a role in SignHR
Roles are created and managed in recruitment as normal — title, location, description, employment type. Nothing extra is needed to make a role feed-eligible beyond publishing it.
- 2
SignHR generates the feed
Your workspace exposes an XML feed of currently open roles at a stable public URL. It reflects what is open right now rather than being a snapshot someone has to regenerate.
- 3
LinkedIn ingests on its schedule
You give LinkedIn the feed URL once. From then on LinkedIn re-reads it periodically and updates what it advertises — new roles appear, closed roles drop off.
- 4
The same data powers your careers page
Alongside the feed, a versioned public careers API serves the same roles as JSON, so your own site can render live listings against a response shape that will not change underneath it.
Where it stops
Every integration has edges. These are ours, stated here rather than discovered during implementation.
- One-way. Roles flow out to LinkedIn; applicants submitted on LinkedIn do not flow back into SignHR automatically.
- LinkedIn controls the ingestion schedule, so a newly opened role is not instant — it appears when LinkedIn next reads the feed.
- Feed ingestion is subject to LinkedIn's own eligibility and account requirements, which are theirs to change and sit outside SignHR.
- This is a job feed, not a LinkedIn API integration. There is no posting to a company page, no InMail, and no candidate sourcing.
Questions
No. The feed pushes roles out; it does not pull applicants in. Candidates who apply through LinkedIn are handled in LinkedIn. If you want applications landing in SignHR, point candidates at your careers page, which is served by the public careers API and does write applications into recruitment.
That is LinkedIn's decision, not ours — it re-reads the feed on its own schedule. The feed itself is current the moment you publish the role, so any delay is on the ingestion side.
It is a standard XML job feed at a public URL, so any board that ingests feeds can in principle read it. We name LinkedIn because that is what it was built and tested against; another board is worth trying but is not something we have verified.
Yes, and that is what the versioned public careers API is for. It serves the same roles as JSON with a stable response shape, so a custom careers page will not break when we ship changes elsewhere.
This integration feeds Recruitment & Hiring.
Other integrations
Technical detail last checked against the product on 2026-08-07.
