Recruitment Marketing Public

Delivering jobs to distribution channels via a structured feed in Recruitment Marketing is a better, more reliable alternative to scraping.

Generating a structured feed

1. From the side menu, under Integrations, click on Feeds.
2. In the list of Free Jobs Boards, next to the Clinch generic feed, click the Edit (pen) icon to edit the feed.
3. Ensure the Enabled checkbox is checked.
4. Configure the feed rules if required, for example, on for some departments but not all. For more information, refer to Configuring jobs for distribution channels with feeds.
5. Back on the Free Jobs Board listing page, to obtain the unique URL for this feed, click the clipboard icon (Copy feed URL for this company) in the Actions column.
6. You will receive a confirmation that the URL has been copied to your clipboard.
7. The URL will follow the following format, and by default, the URL copied to your clipboard will be the XML version. To obtain the JSON version, upload the extension from XML to JSON:
   1. JSON - https://api.clinchtalent.com/v1/feeds/generic.json?company_id=CompanyID
      or
   2. XML - https://api.clinchtalent.com/v1/feeds/generic.xml?company_id=companyID

This URL now allows your job data to be shown in a structured format.

Sample structure of a posted job (XML format)

<jobs>
<publisher>Clinch</publisher>
<lastBuildDate>Thu, 3 Nov 2022 04:50:49 GMT</lastBuildDate>
<job>
<title>The title of the job posting </title>
<link>URL of the job posting on the career site</link>
<guid>Unique ID for the job posting</guid>
<ats_uid>Unique ID from the source ATS</ats_uid>
<requisition_ats_uid>Unique ID from the source ATS</requisition_ats_uid>
<postDate>The date the job was posted</postDate>
<opening_at/>
<closing_at/>
<opening_on/>
<closing_on/>
<summary>A short summary or overview of the job posting.</summary>
<description>The detailed advertising content, including HTML mark-up</description>
<remote> is this a remote job (true or false) </remote>
<streetaddress> </streetaddress>
<city> </city>
<state> </state>
<country> </country>
<postalcode> </postalcode>
<categories>
<category> A collections of assigned categories </category>
</categories>
<departments>
<department> A collections of assigned departments </department>
</departments>
<level> e.g. graduate, executive </level>
<employment_type> e.g. Full Time, Part Time </employment_type>
<company>
<name> Aqua Corp </name>
<website> </website>
</company>
</job>
</jobs>

Not all fields in the feed may be populated. This will depend on whether the relevant data field has been populated by the data received from the Applicant Tracking System (ATS).

Assigning attribution and source of hire when using a feed

If you would like to associate attribution and source of hire, you can set a utm_source when calling the feed. This will set the utm_source you provide onto all the job landing page URLs. The platform will then use this to assign attribution for traffic in analytics and reporting.

Below is an example feed URL where the desired attribution is to a jobs board called "super jobs board".

JSON format:

https://api.clinchtalent.com/v1/feeds/generic.json?company_id=12341234&utm_source=super_jobs_board

or

XML format:

https://api.clinchtalent.com/v1/feeds/generic.xml?company_id=12341234&utm_source=super_jobs_board

FAQs

What link should be provided in the <link> field?

The link must be the direct URL to the specific job posting rather than the search or listing page. This field drives the candidate apply button; providing a search page URL will direct candidates back to the main search page instead of the specific position.

Is it preferable to use separate URLs for Test and Production environments?

Yes. Test and Production operate in distinct environments, and each should reference the feed URL specific to that environment.

How should date fields like <postDate> or <closing_on> be formatted?

Per-job date fields are ISO 8601 formatted:

• <postDate>, <opening_on>, <closing_on> - date only, YYYY-MM-DD
  (e.g. 2025-12-31).
• <opening_at>, <closing_at> - UTC timestamp, YYYY-MM-DDTHH:MM:SSZ 
  (e.g. 2025-12-31T00:00:00Z).
• All dates are generated from values stored in UTC.

How do <postDate> and closing date fields affect job visibility?

Jobs appear in the feed as soon as they pass their opening date, regardless of the post and closing date. Date fields in the feed serve as informational metadata only.

Location fields vary depending on the underlying ATS Integration:

• Accuracy: There is no strict data validation beyond a 191-character limit on address fields. However, providing more granular detail (such as city, county, or specific address) improves geocoding accuracy and prevents confusion between locations with matching names.
• Postal/ZIP Codes: There is no enforced digit validation (e.g., 5 vs. 9 digits). Postal codes should simply match the standard structure of the location referenced.
• Region/State: Region or state fields should reflect the state/region location if no other detailed location data is provided.

What HTML tags and attributes are allowed in the <description> field?

Marked-up HTML is permitted in the job description, but it undergoes automatic sanitization. Any tag or attribute not included on the lists below will be stripped automatically before storage or display:

• Allowed Tags: div, strong, em, b, i, a, br, p, img, ul, ol, li, hr, h1, h2, h3, h4, h5, h6
• Allowed Attributes: href, class, src, width, height, alt, title, target, id