Vincere
website integration
Vincere website integration connects Vincere to your recruitment website so that jobs posted in Vincere appear on your own site, and applications and registrations made there flow back into Vincere as candidate records with their CVs. You can use Vincere's own job portal, a recruitment website platform with a Vincere connector, or a custom integration built on Vincere's API.
Your Vincere jobs, on your own site
- 01
Live jobs on your own site
Jobs you publish in Vincere appear on your website automatically, with keyword, location, sector and salary search and filters, and a page of their own for every job.
- 02
Google for Jobs markup
Each job page carries JobPosting structured data. Google requires it on the same page as the job description candidates read, on the most detailed page possible, and not on search-results pages.
- 03
Applications straight back into Vincere
Applications and registrations create or update the candidate record, attach the CV, link the candidate to the job where Vincere supports it, and record the source so you can see which jobs and channels work.
- 04
Job alerts
Candidates can sign up for alerts by keyword, location or sector and are emailed when matching jobs go live.
- 05
Expiry and unpublishing
When a job is filled or unpublished in Vincere, it comes off your site. Google asks for expired jobs to be removed from the page, marked with a past validThrough date, or returned as 404 or 410.
How Vincere integration works technically
Based on Vincere's own published documentation, linked below. Vendors change their APIs and access rules, so we confirm the details with Vincere before every build.
- 01API access
- Vincere runs a developer portal where developers register, subscribe an app to an API plan and retrieve an API key. The endpoint reference is in Vincere's API documentation, which the portal provides on request.
- 02Authentication
- Vincere's January 2026 developer-portal guide says the key is sent in an x-api-key header, and that an administrator must create a consent record in the Vincere web application linking the key to an app, a representative user and optional scopes; without it, requests are rejected. Vincere's help centre also describes an Auth0 sign-in that returns id, access and refresh tokens, with HTTPS callback URLs.
- 03Who can get a key
- Vincere's help centre says API keys are only issued to partners with a formal agreement with Vincere, requested through Vincere Support with your tenant URL, the integration name and a callback URL. Confirm the route with Vincere before you commission a custom integration.
- 04How jobs reach a website
- Vincere's own Job Portal runs at an address on Vincere's domain by default and can be moved to your own domain. Through Marketplace connectors such as Access Volcanic, Vincere posts, updates and unposts jobs on the connected website.
- 05How applications come back
- With the Access Volcanic connector, Vincere retrieves applications and registrations (name, email, CV and cover letter) using a Vincere API key from Vincere Support and a webhook pointing at your Vincere tenant.
Four ways to connect Vincere to your website
| Option | Cost model | Design freedom | SEO control | Data flow | Lock-in |
|---|---|---|---|---|---|
| Vincere's own job portalVincere's Job Portal (and the Instant Job Board in Vincere Engage) is a hosted job listing page you customise in Vincere. It runs on a Vincere address by default; Vincere explains how to point your own domain at it. | Depends on your Vincere package | Low to medium: Vincere's templates and settings | Limited: a separate site from your main website | Managed inside Vincere | Tied to Vincere |
| Off-the-shelf pluginA plugin for your CMS, where one exists. Vincere says it only issues API keys to partners with a formal agreement, so check that any plugin is listed in Vincere's Marketplace or has its own agreement with Vincere before you rely on it. | Plugin licence plus your website build | High, within your CMS theme | Good if jobs render as pages on your domain | Depends on the plugin: check it writes applications back | Tied to the plugin and its Vincere access |
| Recruitment website platform with a connectorAccess Volcanic, for example, is in Vincere's Marketplace: Vincere posts, updates and unposts jobs on the Volcanic site and retrieves applications and registrations back into Vincere. | Monthly platform fee, often on a fixed-term contract, plus set-up | Medium: within the platform's templates and modules | Medium: on your domain, within what the platform allows | Jobs out; name, email, CV and cover letter back | High: site, jobs and integration sit with the platform |
| Custom integration in your own site (what we build)Once Vincere API access is confirmed, we connect your website to Vincere directly: job search and job pages on your domain, JobPosting markup, applications and registrations written to Vincere with CV, source and consent. | Scoped to your requirements; included in our 5-page website offer | Full | Full: every job is an indexable page on your domain | Two-way, mapped to your fields and rules | Low: you own the site and the code |
Third-party products are named only where the vendor's own documentation (linked above) describes the integration. TRG Digital is independent and not a Vincere partner.
How a Vincere integration project runs
Audit what you have
We look at how jobs reach your site today, what happens to an application, and where candidates and Google see your jobs.
Get API access
Your Vincere admin requests API access from the vendor, and nothing is built until it is confirmed. Ask Vincere Support how API access is granted for your integration. Vincere says keys go only to partners with a formal agreement, and that an administrator must create a consent record linking the key to an app and user.
Map the fields
We agree which ATS fields drive titles, filters, salary, location and the Google for Jobs markup, and how applications map back.
Build job search and job pages
Search, filters and a fast, indexable page for every job on your own domain, with JobPosting structured data.
Connect applications and registrations
Forms write to Vincere: candidate created or updated, CV attached, source recorded, consent captured.
Handle expiry
Unpublished and filled jobs leave the site and Google; old job URLs return the right status.
Test with live jobs
We publish, edit and close test jobs, submit test applications and check every record in Vincere before launch.
Launch and monitor
We watch the sync, Google Search Console job reports and application volumes after launch.
What we'll need from you
- An Vincere admin who can request or approve API access
- Your list of job fields to show (title, salary, location, sector, job type, consultant)
- How you want applications recorded: new candidate, update existing, source value
- Your privacy notice and the consent wording you use today
- A handful of live test jobs we can publish and unpublish
What goes wrong, and how to avoid it
- Iframes and embedded widgets
- Jobs shown inside an iframe live on someone else's page. Google says JobPosting data must be on the same page as the job description the candidate reads, so an embedded list usually gives you no Google for Jobs listings and no search value on your own domain.
- Jobs on an ATS subdomain
- Hosted careers pages often sit on the vendor's domain or a subdomain. Candidates still find the jobs, but the search visibility builds up on that address rather than your website.
- Duplicate candidate records
- If every application creates a new candidate, your database fills with duplicates. Match on email (and phone where you can) and update the existing record instead.
- GDPR and consent capture
- The ICO says you must give people privacy information at the time you collect their data. Link your privacy notice on every form, record what the candidate agreed to and when, and send that record to the ATS with the application.
- Expired jobs left live
- Jobs that are filled but still marked up confuse candidates and break Google's rules. Make sure unpublishing in the ATS removes the job or its markup from your site.
- Field mapping left to defaults
- Sector, location and job type values in the ATS rarely match your website's filters out of the box. Agree the mapping before build, not after launch.
A 5-page recruitment website with job pages and integrations included, worth up to £4,999, is free with any SEO package from £299 a month (12-month minimum term). Additional pages are priced on requirements.
It connects Vincere to your recruitment website so jobs posted in Vincere appear on your site and applications and registrations made there go back into Vincere with the candidate's CV.
Yes. Vincere's Job Portal, and the Instant Job Board in Vincere Engage, are hosted job pages you customise inside Vincere. They run on a Vincere address by default and can be moved to your own domain.
Vincere's developer portal lets developers register an app and retrieve a key, and an administrator in your Vincere account must create a consent record for it. Vincere's help centre says keys are only issued to partners with a formal agreement, requested through Vincere Support.
Vincere's Marketplace lists integrations; Access Volcanic is one, documented by both Vincere and Access, posting jobs to the website and pulling applications and registrations back. Check the Marketplace for others before you choose.
Only if each job has its own page carrying JobPosting structured data with Google's required properties. Google says the markup must be on the same page as the job description the candidate reads, so jobs shown inside an iframe won't count for your site.