Knowledge Center

Back to the Dice Knowledge Center

Batch Posting Instructions

Updated September 4, 2020

Introduction

In addition to the web-based job posting process, Dice offers an email-based batch posting system to allow automated job posting and avoid redundant data entry.

In order to allow clients to easily add, delete and update their job postings the batch posting system implements a "total replace" processing mode. Under that mode, batch files are assumed to include all jobs that the client intends to post, including those jobs that have been previously submitted. Any jobs not present in the batch posting file will be removed.

Also available is an "incremental" batch posting mode, where batches are comprised of one or more jobs a client wishes to add to their existing set of jobs. There is no way to delete jobs with an incremental batch. A client must submit a "total replace" batch or manually delete jobs to remove them.

Please note that your Dice ID is your Group ID.


Email Format

Batch posting requests must be submitted via email to dicejobs@dice.com. That email must include a plain-text batch file, as described below, and must contain only your batch posting username and password in the body. If you do not have a batch posting username and password contact support@dice.com to obtain one.
 

Example Batch Posting Message
To: dicejobs@dice.com
Subject: (May be anything or left blank)
Body: username: batchUsername
password: batchPassword
Attachment: jobs.txt

 

Batch File Format

The batch posting file is a plain-text SGML file that defines the jobs you wish to post. The requirements for this file, a complete list of the required and optional tags and an example batch file, are provided below.
 

File Format Requirements
  • Batch files must be submitted as an email attachment
  • Batch files can be compressed into .gz files
  • Batch files must be plain-text files (i.e. not MS Word documents)
  • Batch file names must contain only standard characters and must not contain any spaces
  • Each batch file must contain jobs for only one Dice ID
  • Each batch file must contain at least one job
  • Each tag must appear on a line by itself
  • Each tag must start on the first column of a line
  • There must be no space between the tag name and its bracket (e.g.<title> not < title >)
  • Except for the <comment> tag, no tag may contain a line break and the field contents and closing tag must be on the same line as the opening tag
  • The first line of the file must read exactly: <!doctype batch totalreplace> for total replace batches or <batch> for incremental batches
  • Each job definition begins with a <doc> tag and ends with a </doc> tag, and all other tags related to that job must appear between those tags
  • The order of tags within the <doc> and </doc> tags is not important
  • The characters < and > must be expressed as &lt; and &gt; respectively if used within a tag value
     
Required and Optional Tags
Tag Name
Required or Optional
Definition
Maximum Length
Example
positionid Required A client-assigned code that is unique to this job. This code must not include spaces and should contain only standard characters. If this code is not unique the batch file will not process properly. 15
<positionid>1234</positionid>
diceid Required The Group ID assigned to the client submitting the batch. This Group ID must be the same for all jobs in the batch and must be associated with the batch posting username submitted with the batch file. Group IDs are always lowercase. 8
<diceid>yourgroupid</diceid>
taxterm Optional The terms of employment being offered for this job. Must contain one of the following codes:
  • FULLTIME
  • PARTTIME
  • CON_W2
  • CON_HIRE_W2
  • CON_CORP
  • CON_HIRE_IND
  • CON_HIRE_CORP
  • CON_IND

This tag may be repeated to indicate that multiple taxterms apply to the job.

15
<taxterm>CON_W2</taxterm>
<taxterm>TEMP</taxterm>
country Optional The two-letter ISO country code for the country in which the job seeker would be working if hired for this job. 2
<country>US</country>
    or:
<country>CA</country>
state Optional The US state or Canadian province in which the job seeker would be working if hired for this job. This field is optional but highly recommended; without it your job posting will not show up when job seekers search by state or province. This field must contain a valid two-letter state or province code or the code "INT" for jobs in countries outside the US or Canada. 3
<state>IA</state>
    or:
<state>AB</state>
postalcode Optional The zip or postal code for the city in which the job seeker would be working if hired for this job. If no postal code is specified the job will not be searchable by zip code or metro area. 6
<postalcode>50322</postalcode>
location Optional The city in which the job seeker would be working if hired for this job. This field is optional but highly recommended; without it your job posting will not show up when job seekers search by city. 34
<location>Urbandale</location>
remote Optional Must be "Y" if working remote is available for this job and "N" otherwise. 1
<remote>Y</remote>
areacode Optional The area code in which the job seeker would be working if hired for this job. This field is optional but highly recommended; without it your job posting will not show up when job seekers search by area code. 3
<areacode>515</areacode>
telecommute Optional Must be "Y" if telecommuting is available for this job and "N" otherwise. 1
<telecommute>N</telecommute>
travel Optional The percent of travel involved with this job. Must be an integer between 0 and 100 inclusively. 3
<travel>0</travel>
company Optional Your company name. 60
<company>Dice, Inc.</company>
companystate Optional Your company's US state or Canadian province. This field must contain a valid two-letter state or province code or the code "INT" for companies outside the US or Canada. 3
<companystate>IA</companystate>
companycity Optional Your company's city. 20
<companycity>Urbandale</companycity>
companyzip Optional Your company's zip code. 10
<companyzip>50322</companyzip>
addr1 Optional The first line of your company's address. 50
<addr1>4101 NE Urbandale Dr.</addr1>
addr2 Optional The second line of your company's address. 50
<addr2>PO BOX 1234</addr2>
url Optional Your company's URL. This URL is displayed with your company name and address and should not be confused with the <applylink> tag, which is linked from the "Apply for this Job" button. 100
<url>http://www.dice.com/</url>
recruiter Optional The person a job seeker would contact to apply for this job. 40
<recruiter>Rolan D. Dice</recruiter>
recruiteremail Optional An existing Dice User email address of the recruiter you would like attached to the job posted. 40
<recruiteremail>roland@dice.com</recruiteremail>
phone Optional This job's contact phone number. 15
<phone>(515) 280-1144</phone>
ext Optional This job's contact phone extension. 6
<ext>1234</ext>
fax Optional This job's contact fax number. 15
<fax>(515) 280-1452</fax>
altphone Optional An alternate phone number for this job's contact. 15
<altphone>(877) 386-3323</altphone>
email Required The email address that Dice will use when sending messages from job seekers user the "Apply for this Job" button. If the <applylink> tag is used this field is ignored. 70
<email>hr@dice.com</email>
applylink Optional The URL that Dice will link from the "Apply for this Job" button. If this tag is used the <email> field is ignored. 70
<applylink>http://example.com/job?ID=1</applylink>
joblength Optional The length of the this job, if applicable. For example, if the job posting lists a 6-month contract, this field could state "6 Months". Permanent positions may wish to state "Full Time" in this field. 55
<joblength>Full Time</joblength>
payrate Optional The pay rate for this job. Non-numeric values such as "Competitive" are allowed, but specific dollar ranges may increase the reponse rate for this job. 55
<payrate>$75,000 - $95,000</payrate>
jobtitle Required The formal title of the position you are advertising. 95
<jobtitle>Integration Engineer</jobtitle>
skillsreq Optional A short list of skills required for this job. While not required, if this tag is not provided the value defaults to "See job description". 55
<skillsreq>Perl, HTML, JavaScript</skillsreq>
dtncompany Optional The DiceID of the company that seekers will connect to when using the Dice Talent Network for this job. If omitted or blank this field defaults to the posting DiceID. 8
<dtncompany>yourdiceid2</dtncompany>
dtnrecruiter Optional The username of the recruiter that seekers will connect to when using the Dice Talent Network for this job. If omitted or blank users will be connected to the company instead of a specific recruiter. 64
<dtnrecruiter>rolan@dice.com</dtnrecruiter>
autoresponse Optional If you have configured one or more autoresponse messages via the web interface, enter any one of your autoresponse codes in this field to select and enable a specific response for this job. If omitted or blank no autoresponse will be sent for applications to this job. 8
<autoresponse>2586</autoresponse>
comments Required The main body of the job description. This field may include linebreaks and escaped <B> </B> and <BR> tags. Both plain-text line breaks and these escaped HTML tags will be respected when the field is displayed. 10000
<comments>
Combines software development and solutions
architecture with sales &lt;BR&gt;
engineering to solve related data sharing
challenges while supporting both the internal
and &lt;BR&gt;
external customers in the integration and
expansion of the Company's product offerings.
</comments>

Deprecated Tags

There are several tags that were previously accepted or required by the batch processing system that are no longer in use. Batch files including these tags will process correctly, but the tags will be ignored. If possible, these tags should be omitted from batch files to prevent possible processing errors in the future. These tags include:

  • filetype
  • jobtype
  • oscarofficenum

File Format Notes
  • Each total replace batch file must contain all jobs you wish to post. Any jobs currently posted but not in the batch posting file will be removed. Incremental batch files will not remove jobs already posted.
  • Leading and trailing white space is removed from all fields before processing. However, linebreaks within the <comment> tag will be respected after leading and trailing white space is removed.
  • Position IDs must be unique. If a position ID is duplicated within the batch only one of the jobs with that ID will be posted.
  • The characters < and > must be expressed as &lt; and &gt; respectively. Failure to escape these characters will prevent the batch from processing.
  • A batch file must contain jobs for only one Dice ID, and that Dice ID must be associated with the batch posting username.


Example Batch File
<!doctype batch totalreplace>
<doc>
<positionid>1234</positionid>
<diceid>yourdiceid</diceid>
<taxterm>FULLTIME</taxterm>
<country>US</country>
<state>IA</state>
<postalcode>50322</postalcode>
<location>Urbandale</location>
<remote>Y</remote>
<areacode>515</areacode>
<telecommute>N</telecommute>
<travel>0</travel>
<company>Dice, Inc.</company>
<companystate>IA</companystate>
<companycity>Urbandale</companycity>
<companyzip>50322</companyzip>
<addr1>4101 NE Urbandale Dr.</addr1>
<url>http://www.dice.com/</url>
<recruiter>Rolan D. Dice</recruiter>
<recruiteremail>roland@dice.com</recruiteremail>
<phone>(515) 280-1144</phone>
<ext>1234</ext>
<fax>(515) 280-1452</fax>
<altphone>(877) 386-3323</altphone>
<email>hr@dice.com</email>
<joblength>Full Time</joblength>
<payrate>$75,000 - $95,000</payrate>
<jobtitle>Integration Engineer</jobtitle>
<skillsreq>Perl, HTML, JavaScript</skillsreq>
<dtncompany>yourdiceid2</dtncompany>
<dtnrecruiter>rolan@dice.com</dtnrecruiter>
<autoresponse>2586</autoresponse>
<comments>
Combines software development and solutions architecture with sales
&lt;BR&gt;engineering to solve related data sharing challenges while supporting both the internal and
&lt;BR&gt;external customers in the integration and expansion of the Company's product offerings.
</comments>
</doc>
<doc>
...Another job for yourdiceid...
</doc>

 

Batch Posting Report

Each time a batch posting is processed a report that details the number of jobs processed and any errors that may have occurred will be returned to the email address that submitted the batch. This report can be used to confirm that your jobs are being posted as you intended.


Sample Batch Posting Report
From: BatchSupport@dice.com
Date: Thu, 22 Jun 2006 15:23:49 -0500 (CDT)
To: you@yourDomain.com
Subject: Batch Job Status Report for Your Company, yourgroupid
Body: Processing summary for file jobs.txt [Total Replace]
Total jobs submitted: 116
Jobs successfully processed: 116
Jobs failed to be processed: 0
0 job(s) failed to be posted because the job count limit has been reached.
Please view the attached Batch Submission Status Report for processing details.
======================================================

 


Questions? Issues? Contact Product Support anytime by emailing support@dice.com.

Prefer to talk on the phone? Call us Monday-Friday, 8am to 5pm CST at 888-321-3423.
 

Loading...