RTP with Apply with Monster

 

Create the XML Request

 

SOAP Envelope

 

Job Duration

 

Job Board

 

Twitter Card Language

 

Social Ads on Twitter

 

DisplayTemplate

 

Bolding

 

Job Refresh

 

Auto-Refresh

 

CAN (Career Ad Network)

 

Apply Methods

 

Testing

 

Deployment

 
 

Real Time Posting

Getting Started

With Real Time Posting (RTP), job ads can be published, edited and deleted via Monster's Business Gateway (BGW) in near real time.

Here is an overview of the steps for implementing your RTP integration:

  1. Decide which Job Posting Features to utilize.  We recommend taking advantage of Apply with Monster (AwM) in conjunction with RTP to achieve the best candidate response; when utilizing Apply with Monster, do the Apply with Monster integration first.
  2. Create the XML job posting.   Samples are also provided with Monster's web services toolkit. NOTE that the toolkit cannot be used to test the posting part because it doesn’t point to the correct environment for testing Real Time Posting. The jobs need to be sent via HTTP POST using your application or a third party app.
  3. Validate the XML using the toolkit.
  4. Test posting a job from your application.
  5. If using Apply with Monster, apply to a test job and confirm receipt of candidate information.
  6. When testing is completed, transition to production using the steps outlined in the "Deployment" section of this guide.

Job Posting Features

Monster jobs include enhancement features to help an employer's job stand out from others, and/or target the best candidates.  Highlights of key features that will differentiate your integration and offer value to employers include: 

Supported Boards Clients can post to the following boards based on their available purchased inventory and their desired distribution and targeting.

  • Monster Board - Jobs posted to Monster's core job sites, our mobile app, our BeKnown professional networking app on Facebook, our affiliate websites including Military.com and Jobs.com, and over 1,000 newspaper partner co-branded websites.
  • Career Ad Network Direct - Syndicates jobs to a network of thousands of sites, targeted to attract the right seekers. When job seekers click on the ad, they'll learn more about the job and apply online. Learn more
  • Diversity Board - Distributes jobs to Monster's exclusive network of sites targeting diverse candidates. Learn more
  • Veterans - Find and hire the best military talent with the largest military-focused destination site and network. Learn more
Inventory Types / Add-On Inventory Clients may add additional job visibility in job search results.  
  • Bolding - Increases the visibility of the posting with a bolded posting in the search results.
  • Refresh - Moves the posting to the top after a pre-determined interval with manual updates.
  • Auto-Refresh - Moves the posting to the top automatically after a pre-determined interval.
  • Social Ads on Twitter - Creates a targeted Job Ad campaign on Twitter appearing in a Twitter user’s timeline.

Tip!

Use the job inventory query to get a snapshot of available inventory for a user. Learn more 


RTP with Apply with Monster
  Jobs posted to Monster can be enabled to take advantage of Apply with Monster's integrated resume delivery capability and streamlined apply experience.  Find out how.


   
Integrated delivery of Recommended Resumes
When jobs are posted to Monster via RTP, they can be enabled to specify the integrated delivery of Recommended Resumes.  Find out how.

Create the XML Request

BGW requests 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. SOAP messages are sent via HTTPS.

Sample Job in Monster XML Format (Click to Expand XML Code)

Information about Job Fields (Click to Expand)  


SOAP Envelope
The envelope is a container for a SOAP message. (Click to Expand)  


SOAP Header
The header contains information about the request, request protocol, and a security protocol with the user credentials. (Click to Expand)  


SOAP Envelope Job
The Body contains all the data related to the job you're posting and should comply with Monster job schema.
  • 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...) (Click to Expand)  


Job Information
This contains the main information that will be displayed in the job ad. Example: job title, job description (jobBody), salary , contact, etc. (Click to Expand)  


Job Posting
This section sets where the job posting will be searchable, identified by the combination of JobCategory, JobOccupation, Location and BoardName. Inventory preferences, industries, video, etc can be set in this section as well. (Click to Expand)  


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.

Monster’s current job posting solutions offer these durations: 14, 30, 60, 90, 180 & 365 days. The most commonly purchased job solutions contain 14, 30 or 60 day job ads.

(Click to Expand)  

Job Posting Inventory

Decrements to Job Posting Inventory

  • Job Posting Inventory is decremented based on the number of Job Postings within a submission. A Job Posting consists of a single location and category. If multiple locations or categories are added, the job inventory will be decremented based on the number of locations/categories requested.
  • For new jobs, each Job Posting within the Job will cause the inventory to be decremented.
  • For updated jobs, each new/additional Job Posting will cause the inventory to be decremented.
  • Modification to the location of the job outside of the current Country it is posted to will cause the inventory to be decremented.
  • The Job Reference Code is a unique job identifier. Any modifications to the jobRefCode field will be interpreted as the creation of a new job and all Job Posting within that Job will decrement the job posting package. However – the original job will not be expired automatically.

Location
This is the location (region or part of it, down to the postal code level) under which the job will be searchable on Monster sites. This will restrict the website on which it will be searchable. 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. (Click to Expand)  


Twitter Card Language
When added, the channel tag lets the system know which language to use on the Twitter Card.

In the job XML, the channel tag is added after the RecruiterReference and before the JobInformation block. If this tag is omitted, the card will be tweeted in US English by default. The example below will cause the card to be tweeted in Canadian French. A list of country channels can be found by clicking this link: http://integrations.monster.com/Toolkit/Enumeration/CoreMonsterChannels. Select Core Monster Channels to find the country and language ChannelID.
  <RecruiterReference>
    <UserName>xrtpjobsx01<UserName>
  </RecruiterReference>
  <Channel monsterId="14"> 
</JobInformation>
 




Social Ads on Twitter
When added, creates a targeted Job Ad campaign on Twitter appearing in a Twitter user’s timeline.

In the job XML
  <JobPosting>
    <InventoryPreference>
      ...
      <SocialAdTwitter desired="true"/> 

 


DisplayTemplate
The DisplayTemplate defines which job template is used to used to format the posting ad. Id value of 1 is for the standard job posting template offered by Monster. Other Id values are for customized job posting templates. (Click to Expand)  


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.

In the job XML, bolding is defined as a Boolean attribute of the JobPosting element, as shown below: (Click to Expand)  


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.

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


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. (Click to Expand)  


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, Setting Video on a job will require available video inventory or else the job will fail to post. (Click to Expand)  


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. (Click to Expand)  


Apply Methods
If you utilize Monster's candidate management capability, then by specifying 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 the default apply method, and is disabled via the DisableApplyOnline field. Contact\E-Mail address must be provided in order for the apply button to be displayed on a job.

If candidates are managed within your own applicant tracking system, an integrated apply solution can be used to specify delivery of an applicant's resume, cover letter and profile information to your platform. To enable this integration, an element containing Apply with Monster configuration parameters is specified. If your apply process requires the completion of additional interview questions in addition to the collection of the candidate's resume, the seeker can be redirected to the site specified by OnContinueURL.

If circumstances prevent an integrated solution, a basic applicant redirect is available specified by the CustomApplyOnlineURL field.

Important! If not using Apply Online, it is critical that proper source attribution is specified such that the candidate source is identified as originating from Monster.

In some cases, an email address or apply link in the job body may be copied and used as the target for the apply button.

The XML tag ApplyOnlineURL is used for outbound exports and is not relevant for setting up the apply URL.

Example ApplyWithMonster element within the RTP job XML: (Click to Expand)  


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

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
Posting a request with jobAction="addOrUpdate" will update a pre-existing job with such a jobRefCode under the referred recruiter account.

An alternative way of updating a job posting is by using jobAction="update", but this is not recommended. In the case that a job does not already exist with this jobRefCode, it will return an error in the XML Response.

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
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
(Click to Expand)  


Job postings Processing
An XML job request can contain multiple postings for the same job position.

Each of the posting will be referred by the unique combination of 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 (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
(Click to Expand)  


Testing


  • A Webservices Toolkit, http://integrations.monster.com/Toolkit, is available ONLY to validate the XML. It is recommended that this be done in the early stages of development until valid Monster XML can be created on a consistent basis.
  • The toolkit cannot be used to post jobs on a client's account. Clients need to use their application or a 3rd party tool like the Fiddler or Advanced REST Client (ARC) in Chrome.
  • Once XML is valid, test posting a job directly to Monster's Business Gateway (BGW) URL https://gateway.monster.com:8443/bgwBroker.
  • Monster's BGW uses port 8443; this is not an industry standard port so in some cases it needs to be configured in your firewall. If issues are encountered, be advised that it is not necessary for clients to use port 8443 to exit their systems.
  • Test account that can be used to post directly to BGW is username: xrtpjobsx01 password: rtp987654

Test the following activities as part of Real Time Posting (RTP):
  1. Create the job XML with the job board set to the Monster demo job board (monsterId = 178).
  2. POST the job XML to https://gateway.monster.com:8443/bgwBroker. NOTE that the toolkit cannot be used to test the posting part because it doesn’t point to the correct environment for testing Real Time Posting. The jobs need to be sent via HTTP POST using your application or a 3rd party tool like the Fiddler or Advanced REST Client (ARC) in Chrome.
  3. Receive and view the response.
  4. Be able to parse the XML response and provide feedback to users on job posting status (success or failure).
  5. Ensure there's a process in place to fix and resubmit job postings.
  6. View the job posting and make adjustments in the XML request as necessary.
  7. Jobs on the demo board can be viewed by using http://jobview.monster.com/getjob.aspx?JobID=xxxxxxxxx. Where xxxxxxxxx is the postingId in the XML response.
  8. View the job search results (job board 178 only) and make adjustments as necessary. This can be done by going to http://jobsearch.demo.monster.com. Note that job search indexing is typically done within 90 minutes.
  9. Apply to a job using Apply With Monster
    a. Confirm Apply button is visible on job posting
    b. Apply to a job. 
    c. Confirm receipt of job seeker resume and cover letter
  10. Repeat steps above and post jobs to the Diversity, CAN and VETERANS demo job boards.
  11. Note that viewing jobs is not applicable for the Diversity, CAN and VETERANS job boards.
  12. Perform an inventory query. Parse the results and provide inventory level information to users.

Take Note!

Different job boards are used for integration testing and Monster's production job boards. Be sure that the appropriate job boards are used for the intended destination.



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.

Deployment


1. Ensure the correct job boards are being used. The job board Id's are located in the Job Board section of this guide.
2. Have your customers contact their Monster Representative for the following:
    a. Request their Real Time Posting credentials or update their existing account to support Real Time job Posting.
    c. Check their current job posting inventory types, durations, levels and purchase additional inventory if needed.
3. Contact the partnership team for other marketing ideas to drive client adoption - partner@monster.com
4. Send your name, title, email, phone to be added to the communications list for future updates, important changes, new and opportunities to partner@monster.com

Frequently Asked Questions



Where can I find a sample XML file?

Sample files can be found in the webservice toolkit at: http://integrations.monster.com/Toolkit

Where are Monster schemas, Web Service and WSDL's located?

Business Gateway schemas can be found at: http://schemas.monster.com/current/xsd
The Web Service can be found at: https://gateway.monster.com:8443/bgwBroker
The WSDL’s can be found at: http://schemas.monster.com/current/wsdl

How soon before a job posting can be found in job search results?

Typically within 90 minutes.

How soon before a job posting can be viewed?

Immediately if you go to the following web address http://jobview.monster.com/getjob.asp?jobid=xxxxx where xxxxx=postingId returned in XML response.

Where can I find a list of valid Monster locations and other enumerations?

This information can be found at http://integrations.monster.com/Toolkit/LocationEnumeration. For other enumerations select other items from the Enumerations dropdown list in the tool. For enumeration in the schema definitions, go here: http://schemas.monster.com/Current/XSD/Enumerations.xsd

Can I send a Real Time Posting in HTTP?

No. It must be in HTTPs.

Can I post to multiple job boards?

Yes. You have access to post to any boards associated with your company. The boards have restrictions and some function differently. Contact your Customer Service Representative for additional information.

Do I have to send a job posting in Monster's standard XML format?

Yes.

Does the encoding of XML matter?

The encoding of the XML has to match the characters in the text fields otherwise the job will not be displayed properly.

What text must be included in CDATA sections?

Any text that includes invalid XML characters without HTML encoding.

What text should not be included in CDATA sections?

Any HTML encoded text.

How do I take down a job posting?

There are two ways to do this: 1) Enter a delete request through the Business Gateway. 2) If there are multiple postings within a job, leave out the posting you want to take down. Note that "Job Posting Action = Delete" does not work!

Why is the username and password in the wsse: Security header as opposed to the Monster header?

This is because the username and password elements are not in the same namespace. They use the namespace - http://schemas.xmlsoap.org/ws/2002/04/secext

What do I need to do in order to get the recruiter contact information to show up in a job posting?

Place the job contact information within the Contact element, which is located under the Job Information element. See the following example: http://integrations.monster.com/Toolkit/RealtimePosting/Sample/Add_Or_Update_Job/Advanced_Fields. The type details can be found at: http://schemas.monster.com/current/xsd/job.xsd. Once at this url, search for "HideableContactType". This is an extension of ContactType.

How to post to more than one Location/Category/Job Board?

You need to have multiple JobPosting sections. See http://integrations.monster.com/Toolkit/RealtimePosting/Sample/Add_Or_Update_Job/Multiple_Postings for an example ofthis.

Is there an option to post multiple jobs in one file?