Silver data cables connecting to a server rack, one glowing amber mid-insertion, with a dashboard laptop on a concrete desk nearby.

How do you connect a vacancy aggregation solution to your own intranet or ATS?

To connect a vacancy aggregation solution to your own intranet or applicant tracking system, you typically use an API or structured data feed that pushes job listings from the aggregator into your target platform on a scheduled or real-time basis. The exact method depends on what output formats your aggregator supports and what integration capabilities your intranet or ATS offers. The sections below walk through each key question you need to answer before building that connection. If you want to explore what this looks like in practice, visit Openindex for an overview of our data and crawling capabilities.

What data formats do vacancy aggregators typically output?

Vacancy aggregators most commonly output data in JSON, XML, or CSV formats, with JSON via REST API being the most widely adopted in 2026. Some aggregators also support RSS or Atom feeds for simpler, read-only consumption, while others offer webhook-based push delivery for near-real-time updates.

The format you receive matters because it determines how much transformation work sits between the aggregator and your target system. JSON is the most developer-friendly and maps cleanly to modern ATS APIs. XML is still common in older enterprise environments and government platforms. CSV exports are typically reserved for batch uploads rather than live integrations.

Beyond the file format itself, pay attention to the data schema. Some aggregators follow established standards such as Schema.org JobPosting or HR-XML, which makes mapping fields to your ATS straightforward. Others use proprietary field names that require a custom mapping layer. Always request a sample payload from your aggregator before committing to an integration approach.

How does an API-based vacancy integration actually work?

An API-based vacancy integration works by having your system send authenticated HTTP requests to the aggregator’s API endpoint, retrieve a structured list of job listings, and then write those listings into your intranet or ATS through a second API call. This process runs on a schedule or is triggered by a webhook event whenever new vacancies are published.

The typical flow looks like this:

  1. Your integration layer authenticates with the job aggregator API using an API key or OAuth token.
  2. It requests a filtered set of vacancies, often scoped by category, location, or publication date.
  3. The response is parsed and each vacancy is mapped to the field structure your intranet or ATS expects.
  4. The mapped records are sent to your target system via its own API or database connector.
  5. A reconciliation step checks for updated or expired listings and removes or archives them accordingly.

The integration layer in the middle, sometimes called middleware or an ETL component, is where most of the complexity lives. It handles authentication, field mapping, error logging, and retry logic. For smaller teams, a low-code tool like Zapier or Make can handle this. For high-volume or complex transformations, a custom-built service or a dedicated data pipeline is more reliable.

What’s the difference between connecting to an intranet versus an ATS?

Connecting a vacancy feed to an intranet is primarily a display and search problem: you want employees to browse and search internal or external job listings. Connecting to an ATS is a transactional problem: you need vacancy data to trigger workflows, manage applications, and track candidates through a hiring pipeline. These two goals require different integration depths.

An intranet integration is typically read-only. The aggregated vacancies are indexed and made searchable within the intranet environment, but the intranet does not write back to the aggregator. The main technical requirements are a reliable data feed, a search index that stays current, and a clean display layer.

An ATS integration is bidirectional in many cases. The aggregator feeds vacancy data in, but the ATS also needs to publish job statuses back, close filled positions, and sometimes syndicate listings outward to job boards. This creates more dependencies and means changes on either side can break the integration if the connection is not built with that two-way flow in mind.

Which ATS platforms support vacancy feed integrations?

Most enterprise-grade ATS platforms support vacancy feed integrations through native APIs, pre-built connectors, or partner marketplaces. Platforms such as Workday, SAP SuccessFactors, Greenhouse, Lever, SmartRecruiters, and Bullhorn all offer documented APIs that allow external vacancy data to be pushed or pulled into their systems.

The level of integration support varies significantly between platforms. Greenhouse and Lever, for example, have well-documented REST APIs with clear endpoints for creating and updating job listings programmatically. Workday and SAP SuccessFactors are more complex and often require middleware or a certified integration partner to handle the connection reliably.

Smaller or sector-specific ATS tools may offer CSV import as the primary integration method rather than a live API. In those cases, an automated export-and-import workflow can still achieve near-real-time synchronization if the import schedule is frequent enough. Always check whether your ATS supports upsert operations, meaning it can update existing records rather than creating duplicates on each import cycle.

What causes mismatches when syncing vacancy data between systems?

The most common cause of mismatches when syncing vacancy data is field mapping inconsistency: the aggregator uses different field names, value formats, or taxonomies than the target system expects. This leads to missing data, incorrect categorization, or records that fail validation on import.

Other frequent causes include:

  • Encoding differences: Special characters in job titles or descriptions can corrupt records if character encoding is not handled consistently across systems.
  • Duplicate records: If the integration does not use a stable unique identifier for each vacancy, the same listing can be created multiple times after updates.
  • Timing gaps: When a vacancy is closed in the source system but the sync has not yet run, candidates may still see and apply for a filled role.
  • Schema changes: If the aggregator updates its API schema without notice, previously working field mappings break silently.
  • Mandatory field mismatches: The ATS may require fields that the aggregator does not always populate, such as a salary range or contract type, causing records to fail on creation.

Building robust error logging into your integration layer is the most practical way to catch these issues early. A daily reconciliation report that flags records that failed to sync, or that exist in one system but not the other, saves significant manual effort over time.

How do you keep vacancy data compliant with GDPR during integration?

Keeping vacancy data compliant with GDPR during integration requires limiting the personal data you transfer, ensuring a lawful basis exists for any processing, and securing data in transit and at rest. Vacancy listings themselves typically contain no personal data, but the moment candidate application data enters the flow, GDPR obligations apply in full.

For the vacancy feed itself, compliance is relatively straightforward: job titles, descriptions, locations, and company names are not personal data under GDPR. The risk increases when the integration also handles applicant responses, contact details, or CVs.

Key compliance steps for any vacancy integration that touches personal data include:

  • Ensure all data transfers between systems are encrypted in transit using TLS and encrypted at rest where sensitive fields are stored.
  • Define and document the lawful basis for processing candidate data, typically contractual necessity or legitimate interest, before the integration goes live.
  • Apply data minimization: only transfer the fields that are genuinely needed in the target system.
  • Set retention policies so that candidate data is automatically deleted or anonymized after the defined retention period.
  • If data crosses EU borders, verify that the receiving system or service provider meets GDPR transfer requirements, for example through Standard Contractual Clauses.

Working with a data provider that understands these obligations reduces compliance risk considerably, particularly when the aggregation layer involves automated crawling of third-party job sources.

How Openindex helps with vacancy aggregation and ATS integration

We build the data infrastructure that makes vacancy aggregation reliable, structured, and ready to connect to whatever system you use. Whether you need a clean job feed delivered to your intranet search layer or a fully mapped data pipeline feeding directly into your applicant tracking system, we handle the crawling, extraction, normalization, and delivery so your team does not have to.

Here is what working with us on a vacancy aggregation integration looks like:

  • Custom crawling and data collection: We crawl the vacancy sources you specify, whether public job boards, sector-specific platforms, or partner sites, and extract structured data on your schedule.
  • Normalized output formats: We deliver vacancy data in the format your system expects, JSON, XML, or a direct API feed, with field mapping aligned to your ATS or intranet schema.
  • Crawling as a Service: You define what data you need and we manage the entire collection process, delivering only the clean, deduplicated records your integration requires.
  • GDPR-aware data handling: Our processes are built with data minimization and legal compliance in mind, so the feeds we deliver are ready for use in regulated environments.
  • Scalable infrastructure: Whether you need hundreds or millions of vacancy records processed, our infrastructure scales without performance degradation.

If you are building or improving a vacancy aggregation setup and want to discuss what the right integration architecture looks like for your situation, get in touch with us and we will help you map it out.

Veelgestelde vragen

Do I need a developer to set up a vacancy feed integration?

Not always. For straightforward use cases, low-code tools like Zapier or Make can handle the connection between an aggregator and your target system without custom code. However, if your ATS requires complex field mapping, bidirectional sync, or high-volume data processing, a developer or integration specialist will save you significant time and reduce the risk of data issues down the line.

How often should vacancy data be synced between systems?

It depends on how quickly your vacancies change and how critical freshness is to your users. For most intranet use cases, syncing every few hours is sufficient. For ATS integrations where candidates might apply to already-filled roles, a more frequent schedule — or a webhook-based real-time trigger — is worth the added setup effort.

What's the best way to avoid duplicate vacancy records during integration?

Always use a stable, unique identifier from the source system as the primary key in your integration logic. This allows your middleware to perform upsert operations — updating existing records rather than creating new ones on each sync cycle. Without this, duplicates will accumulate quickly, especially when vacancy listings are updated rather than replaced.

Can a vacancy aggregator feed multiple systems at the same time?

Yes, and this is a common setup for larger organizations that run both an intranet and an ATS in parallel. The aggregator delivers a single normalized data feed, and your integration layer routes the relevant fields to each target system independently. Just ensure each system’s field mapping and update logic is maintained separately, as requirements often differ between platforms.

Gerelateerde artikelen

NEED HELP WITH YOUR DATA OR SEARCH?

Let's find the right solution for you.

From data extraction and site search to custom development, our team can help you turn your ideas into practical solutions.

Let's talk about your project