Invenias job postings,
on your own website.
Redsun reads the job postings you publish in Invenias, turns the live ones into job pages on your website, and adds each applicant to the assignment behind the posting with their CV and a note of how they applied.
A third-party application and a dedicated API user.
Invenias signs integrations in with its own OAuth login. A System Administrator creates a third-party application in the Invenias Swagger page, which issues a client ID and secret, and sets up an API user with an Invenias password. Redsun takes those and your Invenias subdomain, and signs in afresh on every run, so no token is stored.
- Only postings with the status Published or Promoted appear, which makes publishing in Invenias your switch for the website
- Invenias publishes no webhooks, so changes reach your site on the hourly sync or when you press Sync now
- Invenias applications expire after one, two or five years, and when yours lapses the connection test tells you how to renew it
What the Invenias adapter does.
Each item below maps to an endpoint in the Invenias API that the adapter calls.
Job postings as job pages
Each live posting comes across with its advert, location, employment type and closing date, with salary on postings where you have made packages and rates visible. Promoted postings are marked as featured.
Applicants on the assignment
A website applicant is added as a candidate on the assignment behind the posting, with a progress note naming the advert, so they land in that search's pipeline. A note on their record keeps the phone number, LinkedIn and cover letter they gave.
CV upload
The CV uploaded on your site is attached to the person's Invenias record and set as their default CV.
Candidates and client contacts
People come across split on their own Candidate and Client roles. Someone who applies with an email address Invenias already holds is matched to that person, and their record is left as your researchers keep it.
Client companies, placements and users
Client companies, confirmed placements and your consultants' user records come across too, feeding consultant profiles and placement counts on the site.
Sensitive fields left out
Date of birth, gender, nationality, marital status, passport number and internal comments are never requested from Invenias.
Invenias Integration FAQs
Common questions about connecting Invenias to a Redsun-powered recruitment website.
- Which Invenias roles appear on my website? +
- Job postings with the status Published or Promoted. Drafts stay off the site, and a posting you unpublish is closed on the next sync. Assignments are never read for the job board, which keeps a confidential search off your site until you advertise it.
- Where do applicants end up in Invenias? +
- On the assignment the posting belongs to, as a candidate with a progress note naming the advert. If their email address already belongs to someone in Invenias, Redsun attaches that existing person. A posting with no assignment behind it cannot take applications, and Redsun reports the failure.
- What happens when the Invenias application expires? +
- Third-party applications in Invenias last one, two or five years. When one lapses, Invenias refuses the login and the connection test in Redsun says so. A System Administrator renews it from the Invenias Swagger page, which issues a new client secret, and pastes that secret into Redsun.
Keep reading
See the Invenias integration in action.
Book a demo and we'll show you a role moving from Invenias onto your site, and an application landing back on the record.