Skip to main content

Set Up XML Feed

Updated over a week ago

The XML job feed provides a structured way to transfer job data from your database into Wonderkind. It ensures that job details such as title, location, and company are automatically imported and formatted for use in campaigns.

Once the XML feed is set up, the feed keeps job ads consistent, accurate, and ready for review in your account, reducing manual setup and simplifying campaign activation.

In this documentation, we’ll walk you through the steps on how to:

Let’s get started 🚀

Prepare XML Feed URL

Your XML feed must be hosted at a public URL so Wonderkind can access and update jobs in campaigns.

Requirements

  • Must allow GET and HEAD requests

  • Content-Type should be either text/xml or application/xml

Optional

  • Add an ETag header to detect changes automatically.

TIP: Always verify the feed URL is stable and accessible before sharing it with Wonderkind. You can do this by testing the URL in a browser or using a tool like HTTP Status Checker or cURL. This ensures the feed is reachable and responds correctly.

Required XML Structure

Wonderkind uses a Market Standard XML format, where each <item> corresponds to a single job. Your XML must include certain fields to be accepted.

Required Fields

The feed must include the following elements to ensure proper import:

Element

Description

Example

<title>

Job title only. Avoid type, location, or extras.

<![CDATA[Sales Executive]]>

<referencenumber>

Unique job ID that never changes.

<![CDATA[unique123131]]>

<url>

Job description page with source=Wonderkind token.

<![CDATA[examplesite.com/job123?source=Wonderkind]]>

<company>

Company or brand name (keep simple/consistent).

<![CDATA[ABC Hospital]]>

<location>

Full city or region name (no abbreviations).

<![CDATA[Amsterdam]]>

<country>

Job’s ISO country code

<![CDATA[US]]>

<language>

ISO code for language

<![CDATA[EN]]>

NOTE: If targeting an entire country instead of a city, place the ISO country code in <location>.

Optional Fields

Additional fields improve campaign performance and clarity:

Element

Description

Example

<category>

Comma-separated categories.

<![CDATA[Healthcare, Nursing]]>

<description>

Job description text

<![CDATA[Responsible for patient care...]]>

<salary>

Annual or monthly salary

<![CDATA[$50,000 per year]]>

<education>

Required education level

<![CDATA[Bachelors]]>

<benefits>

Benefits offered

<![CDATA[Health insurance, Pension]]>

<experience>

Experience required

<![CDATA[3 years]]>

<ponumber>

Purchase order number

<![CDATA[PO120324225]]>

<postalcode>

Job location postal code

<![CDATA[85003]]>

<budget>

Campaign budget

<![CDATA[$5000]]>

<address>

Full job address

<![CDATA[Rozengracht 52]]>

<image1>

Image for the ad

<campaignid>

Campaign identifier

<![CDATA[campaign_ABC123]]>

<packageid>

Package ID with distribution rules

<![CDATA[package_456XYZ]]>

TIP: Include optional fields wherever possible; richer job data leads to better-performing campaigns.

WARNING: Use CDATA (Character Data) sections only when necessary, such as when your job description includes special characters (<, >, &) or raw data that may break XML.

For example, consider <note> as a text and not a tag within the XML URL.

Example XML Job Entry

<job>
<title>Business Development Manager</title>
<company>Wonderkind</company>
<country>NL</country>
<language>NL</language>
<location>Amsterdam</location>
<referencenumber>123456789</referencenumber>
<url>http://www.testwonderkind.com?source=Wonderkind</url>
</job>

NOTE: Always write full city names (✔ Alphen aan de Rijn, not ❌ Alphen a/d Rijn).

Integration Process

Once the XML feed URL is generated, it should be connected to the data source for automatic import.

NOTE: For more information on how to import the XML URL, please refer to this document.

Did this answer your question?