Settings Sign In
JobInventory Feed Format

JobInventory Feed Format


Feed Guidelines

Your listings should comply with the following:

  • Include current jobs posted directly to your site or by a company representative.
  • All jobs must be your own, and not third party listings.
  • Do not include "crawled" or redistributed jobs in your feed.
  • Include complete data for the job including company name, location, job title and complete job description.
  • Job seekers should be able to view the entire job description without requiring a login and there should be no charge to apply to jobs.
  • Job seeker should be sent directly to full job description without being prompted or obstructed by interstitial messages/pages or popups.

In addition we ask that all organizations:

  • Include a clear contact page with a physical address.
  • Display a clear privacy policy to the end user.
  • Do not employ excessive or fraudulent advertising.

We reserve the right to remove any organization or feed from our index if they fail to adhere to the above guidelines.

XML Format

We accept feeds only in XML format.

XML feeds should be well-formed and follow W3C requirements on well formed XML document. The best way to ensure this is to run your prospective feed through an xml validator.

All job content must be inside CDATA sections to avoid issues processing your XML feed.

Character Encoding

Please provide the proper character encoding for your feed in the XML header. If you're not specifying the proper encoding your listings may come through with weird characters.

Submission Methods

JobInventory can fetch feeds from your site via HTTP, HTTPS, or FTP. We only download your feed as often as it updates, but we check often.

Feed Specification

Document should have root tag <listing> and the following tags under it.

  • <ctime> – last time, when feed file has been updated.
  • <entry> – jobs listings defined in the feed.

Each job listings should contain required and optional fields defined below. We like as much information about the listing as possible. The more information we have, the more likely a user is to find the listing. To that end, we accept a lot of fields with different information. Additionally, *some fields are required *and you can't submit your feed without them (the field has to be present and there has to be content in it).

Job Fields

Required Fields

Each job listing should include these fields.

  • id
  • title
  • location
  • description
  • date
  • url
Location Fields

The location fields indicate the location of the item being listed. For location-based search to work, it is highly recommended that each listing specify its location at least down to the city or zip/postal code level.

Location information should be defined under location tag and might contain the following field.

  • country
  • state
  • city
  • postalcode
Additional Fields

The more of these additional fields that are included for a listing, the more likely that listing is to be found in searches.

  • category
  • company
  • jobtype
  • education
  • experience
  • publisher

Field Descriptions


The occupation of the job being listed. We strongly advise to use one of the accepted values for category field.

Format: text

Accepted Values:

  • Management
  • Business and Financial Operations
  • Computer and Mathematical
  • Architecture and Engineering Occupations
  • Life, Physical, and Social Science
  • Community and Social Service
  • Legal
  • Education, Training, and Library
  • Arts, Design, Entertainment, Sports, and Media
  • Healthcare Practitioners and Technical
  • Healthcare Support
  • Protective Service
  • Food Preparation and Serving Related
  • Building and Grounds Cleaning
  • Personal Care and Service
  • Sales and Related
  • Office and Administrative Support
  • Farming, Fishing, and Forestry
  • Construction and Extraction
  • Installation, Maintenance, and Repair
  • Production
  • Transportation and Material Moving
  • Military Specific


The title of the listing

Format: text. Maximum length is 500 chars.


The description of the listing

Format: text. Maximum length is 20,000 chars.


The date/time at which the listing was created. If not specified then time of feed file generetion used by default.

Format: YYYY-MM-DD, or RSS format (i.e. 2004-07-16T14:00:00-07:00).


The URL of the details page for this listing. This URL must have relevent information about the listing. The URL must be unique in the feed, two different listings are not allowed to have the same URL.

Format: Fully qualified url.


The location of the listing. We highly recommend define location at least up to city level by including country, state and city information.


  • country - Country two letters abbreviation code. US by default.
  • state - State abbreviation code when applicable.
  • city - City name
  • postalcode - Postal code or zip code


Unique ID for this listing. You must use the same id with a listing in subsequent versions of the feed.

Format: Text.


The characteristics of the employment being  offered. We strongly advise to use one of the accepted values for jobtype field.

Format: Text.

Accepted Values:

  • Part-time
  • Contract
  • Volunteer
  • Internship
  • Temporary
  • Telecommute
  • Seasonal


Education required for the job position. We strongly advise to use one of the accepted values for education field.

Format: Text.

Accepted Values:

  • High School
  • Some College
  • Associate's Degree
  • Bachelor's Degree
  • Master's Degree
  • Doctorate
  • Professional


Experience required for the job position. We strongly advise to use one of the accepted values for experience field.

Format: Text

Accepted Values:

  • 0-2 years
  • 2-5 years
  • 5-7 years
  • 7-10 years
  • 10-15 years
  • 15+ years


Listing publisher name.

Format: Text.

Sample Feed

<?xml version="1.0" encoding="utf-8"?>



	    <title><![CDATA[Example title]]></title>


	    <description><![CDATA[Example description]]></description>



	    <category><![CDATA[Community and Social Service]]></category>

	    <company><![CDATA[Example Company]]></company>



	    <experience><![CDATA[5-7 years]]></experience>