Introduction

Welcome to the Jobrapido XML Feed Guide!
This document provides comprehensive instructions to help you successfully integrate and configure your job data feed with the Jobrapido platform.
By leveraging the XML feed, you can ensure that your job listings are published efficiently and reach a broad, relevant audience on Jobrapido.

This guide outlines the specifications and best practices for setting up and managing your XML feed, including support for the following advanced features:

Dynamic CPC (Cost-Per-Click) values
Budget Campaigns (with a further specific API integration)
CPA (Cost-Per-Action) campaign tagging
ATS Connectivity (with a further specific API integration)

Key Points:

The XML feed is a core integration method, enabling automatic publishing, updates, and removal of your job listings.
Once your feed URL is provided, jobs typically go live within 24 hours on Jobrapido (assuming there are no technical issues and the feed meets the required standards).
Supported protocols for feed retrieval (pull mode): HTTP, HTTPS, FTP, SFTP.
Feeds must be hosted on your own server; Jobrapido will handle scheduled downloads.
Supported formats: XML and JSON

Important: for XML nodes, Jobrapido does not support HTML entities. Always use raw characters (e.g., < instead of <).

Standard Feed Elements Reference

The XML feed must include a set of <job> elements, each representing a single job listing.
This section provides a detailed explanation of each XML tag/node to be used in your feed.
Elements marked Required must be included for your feed to be valid.

Element	Required	Description
`<title>`	Yes	The job title should clearly reflect the role. It must contain at least 3 characters and must not include marketing claims (e.g., "Best job ever"). Only the specific job title should be included.
`<location>`	Yes	Indicates the specific city or town where the job is located. Do not include full address or region details. If a job is listed in multiple locations, a separate entry must be created for each one.
`<state>`	Yes	The state, province, or region in which the job is located. Use the correct local designation.
`<country>`	Yes	The country where the job is located. Use the standard two-letter country code (e.g., US, IT).
`<postalcode>`	No	The ZIP or postal code of the job location. Useful for improved geo-location targeting.
`<company>`	Yes	The official company name offering the job position.
`<website>`	Yes (for Multiposters and Job Reposters)	Official or brand website domain(e.g., `www.example.com`).
`<publishdate>`	Yes	The date the job was first published, in DD/MM/YYYY format. It must match the date shown on the job description page, must not be older than 2 months, cannot be equal to the expiry date, and must not be in the future..
`<expirydate>`	Yes	The date the job listing expires, in DD/MM/YYYY format. It must be after the publish date and cannot be the same as the publish date.
`<url>`	Yes	The direct URL to the full job description page (not the application form). The URL must be in a valid format (http:// or https://) and may include tracking tokens.
`<email>`	No	A valid email address to receive applications. It can vary per job, may be encrypted, but must be active.
`<application_URL>`	No	If present, this URL should link directly to the job application form.
`<description>`	Yes	A complete and well-formatted job description enclosed within a CDATA section. It must include: job responsibilities, required skills and experience, and details about what the company offers (e.g., training, working hours, benefits). The content must be written in the native language of the job's location or in English, and must match the content on the job detail page. We encourage providing the job description with HTML formatting to allow proper styling (e.g., paragraphs, bullet points, headings) and ensure a better display for candidates.
`<reference_id>`	Yes	A unique identifier for each job post. It is used to update, refresh, or remove the listing from the feed.

Formatting Guidelines for Job Descriptions

By using basic HTML tags, we can render job ads in a structured and visually appealing way, while also ensuring they are fully indexed for automatic keyword extraction—enhancing their visibility and discoverability on Jobrapido.

Example in the Feed:

<description>
<![CDATA[
  <p>
    <strong style="color:#ff538f;">Customer Support Representative</strong><br>
    <em>Introduction:</em><br>
    At Company Example we work hard so our customers can play hard. We love what we do and because we have been 
    the market leader for over 40 years, we want the very best experts on our team.
  </p>
  <p>
    Working for us certainly isn't for the "shy and retiring", but it's definitely for the passionate, the daring, and the expert. 
    All of our employees are passionate about Company Example and act as our Brand Ambassadors—and why wouldn't they be, 
    when our ultimate vision is to help every woman in the world feel like the sexiest woman in the world.
  </p>
]]>
</description>

Structured XML Feed example

This example XML feed defines one job:

<?xml version="1.0" encoding="utf-8"?>
<source>
<jobs>
	<job>
		<title><![CDATA[Customer Support Representastive]]></title>
		<location><![CDATA[Phoenix]]></location>
		<state><![CDATA[AZ]]></state>
		<country><![CDATA[US]]></country>
		<postalcode><![CDATA[85003]]></postalcode>
		<company><![CDATA[Company Examplel]]></company>
		<website><![CDATA[www.examplesite.com]]></website>
		<publishdate><![CDATA[19/10/2018]]></publishdate>
		<expirydate><![CDATA[19/12/2018]]></expirydate>
		<url><![CDATA[http://www.examplesite.com/viewjob.cfm?jobid=123456]]></url>		
		<email><![CDATA[example@examplemail.com]]></email>
		<description>
		<![CDATA[<p><strong>Customer Support Representative</strong><br><em>Introduction:</em>
		<br>At Company Example we work hard so
		our customers can play hard. We love what we do and because we have been 
		the market leader for over 40 years we want the very best 
		experts on our team.</p><p>Working for us certainly 
		isn't for the "shy and retiring", but it's 
		definitely for the passionate the daring and 
		the expert. All of our employees 
		are passionate about Company Example and act
		as our Brand Ambassadors and why wouldn't they 
		be, when our ultimate vision is to help every woman
		in the world feel like the sexiest woman in the world.</p>]]>
		</description>
		<reference_id><![CDATA[ad3456]]></reference_id>
		<salary><![CDATA[$50K per year]]></salary>
		<education><![CDATA[Bachelors]]></education>
		<jobtype><![CDATA[fulltime, parttime]]></jobtype>
		<category><![CDATA[Category1]]></category>
		<experience><![CDATA[5+ years]]></experience>       
	</job>
	<job>...</job>
	<job>...</job>
	<job>...</job>
</jobs>
</source>

Custom Feed Elements Reference

We offer flexibility regarding the naming and structure of XML tags (nodes), especially when clients wish to introduce custom tags to enrich the feed or support specific integrations. Custom nodes generally fall under two main macro categories:

1.CAMPAIGN ACTIONs

What	Guidelines
Grouping Ads	To group dynamically Ads into specific Groups and run focused campaigns on. Add a `<group_campaign>` node (or a custom tag agreed upon with our team) to assign job ads to a group. Custom grouping tags must be pre-approved by Jobrapido. Any future changes must be communicated in advance to avoid misconfiguration.
Dynamic CPC	To enable Dynamic Cost Per Click (CPC) bidding, you can include a specific `<CPC>` tag in the feed. Add a `<CPC>` node (or a custom node agreed with our tech team) containing the CPC value as a numeric-only field. Only numeric values are accepted (e.g., 0.25). Do not include any text or symbols. The `<CPC>` value must be included in each job ad. A minimum CPC threshold can be set with your Sales Account Manager. If a lower value is provided in the feed, the job will be automatically dropped.
CPA Campaigns	For Cost-Per-Acquisition (CPA) campaigns, you can include a dedicated `<CPA>` tag. Define a `<CPA>` node (or equivalent) to include the target CPA value. As with CPC, values must be numeric only. Ensure consistent use of the tag across all applicable job listings.
Job Posting Budget	To set a specific budget cap per job ad, include a custom tag such as `<job_budget>` tag. Use numeric values only. Once the defined budget cap is reached, the ad will stop being sponsored. To continue delivery, an additional budget must be added.

2. API INTEGRATIONs

What	Guidelines
Applyrapido	We offer Applyrapido, an advanced ATS integration solution. Use the `<posturl>` node to define the application URL for the job. This enables seamless candidate redirection and application tracking. Request complete collateral documentation to set up the Applyrapido solution. If you're interested in integrating this solution, our tech team will provide full documentation and offer support throughout the entire process.
JSON Screener Questions	When using Applyrapido Solution, you can set also the screening question dynamically added at the job level. Use JSON nodes to define the Questions URL for each job. Request complete collateral documentation to set up the Applyrapido solution. If you're interested in integrating this solution, our tech team will provide full documentation and offer support throughout the entire process.
Campaign Budgets	To automatically associate a budget to a group of adverts (which will be parto of a cammpaign) via API, you can include a dedicated node in your feed. Use the `<campaign_name>` Tag. This enables us to programmatically create or update campaigns based on the job data provided. Request complete collateral documentation for setting up the Campaign Budget Management solution. If you're interested in integrating this solution, our tech team will provide full documentation and offer support throughout the entire process.

Multiposters and Job Reposters

What are Multiposters/Job Reposters?
Feeds provided by multiposters or job reposting platforms often contain job ads from various companies or recruiters. Jobrapido supports this structure, but it’s important that each individual ad is clearly attributed and categorized.

Feed Requirements
To ensure correct processing and display of each job ad, your XML feed must include the following fields for each job posting:

Element	Description
`<website>`	The URL or domain of the source or client for whom the job ad is posted.
`<company>`	The name of the employer or recruiting company.

Why It Matters?
Without these fields, Jobrapido may not be able to:

Display the correct company name on the ad
Assign the job to the appropriate category
Attribute the ad to the right client or domain
Proper feed structure ensures visibility, accuracy, and a better user experience for job seekers.

Common Issues That Can Cause Feed Rejection

Jobrapido uses automated systems to validate XML feeds.
If the feed contains invalid or inconsistent data, jobs may be rejected. Below are the most frequent issues and how to resolve them:

Issue	Action Required
Incomplete or empty job descriptions	Ensure that each job advert includes a complete and well-written description. Ads with missing or partial content will be rejected.
Feed details do not match job URL	All job details in the feed must match those shown on the destination job URL. Discrepancies will cause the job to be excluded.
Scam or suspected scam job ads	Only publish genuine job offers with legitimate, clear descriptions. Jobrapido actively blocks suspected scam content.
Obsolete or expired job ads	Make sure all jobs in the feed are active and up to date. Expired job ads will not be displayed.
Feed structure or tag changes	If you plan to change the feed structure or rename tag elements, notify Jobrapido in advance so we can update our system accordingly.
Job title is less than 3 characters	Always provide a clear and descriptive job title. Avoid abbreviations or single-word titles. Incomplete titles will be rejected.
Duplicate job adverts (same URL or reference ID)	Each job must have a unique URL and/or reference ID. Duplicate entries will be excluded.
Missing application instructions	Include clear, precise instructions on how to apply. Jobs with no way to apply will be rejected.
Jobs requiring payment or subscription to apply	Do not ask candidates to pay fees or subscribe to access job details or submit applications. Such job ads will be rejected.
The feed is blocked	Ensure your feed is accessible and not restricted by firewalls or IP filters. A blocked feed cannot be processed.
The feed is not reachable	Jobrapido must be able to regularly access the feed URL. If the feed is down or unreachable, jobs will not be updated or displayed.
Clean content	The content of the feeds must not contain any profanity, swear words, sexual content, or inappropriate language of any kind.

Frequently Asked Questions (FAQs)

What are the options for delivering the feed?

Supported protocols for feed retrieval (pull mode): HTTP, HTTPS, FTP, SFTP.

Does Jobrapido accept ZIP files?

Yes, ZIP files are accepted. The XML or JSON files must be properly formatted and included within the ZIP archive.

How often does Jobrapido index the feed?

By default, Jobrapido refreshes XML and JSON feeds 4 times per day.
This frequency can be increased for premium clients or upon specific sponsorship needs.

What if the same job is posted in multiple countries?

To ensure correct indexing across countries:

Submit one advert per country in the feed.
Use the <country> tag to define the job’s location.
Ensure each advert has a unique URL or reference ID.

What happens if I delete a job from my feed?

To ensure your job listings stay up-to-date on Jobrapido, you can manage expired or removed ads in one of the following ways:

Option 1: Include an <expiry_date> tag within each job entry in your feed.
Option 2: Remove the job’s URL from your site—this URL should return a 404 error or redirect to a page that does not display job details.

Using either of these methods, Jobrapido will update or remove the job ads within 24 hours from the time it processes the feed.
Please also share the contact details of your technical support team, so we can align on how feed updates and expiry logic are handled on your side.

Can I add additional custom elements in the feed

Yes, you can include custom (non-required) tags.
However, please ensure the following:

All standard Jobrapido-required fields must be included in every job advert.
Notify Jobrapido of any new tags.
Clearly specify the purpose of each custom tag, so we can ensure compatibility with our system.

This helps us maintain data integrity and avoid issues with job indexing.

How do I assign a specific CPC to job ads?

You can include a <cpc> tag in your feed to define the cost-per-click per job.

Coordinate with your Sales Account Manager to agree on:

Minimum/maximum CPC

Incremental values

Jobrapido will apply your bidding rules accordingly.

IMP: Make sure each job advert includes the tag only if it complies with the defined bidding parameters.

When should I add an email address, application URL, or PostURL?

If your job ads are to be published on Recruitrapido (Jobrapido-hosted pages), you need to include in your feed one of the following application methods:

An application email — where Jobrapido will forward candidate applications via email.
An application URL (ATS link) — directing users to your external application page.
A PostURL — to enable Jobrapido to send applications directly to your system via API.

Please ensure that at least one of these options is correctly configured for each job advert, so candidates can easily apply and your ads can be indexed without issues.

Get in touch

Feel free to write to Jobrapido if you have any doubt or you want to have more information.
You will be contacted by our Premium Service Representative as soon as possible.