Real Time Posting (RTP) is a service that allows customer systems to post jobs to Monster similarly to posting jobs being logged into the Monster hiring application system (http://hiring.monster.com). RTP reduces the time required for recruiters to post jobs and enables nearly instant processing of opportunities.

Purpose and Objective

The Purpose of this guide is to help you publish job ads to Monster via the Monster's Business Gateway (BGW) in real time.
In the following guide, we describe how to interact with the the BGW by sending SOAP messages over HTTPS.

This guide is divided into 3 main areas:

Sample Job in Monster XML Format:

 

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

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

  <SOAP-ENV:Header>

    <mh:MonsterHeader xmlns:mh="http://schemas.monster.com/MonsterHeader">

      <mh:MessageData>

        <mh:MessageId>Company Jobs created on 09/08/2011 02:41:44 PM</mh:MessageId>

        <mh:Timestamp>2011-09-08T14:41:44Z</mh:Timestamp>

      </mh:MessageData>

    </mh:MonsterHeader>

    <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">

      <wsse:UsernameToken>

        <wsse:Username>username</wsse:Username>

        <wsse:Password>password</wsse:Password>

      </wsse:UsernameToken>

    </wsse:Security>

  </SOAP-ENV:Header>

  <SOAP-ENV:Body>

    <Job jobRefCode="myownjobreferencecode" jobAction="addOrUpdate"
    inventoryType="transactional" jobComplete="true"
    xmlns="http://schemas.monster.com/Monster"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://schemas.monster.com/Monster
    http://schemas.monster.com/Current/xsd/Monster.xsd">

      <RecruiterReference>

        <UserName>username</UserName>

      </RecruiterReference>

      <JobInformation>

        <JobTitle>Executive Officer </JobTitle>

        <JobLevel monsterId="12"/>

        <JobType monsterId="1"/>

        <JobStatus monsterId="4"/>

        <Salary>

          <Currency monsterId="1"/>

          <SalaryMin>100000.00</SalaryMin>

          <SalaryMax>150000.00</SalaryMax>

          <CompensationType monsterId="1"/>

        </Salary>

        <Contact hideAll="false" hideAddress="true" hideStreetAddress="true" hideCity="true"
        hideState="true" hidePostalCode="true" hideCountry="true" hideContactInfoField="false"
        hideCompanyName="false" hideEmailAddress="true" hideFax="true"
        hideName="false" hidePhone="true">

          <Name>John</Name>

          <CompanyName>John's Company</CompanyName>

          <Address>

            <StreetAddress>1 John Street</StreetAddress>

            <StreetAddress2>PO Box 1</StreetAddress2>

            <City>Johnstown</City>

            <State>PA</State>

            <CountryCode>US</CountryCode>

            <PostalCode>15955</PostalCode>

          </Address>

          <Phones>

            <Phone phoneType="work">999-999-9999</Phone>

          </Phones>

          <E-mail>john@johnscompany.com</E-mail>

        </Contact>

        <PhysicalAddress>

          <StreetAddress>5 Clock Tower</StreetAddress>

          <StreetAddress2>Suite 500</StreetAddress2>

          <City>Maynard</City>

          <State>MA</State>

          <CountryCode>US</CountryCode>

          <PostalCode>01754</PostalCode>

        </PhysicalAddress>

        <DisableApplyOnline>false</DisableApplyOnline>

        <HideCompanyInfo>false</HideCompanyInfo>

        <JobBody>This is the Job Body that needs to be of certain length. 
        This is more information about the Job.
        It should be detailed and well written to attract seekers.
        </JobBody>

        <AdditionalSearchKeywords>additional search keyword
        </AdditionalSearchKeywords>

        <EducationLevel monsterId="1"/>

      </JobInformation>

      <JobPostings>

        <JobPosting desiredDuration="60" bold="true" jobPostingAction="refresh">

          <InventoryPreference>
            <Autorefresh desired="true">

              <Frequency>7</Frequency>

            </Autorefresh>

            <CareerAdNetwork desired="true">

              <Duration>14</Duration>

            </CareerAdNetwork>
           </InventoryPreference>

          <Location>

            <City>Boston</City>

            <State>MA</State>

            <CountryCode>US</CountryCode>

            <PostalCode>02125</PostalCode>

          </Location>

          <JobCategory monsterId="47"/>

          <JobOccupations>

            <JobOccupation monsterId="11909"/>

          </JobOccupations>

          <BoardName monsterId="1"/>

          <Industries>

            <Industry>

              <IndustryName monsterId="1"/>

            </Industry>

          </Industries>

          <Video monsterId="123" refCode="video_A">

          </Video>

        </JobPosting>

      </JobPostings>

    </Job>

  </SOAP-ENV:Body>

</SOAP-ENV:Envelope>
 

Information about Job Fields

Field Name	Requirement	Data Type	Constraints	Notes
Username	Required	String		Value provided by Monster
Password	Required	String		Value provided by Monster
jobRefCode	Required	String	<= 50 characters	Recruiter specific term used to uniquely identify job.
jobAction	Optional	String	Common choices are: addOrUpdate add delete Full list of valid entries can be found in schema at  Job Schema	Recommend using “addOrUpdate” as this allows new ads to be posted and updates to active jobs. “add” allows new ads to be posted. Updates to active jobs not allowed.
InventoryType	Optional	String	Choices are: transactional areaWideTransactional areaWideSlotted slotted	This field specifies the type of inventory that should be used to post the job.  Most customers will use transactional inventory. If no inventory is specified, the account's default settings will be used.
RecruiterReference\UserName	Required	String		Value provided by Monster
JobTitle	Required	String	<= 100 characters
JobLevel attribute: monsterId	Required	Integer	A list of valid entries can be found at: JobLevel list
JobType attribute: monsterId	Required	Integer	A valid list of entries for the US Channel is 1 for Employee, 2 for Temporary/Contract, 3 for Intern and 20 for Seasonal. Entries for other channels can be found at: JobType list
JobStatus attribute: monsterId	Required	Integer	A list of valid entries can be found at: JobStatus list
Salary	Optional
Contact attribute: HideAll	Optional	Boolean	true or false (case sensitive!)	When set to “true”, hides contact given and family name, company name, street address, street address2, city, state, postal code, phone, fax when viewing a job.
Contact attribute: HideAddress	Optional	Boolean	true or false (case sensitive!)	When set to “true”, hides contact street address, street address2, city, state and postal code when viewing a job.
Contact attribute: HideStreetAddress	Optional	Boolean	true or false (case sensitive!)	When set to “true”, hides street address only (NOT street address2) when viewing a job.
Contact attribute: HideCity	Optional	Boolean	true or false (case sensitive!)	When set to “true”, hides city when viewing a job.
Contact attribute: HideState	Optional	Boolean	true or false (case sensitive!)	When set to “true”, hides State when viewing a job.
Contact attribute: HidePostalCode	Optional	Boolean	true or false (case sensitive!)	When set to “true”, hides postalcode when viewing a job.
Contact attribute: HideCountry	Optional	Boolean	true or false (case sensitive!)	No impact as country is not shown in standard job template.
Contact attribute: HideContact	Optional	Boolean	true or false (case sensitive!)	No impact.
Contact attribute: HideEmailAddress	Optional	Boolean	true or false (case sensitive!)	No impact as email address is not displayed when viewing a job.
Contact attribute: HideFax	Optional	Boolean	true or false (case sensitive!)	When set to “true”, hides fax number when viewing a job.
Contact attribute: HideName	Optional	Boolean	true or false (case sensitive!)	When set to “true”, hides given name and family name when viewing a job.
Contact attribute: HidePhone	Optional	Boolean	true or false (case sensitive!)	When set to “true”, hides given name and family name when viewing a job.
Contact\Name	Required	String	<= 255 characters
Contact\  CompanyName	Optional	String	<= 255 characters	JobSearch: Whether provided or not, if company name on account is not an ad agency, the company name on the account will be displayed in job search results. If provided and if company name on account is an ad agency, this company name is displayed as company name in job search results. JobView: If provided, this is company name that will be displayed when viewing a job. If not provided, company name on account will be displayed.
Contact\Address	Optional
Phones	Optional	String	Between 8 and 50 characters	Has to be either “contact” or “fax” type to be displayed. Other phone types can be provided but will not be displayed.
E-mail	Optional	String	<= 100 characters	Only one allowed per job posting.
PhysicalAddress	Optional			Represents a job’s physical location. Controls the visible location information that is displayed on the job posting Controls how the job is pulled up in the job search results. Typically includes <City>, <State>, <CountryCode> and <PostalCode>. <StreetAddress> and  <StreetAddress2> may be provided as well.
DisableApplyOnline	Optional	Boolean	true or false (case sensitive!)	When set to “false”, allows job seekers to apply for the job online. When set to “true”, job seekers will not be able to apply for the job online.
HideCompanyInfo	Optional	Boolean	true or false (case sensitive!)	When set to “true”, company name in job search results and top portion of job view show as confidential. Hides company name in “Job Summary” and “Contact Information” sections of job view.
JobBody	Required	String	>= 25 characters
AdditionalSearchKeywords	Optional	String	<= 255 characters
EducationLevel attribute: monsterId	Optional	Integer	A list of valid entries can be found at: EducationLevel list
JobPostings	Required
JobPosting attribute: DesiredDuration	Optional	Integer	# of days	Highly recommended that this field be supported
JobPostings attribute: Bold	Optional	Boolean	true or false (case sensitive!)	A true value will bold the job title in job search results.
JobPostings attribute: jobPostingAction	Optional	String	Value of “refresh”	Makes the job refresh (move to the top of job search results)
CareerAdNetwork attribute: desired	Optional	Boolean	true or false (case sensitive!)	A true value will set CAN (Career Ad Network ) on the job. CAN allows one to enhance Monster Job Posting with targeted advertising on the Monster network and its diverse partner websites.
CareerAdNetwork\Duration	Only required when desired attribute=1	Integer	# of days: 7, 14 or 30
Autorefresh attribute: desired	Optional	Boolean	true or false (case sensitive!)	A true value will make the job refresh (move to the top of job search results) in 14 days
Autorefresh\    Frequency	Only required when desired attribute= true	Integer	# of days: 7, 14, 30, 60	Not available on 7 day job postings.
JobPosting\    Location	Required			Controls what Monster search location the job is going to be posted to
JobCategory	Required		A list of valid job categories can be found at: JobCategory list
JobOccupation	Required		A list of valid occupationId’s for given job categories can be found at: JobOccupation list	Can contain a minimum of one and a maximum of three per job. Recommend the use of “other” occupation be minimized.
BoardName attribute: monsterId	Required	Integer	1 is value for Monster core job board	Contact Monster Representative for other board ids, such as Diversity board
Industry	Optional		Valid entries can be found at: Industry list	If submitted, can provide a minimum of one and a maximum of three per job.
Video attribute: monsterId	Optional	Integer		Value provided by Monster
MonsterOnDemand attribute: monsterId	Optional	Boolean	true or false (case sensitive!)	A true value will post the job on Comcast's "On Demand" television channel (where available).
MonsterOnDemand\Description	Optional	String		Will be the specific MonsterOnDemand description. If not provided, the description will be defined as first 400 characters of JobBody.

Create the XML Request

Requests to BGW must be sent in the form of SOAP envelopes, which is composed of a header and a body.
Each request can include a maximum of a single job and must follow the schema for the Monster Job Postings.

Envelope

The envelope is a container for Soap message.

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

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

  <SOAP-ENV:Header>

  </SOAP-ENV:Header>

  <SOAP-ENV:Body>

  </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Monster SOAP Schema can be found here

Header

The header contains information about the request, request protocol, and a security protocol with the user credentials.

    <mh:MonsterHeader xmlns:mh="http://schemas.monster.com/MonsterHeader">

      <mh:MessageData>

        <mh:MessageId>Company Jobs created on 09/08/2011 02:41:44 PM</mh:MessageId>

        <mh:Timestamp>2011-09-08T14:41:44Z</mh:Timestamp>

      </mh:MessageData>

    </mh:MonsterHeader>

    <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">

      <wsse:UsernameToken>

        <wsse:Username>username</wsse:Username>

        <wsse:Password>password</wsse:Password>

      </wsse:UsernameToken>

    </wsse:Security>

Monster Header Schema can be found here

Body - Job

The Body contains all the data related to the job you're posting and should comply with Monster job schema.

• XML sample below outlines the job entities commonly used for posting a job ad.
• More job request samples can be found here.
• The full Monster Job Schema can be found here.

The XML job is described by 3 main sections

• Processing Information
• Job Information
• Job Posting

Processing Information

This section contains information about the way the Job Message will be processed, under which account e.g. information about the kind of action (update, delete, etc...)

<Job jobRefCode="myownjobreferencecode" jobAction="addOrUpdate" jobComplete="true"
xmlns="http://schemas.monster.com/Monster"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.monster.com/Monster
http://schemas.monster.com/Current/xsd/Monster.xsd">

      <RecruiterReference>

        <UserName>username</UserName>

      </RecruiterReference>

<!−− [CONTINUES...] −−>

Job Information

This contains the main information that will be displayed in the job ad. Example: job Title, job description (jobBody), salary , contact...

    <JobInformation>

        <JobTitle>Executive Officer </JobTitle>

        <JobLevel monsterId="12"/>

        <JobType monsterId="1"/>

        <JobStatus monsterId="4"/>

        <Salary>

          <Currency monsterId="1"/>

          <SalaryMin>100000.00</SalaryMin>

          <SalaryMax>150000.00</SalaryMax>

          <CompensationType monsterId="1"/>

        </Salary>

        <Contact hideAll="false" hideAddress="true" hideStreetAddress="true" hideCity="true"
        hideState="true" hidePostalCode="true" hideCountry="true" hideContactInfoField="false"
        hideCompanyName="false" hideEmailAddress="true" hideFax="true"
        hideName="false" hidePhone="true">

          <Name>John</Name>

          <CompanyName>John's Company</CompanyName>

          <Address>

            <StreetAddress>1 John Street</StreetAddress>

            <StreetAddress2>PO Box 1</StreetAddress2>

            <City>Johnstown</City>

            <State>PA</State>

            <CountryCode>US</CountryCode>

            <PostalCode>15955</PostalCode>

          </Address>

          <Phones>

            <Phone phoneType="work">999-999-9999</Phone>

          </Phones>

          <E-mail>john@johnscompany.com</E-mail>

        </Contact>

        <PhysicalAddress>

          <StreetAddress>5 Clock Tower</StreetAddress>

          <StreetAddress2>Suite 500</StreetAddress2>

          <City>Maynard</City>

          <State>MA</State>

          <CountryCode>US</CountryCode>

          <PostalCode>01754</PostalCode>

        </PhysicalAddress>

        <DisableApplyOnline>false</DisableApplyOnline>

        <HideCompanyInfo>false</HideCompanyInfo>

        <JobBody>This is the Job Body that needs to be of certain length. 
        This is more information about the Job.
        It should be detailed and well written to attract seekers.
        </JobBody>

        <AdditionalSearchKeywords>additional search keyword
        </AdditionalSearchKeywords>

        <EducationLevel monsterId="1"/>

    </JobInformation>

Job Postings

This section sets where the job posting will be searchable, identified by the combination of JobCategory, JobOccupation, Location and BoardName.

    <JobPosting desiredDuration="60" bold="true" jobPostingAction="refresh">

          <InventoryPreference>
            <Autorefresh desired="true">

              <Frequency>7</Frequency>

            </Autorefresh>

            <CareerAdNetwork desired="true">

              <Duration>14</Duration>

            </CareerAdNetwork>
          </InventoryPreference>

          <Location>

            <City>Boston</City>

            <State>MA</State>

            <CountryCode>US</CountryCode>

            <PostalCode>02125</PostalCode>

          </Location>

          <JobCategory monsterId="47"/>

          <JobOccupations>

            <JobOccupation monsterId="11909"/>

          </JobOccupations>

          <BoardName monsterId="1"/>

          <Industries>

            <Industry>

              <IndustryName monsterId="1"/>

            </Industry>

          </Industries>

          <Video monsterId="123" refCode="video_A">

          </Video>

    </JobPosting>        

Job Duration

The job duration defines how many days an ad will run. When added, it controls the desired duration to attempt to post the job with.  Jobs will require inventory with the appropriate duration or else the job will fail to post, effective March of 2010.

In the job XML, duration is defined as an attribute of the JobPosting element, as shown below:  
 

<JobPostings>

        <JobPosting desiredDuration="60">

Job Category/OccupationTwo tier position Categorizing where JobCategory would be the 1st tier and under it will be JobOccupation as the 2nd.
Example: Sales/Field Sales,International Sales, Telesales... for the full list can be found here: Monster Job Categories

Location

This is the location (region or part of it, down to the post code level) under which the job will be searchable on Monster sites. This will restrict the website on which it will be searcheable.
Example locations: London East, London North West, etc... full available location can be found here: Monster Locations

Job Board

The job board is a container in which your jobs will fall into. It is specified in the BoardName element.

Top

 

<BoardName monsterId="1"/>

For example, Id 1 represents all the Monster sites, excluding Private Label sites (as known as "Co-branded" sites or "Branded Career Sites") that have their own BoardId.

Diversity Job Postings - to post to Diversity, simply specify the Diversity job board in the BoardName element of the job posting. Please contact your Monster Representative to obtain that id.

To post to both Monster and Diversity, two job postings must be provided in the request. This sample can be used as a reference as it shows multiple postings: Multiple_Postings_Sample

Bolding

When added, bolds the job title in seeker job search results, increasing the visibility of the job. Bolding exists as both as an attribute for standard inventory and as an ala carte option. Setting bold to “true” will require available bolding inventory or else the job will fail to post, effective March of 2010.

In the job XML, bolding is defined as a Boolean attribute of the JobPosting element, as shown below: 

<JobPostings>

        <JobPosting desiredDuration="60" bold="true">

Job Refresh

When added, refresh provides the ability to do a manual, “one time” refresh on an active job posting. Inventory is purchased only ala carte. Setting the jobPostingAction to “refresh” will require available refresh inventory or else the job will fail to refresh, effective March of 2010.

In the job XML, Refresh is defined as an enumeration value of the attribute jobPostingAction of the JobPosting element, as shown below:

<JobPosting desiredDuration="60" jobPostingAction="refresh">

Auto-Refresh

When added, auto-refresh provides the ability for a job posting to be moved to the top of the job search results every "auto-refresh interval" days. Valid auto-refresh frequencies are: 7, 14, 30 or 60 days. Auto-refresh inventory exists only as an attribute for standard inventory. Setting the Auto-refresh to “true” will require available auto-refresh inventory for the selected frequency or else the job will fail to refresh, effective March of 2010.

In the job XML, Autorefresh is defined as an element under InventoryPreference element, as shown below:

<JobPosting desiredDuration="60">
   <InventoryPreference>
      <Autorefresh desired="true">
         <Frequency>14</Frequency>
      </Autorefresh>
   </InventoryPreference>

  

Video

When added, Video provides the ability to have a job video that accompanies the job posting. Inventory is purchased only ala carte. Setting Video on a job will require available video inventory or else the job will fail to post, effective March of 2010.

       </Industries>

       <Video monsterId="123" refCode="video_A">

       </Video>

   </JobPosting>
 

CAN (Career Ad Network)

When added, allows one to enhance Monster Job Posting with targeted advertising on the Monster network and its diverse partner websites. Monster’s Career Ad Network will transform a job posting into a dynamic hiring ad and then strategically place that ad where qualified candidates spend their time online. When interested job seekers click on the ad, they’ll be brought to the Monster Job Posting, where they can learn more about the job and easily apply online. Inventory is purchased ala carte for Monster postings only. It is not available on Diversity. Setting CAN on a job will require available CAN inventory or else the job will fail to post.

<JobPosting desiredDuration="60" bold="true" jobPostingAction="refresh">

          <InventoryPreference>

            <CareerAdNetwork desired="true">

              <Duration>14</Duration>

            </CareerAdNetwork>
 

 

Apply Methods

There are 4 separate ways to apply to a job on Monster.

1)    Apply Online

2)    Apply By Email

3)    Offsite Apply, also referred to as Custom Apply

4)    Shared Apply

With Apply Online, the resume is saved on Monster and a copy is emailed to the job contact as set in the posting account’s preferences. This is enabled/disabled with the DisableApplyOnline field. Contact\E-Mail address must be provided in order for the apply button to be displayed on job.

IMPORTANT NOTE: The XML tag ApplyOnlineURL in the job schema can NOT be used for setting up the apply URL. 

With Apply By Email, the resume is NOT saved on Monster and is instead emailed directly to the job contact. This is enabled whenever any visible email address is included on the job. This can be either in the job body or in the Contact\E-mail field (this is not displayed to the job seeker.) This can be disabled by not including an email in the job body, or not including the Contact\E-mail field, or by setting Contact attribute HideEmailAddress to true. Apply By Email can be used in conjunction with Apply Online. Seekers who are not logged into a Monster account will have the option to use this method to apply even if Apply Online is available.

With Offsite Apply, also referred to as Custom Apply, the seeker is redirected to another site that the client provides. Nothing in the apply is saved on Monster, including the resume. To use an Offsite Apply the client must purchase this add on from their Monster account manager. This is either implemented on the client’s account settings (Custom Apply – Company Level) or can be submitted through the CustomApplyOnlineURL field (Custom Apply – Job Level). Job Level custom apply requires inventory. Without the appropriate purchase and inventory, the field will be ignored and not used on the job. 

 

        Here is a sample showing the CustomApplyOnlineURL in the job XML:

    <JobBody><![CDATA[The Job Body needs to contain at least 50 characters to post successfully.]]>
    </JobBody>    
    <AdditionalSearchKeywords><![CDATA[Network Administrator]]>
    </AdditionalSearchKeywords>    
    <StartDate monsterId="1">Immediately</StartDate>
    <YearsOfExperience monsterId="1">No Experience</YearsOfExperience>
    <CustomApplyOnlineURL>http://www.sample_apply_url.com</CustomApplyOnlineURL>
</JobInformation>

 

 

 

Character sets and encoding

XML requests should be posted to BGW encoded in "UTF-8" (Unicode) characters set.

When text includes special characters in XML, including HTML markup characters, (ex. <li>One<li>) the text should be surrounded with the CDATA tag. If text uses XML/ HTML entities (ex. &gt; &lt; &amp;) then the CDATA tag should not be used.

More information about HTML Encoding can be found here: http://en.wikipedia.org/wiki/Character_encodings_in_HTML

Top

Job Processing

The jobAction attribute within Job Tag is used to determine the action your request will trigger.

Adding a new job

Posting a request with jobAction='addOrUpdate' will add a new job, or update a pre-existing one if a job with such a RefCode exists under the referred recruiter account.

An alternative way of posting a new job is by using jobAction="add", but this is not recommended. In the case that the job already exists with this JobRefCode, it will return an error in the XML Response.

Updating a job

Also for Update, same as for the Add action above, it's preferable to use the addOrUpdate jobAction. Using update with non existence of targeted job (JobRefCode) the posting will be rejected and an error will be returned.

Note: after an add or update request is successfully processed, it can be viewed immediately and will be searchable (listed on job-Search sites) in about 1.5 hours.

Deleting a job

There are two ways to delete a job position:

1. Set the job action attribute, in your request (the same XML format as for adding or updating) to delete (<Job... jobAction="delete"...>) including the targeted JobRefCode and RecruiterReference.

2. Post a Delete XML request with RefCode as the job identifier

Monster Delete Schema can be found here: http://schemas.monster.com/Current/XSD/Delete.xsd

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

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

   <SOAP-ENV:Header>

      <mh:MonsterHeader xmlns:mh="http://schemas.monster.com/MonsterHeader">

         <mh:MessageData>

            <mh:MessageId>Company Jobs created on 09/08/2011 02:41:44PM</mh:MessageId>

            <mh:Timestamp>2011-09-08T14:41:44Z</mh:Timestamp>

         </mh:MessageData>

      </mh:MonsterHeader>

      <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">

         <wsse:UsernameToken>

            <wsse:Username>username</wsse:Username>

            <wsse:Password>password</wsse:Password>

         </wsse:UsernameToken>

      </wsse:Security>

   </SOAP-ENV:Header>

   <SOAP-ENV:Body>

      <Monster:Delete xmlns:Monster="http://schemas.monster.com/Monster"
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation="http://schemas.monster.com/Monster

http://schemas.monster.com/Current/xsd/Monster.xsd">

         <Monster:Target>JobPosting</Monster:Target>

         <Monster:DeleteBy>

            <Monster:Criteria>RecruiterName</Monster:Criteria>

            <Monster:Value>username</Monster:Value>

         </Monster:DeleteBy>

         <Monster:DeleteBy>

            <Monster:Criteria>RefCode</Monster:Criteria>

            <Monster:Value>the_refcode</Monster:Value>

         </Monster:DeleteBy>

      </Monster:Delete>

   </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Note: After deleting a job, it will still be searcheable (listed on job-Search sites) for about another 1.5 hours due to the ads indexing schedule. It will, however, be locked for applying and a message will be visible to the job-seeker saying "We're sorry. This job has been removed from the site and is no longer available for viewing".

Job postings Processing

An XML job request can contain multi postings for the same job position.

Each of the posting will be referred by the unique combination of JobCategory/Location/BoardName
Each posting will get a Monster postingId and will consume a posting Inventory from the recruiter account

Adding a new posting

Add a new posting to the request(include the existing posting) with jobaction set to "addOrUpdate" or "Update" and repost it. This will add a new posting under the same position.

Updating a posting

Update the posting info on the request setup jobAction to "addOrUpdate" or "Update" and repost it.

Changing one of the key entities (JobCategory/Location/BoardName) on a posting will cause it to be deleted and to add a new posting, or update the existing posting if this combination key already exist under the position.

Deleting a posting

There are two ways to delete a single posting:

1. Omitting a posting from the job request with jobAction set to "addOrUpdate" or "Update" and reposting it will cause this position to be deleted.

2. Posting a delete XML request with postingId as the posting identifier

Monster Delete Schema can be found here: http://schemas.monster.com/Current/XSD/Delete.xsd

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

   <SOAP-ENV:Header>

      <mh:MonsterHeader xmlns:mh="http://schemas.monster.com/MonsterHeader">

         <mh:MessageData>

            <mh:MessageId>Company Jobs created on 09/08/2011 02:41:44PM</mh:MessageId>

            <mh:Timestamp>2011-09-08T14:41:44Z</mh:Timestamp>

         </mh:MessageData>

         <mh:ProcessingReceiptRequest>

            <mh:Address transportType="http">http</mh:Address>

         </mh:ProcessingReceiptRequest>

      </mh:MonsterHeader>

      <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">

         <wsse:UsernameToken>

            <wsse:Username>username</wsse:Username>

            <wsse:Password>password</wsse:Password>

         </wsse:UsernameToken>

      </wsse:Security>

   </SOAP-ENV:Header>

   <SOAP-ENV:Body>

      <Monster:Delete xmlns:Monster="http://schemas.monster.com/Monster"
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation="http://schemas.monster.com/Monster
http://schemas.monster.com/Current/xsd/Monster.xsd">

         <Monster:Target>JobPosting</Monster:Target>

         <Monster:DeleteBy>

            <Monster:Criteria>RecruiterName</Monster:Criteria>

            <Monster:Value>username</Monster:Value>

         </Monster:DeleteBy>

         <Monster:DeleteBy>

            <Monster:Criteria>PostingId</Monster:Criteria>

            <Monster:Value>the_postingid</Monster:Value>

         </Monster:DeleteBy>

      </Monster:Delete>

   </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

 

For deleting all job postings for a certain job Position see Deleting a job

Test your job XML

During development you can use the Monster WebService Toolkit Web-Service-Tester to verify your XML, post it to the test environment and see the posted job on job-search site.

Viewing the job ad posted to the Monster Test environment:
After posting a successful job using the Toolkit a link (http://jobview.monster.com/getjob.aspx?JobID=123456) will appear in the page linking to the posted job ad.

In order to be able to display the job ad do as follows:
To your hosts file (on windows XP this path is c:\WINDOWS\system32\drivers\etc\hosts) add the following Test entries:

208.71.198.91 jobsearch.monster.com
208.71.198.91 jobview.monster.com

postingId(JobID) - Monster's job posting identifier, will also appear in the HTTPS response (xpath: /SOAP-ENV:Envelope/SOAP-ENV:Body/JobsResponse/JobResponse/JobPostingResponse/@postingId)

Test BGW URL : https://208.71.198.74:8443/bgwBroker

HTTPS response

For each request, the BGW will return an XML response that will contain information about the success or failure of the request.

Common Job Errors and Resolutions can be found here.

Testing in Production

Testing feeds against our test environment should be sufficient since it mirrors the Production environment.

If a Production test is absolutely necessary, please place in the JobBody and JobTitle... "TEST JOB, DO NOT APPLY"
Note: Such a test will consume Job Inventory just as a real posting does.

Top

Deployment

Production BGW URL : https://gateway.monster.com:8443/bgwBroker

Your checklist for deployment:

Do you know the production username/password to post jobs under?
Is your solution updated with that username/password?
Does this user have BGW posting permissions?
Do you have enough Inventory?
Is the inventory of the correct type (for the targeted location)?

All original information, data, concepts and ideas presented in this document are the exclusive confidential and proprietary property of Monster. Intellectual property law, copyright laws and international treaties protect the contents of this document. No part of this document nor any of the information, data, concepts and ideas contained therein, may be reproduced, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the expressed written permission of Monster. Possession of this document does not constitute a transfer of any intellectual property rights or license rights. All trademarks and registered trademarks are the property of their respective holders.

Copyright © 2011 Monster Worldwide.
All rights reserved.