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.
Batch posting requests must be submitted via email to email@example.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 firstname.lastname@example.org to obtain one.
Example Batch Posting Message
(May be anything or left blank)
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
Type: .txt or compressed .txt files into .gz Size Limit: 10mb
Batch files must be submitted as an email attachment
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
For incremental batches <batch> for incremental
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 < and > respectively if used within a tag value
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.
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.
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.
The formal title of the position you are advertising.
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. Please note: URLs, videos, iframes, and images are not allowed, and will be stripped from the job posting prior to going live.
Combines software development and solutions
architecture with sales <BR>
engineering to solve related data sharing
challenges while supporting both the internal
external customers in the integration and
expansion of the Company's product offerings.
The terms of employment being offered for this job. Must contain one of the following codes:
This tag may be repeated to indicate that multiple taxterms apply to the job.
Allow staffing firms and recruiters to apply on behalf of the candidate. "Y" or "N".
The two-letter ISO country code for the country in which the job seeker would be working if hired for this job.
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.
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.
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.
Must be "Y" if working remote is available for this job and "N" otherwise.
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.
Must be "Y" if telecommuting is available for this job and "N" otherwise.
Telecommute is used synonymously for jobs that allow some work from home as an option, but not fully remote. Telecommute jobs are also commonly referred to as "hybrid" jobs.
The percent of travel involved with this job. Must be an integer between 0 and 100 inclusively.
Your company name.
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.
Your company's city.
Your company's zip code.
The first line of your company's address.
<addr1>4101 NE Urbandale Dr.</addr1>
The second line of your company's address.
<addr2>PO BOX 1234</addr2>
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.
The person a job seeker would contact to apply for this job.
<recruiter>Rolan D. Dice</recruiter>
An existing Dice User email address of the recruiter you would like attached to the job posted.
The URL that Dice will link from the "Apply for this Job" button. If this tag is used the <email> field is ignored. Please note: Dice will use the exact link that is provided in this field. Dice will make no attempt to encode or unencode &’s or &. Please ensure your website is able to properly resolve the same value provided in this field.
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 < and > 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>
<addr1>4101 NE Urbandale Dr.</addr1>
<recruiter>Rolan D. Dice</recruiter>
<payrate>$75,000 - $95,000</payrate>
Combines software development and solutions architecture with sales
<BR>engineering to solve related data sharing challenges while supporting both the internal and
<BR>external customers in the integration and expansion of the Company's product offerings.
<trackingpixel><img style="display: none;" src="tracking url here" /></trackingpixel>
...Another job for yourdiceid...
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
Thu, 22 Jun 2020 15:23:49 -0500 (CDT)
Batch Job Status Report for Your Company, yourgroupid
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 email@example.com.
Prefer to talk on the phone? Call us Monday-Friday, 8am to 5pm CST at 888-321-3423.