Recruitment 17 April 2026 6 min read

Job Board Integration for Recruitment Software: API vs XML Feed

UK agencies post to multiple job boards simultaneously and expect applications to arrive automatically in their ATS. The reality is more complicated: not all major UK job boards offer equivalent API access, multi-posting tools exist specifically because direct API integration with each board separately is impractical, and the most common integration failures — missing applications, duplicate candidates, delayed syncs — are predictable and largely preventable with the right setup.

The UK job board landscape and API access

The main UK job boards each have different levels of technical integration capability:

  • Indeed has the most comprehensive API suite — Job Sync API (GraphQL-based), Indeed Apply integration, and Sponsored Jobs API. ATS partners using the Job Sync API see 70% Indeed Apply adoption versus 50% for XML feed-only integrations. When using Job Sync, all public jobs must be sent to Indeed immediately with updates within 15 minutes.
  • CV-Library offers a Job Search API, though it is designed for front-end JavaScript applications rather than bulk data operations.
  • Reed has a public API supporting job search, details retrieval, and job posting.
  • Totaljobs has limited direct public API documentation; it is primarily accessed through multi-posting platforms.
  • LinkedIn does not offer a public Jobs API for third-party ATS posting — integration is only available through LinkedIn's verified partner programme, which covers enterprise ATS vendors.

API integration vs XML feed: the actual difference

Both methods get jobs onto job boards. They differ in flexibility, stability, and setup requirements.

Aspect XML feed REST/GraphQL API
Setup complexity No engineering required — configure and submit Developer setup required for authentication and endpoints
Update frequency Typically every hour (batch) Near real-time (Indeed Job Sync: 15 minutes)
Stability High — XML schemas rarely change Lower — API versioning can break integrations
Data fidelity Standardised fields; less flexible More granular — can include custom fields per board
Apply flow Candidate applies on job board site Indeed Apply: candidate applies within Indeed interface

XML feeds use the Rightmove V3 BLM format as the UK standard (borrowed from property portals), which is accepted across job boards and estate agent software alike. For most agencies, XML feed posting is sufficient and more reliable than direct API integration with every board independently.

What multi-posting tools do

Broadbean, Idibu, and LogicMelon exist because maintaining direct integrations with dozens of job boards individually is impractical for most agencies. They provide a single interface from which a job is distributed to multiple boards simultaneously, with response aggregation back into the recruiter's dashboard.

Broadbean posts to 7,000+ job boards and channels. It includes internal and external CV searching, referral programme management, and social media publishing. It integrates with most major ATS platforms via API.

Idibu posts to 1,000+ job boards and social networks through standardised feeds and API support. It centralises job management across all boards from one interface.

LogicMelon focuses on ROI tracking by job board — which boards are producing applications, at what cost, and which sources lead to placements. For agencies paying per-posting fees across multiple boards, this visibility matters.

All three tools charge on a subscription basis and integrate with the major UK ATS platforms. The integration typically runs: ATS posts job → multi-posting tool distributes to selected boards → applications flow back to multi-posting tool → forwarded to ATS candidate record. Each step is a potential failure point.

The most common integration failures

The failures that agencies report most consistently are:

  • Missing applications — the job board pushes applications to the ATS but the sync logic breaks. Applications sit on the job board unforwarded for days. In competitive roles where candidates are considering multiple offers, a 2-day delay in acknowledging an application can mean the candidate has already accepted elsewhere.
  • Duplicate candidate profiles — a candidate who applied to two roles, or who previously registered in the database, creates a second record rather than updating the existing one. The root cause is incomplete identity matching rules — the system matches on email address but not on name and phone, so a candidate who used a different email creates a duplicate.
  • Version mismatches — the ATS updates to a new API version; the job board's integration still uses the deprecated endpoint. Jobs stop posting until the ATS vendor or the board updates their integration. This is more common with REST APIs than XML feeds.
  • Authentication failures — incorrect endpoint URLs, missing required parameters, or OAuth token expiry silently break the integration. Jobs appear to post from the ATS side but do not appear on the board.
How to catch failures before they cost placements: Any agency using automated job posting should have a monitoring step — someone checking that live roles are actually visible on the boards they are supposed to be on, at least weekly. Integration failures tend to be silent: the ATS shows the job as posted, the board shows nothing. Discovering this when a role has been live for two weeks without applications is significantly more costly than a weekly five-minute check.

What a bespoke integration can do differently

For agencies with specific posting workflows — different posting logic by division, client-branded career pages that feed automatically to job boards, or proprietary candidate screening steps before applications reach the recruiter — a bespoke integration layer can handle complexity that multi-posting tools do not. The same applies to agencies that have built their own candidate-facing platform and need it to connect to job board APIs on their own terms rather than through a third-party aggregator.

The cost is development and maintenance time. Job board APIs change, authentication protocols update, and new boards enter the market. A bespoke integration needs ongoing technical maintenance in a way that a subscription to Broadbean does not.