Overview

Key Definitions

Development

Input Parameters

Required Parameters

Optional Parameters

Appendix - Monster Country ID List

Testing your integration

Cloud Search Guide

 

Overview

Monster Cloud Resume Search allows clients to use Monster web services to call into Monster to search job seeker resumes. This type of interface allows clients to search a copy of their Jobseeker resumes that have been uploaded to their private resume database hosted by Monster.
 

Key Definitions

MITE - Monster Integrated Test Environment

XML - Extensible Markup Language

CAT - Company Access Ticket

BGW - Business Gateway

PRDB- Private Resume DataBase Search

PRDBX - Power Resume Database External Search

EEO - Equal Employment Opportunity

OFCCP -Office of Federal Contract Compliance Programsbr />
 

Integrated Private Resume Board Search Flowchart

Here is a flowchart of the steps and calls that take place between Monster and client system.

(Click to Integrated Private Resume Board Search Flowchart)
Private Resume Search

Monster and Client Responsibilities:

  • Monster will provide client with a Monster Integration Test Environment (MITE) test account and a CAT to be used for integration testing.
  • Client is responsible for developing and making all system calls to Monster in order to successfully implement Integrated private resume board search.
  • Client is responsible for testing their implementation.
  • Client is responsible for all EEO and OFCCP recordkeeping, reporting and processes that may be required pursuant to their use of Monster's resume database. EEO letters cannot be generated through the Integrated private resume search. The assumption is that the partner's system, which is integrated with Monster, becomes the end customer's system of record and all EEO / OFCCP data should be stored on the client system. Additionally, since the sourced resume is not stored on Monster in association with the customer, Monster has no provision to record the relevant EEO / OFCCP snapshot data for that interaction.
 

Key points to be aware of during development

  • A CAT is an encoded token, representing a user, that is used for authentication within a request to Monster web services.
  • Resume query results provide a resume preview which is used to determine whether to download a seeker's complete resume.
 

Development

CLIENT creates and invokes resume search query (request)

Resume search is done through HTTP GET. Monster PRDBX search parameters detailed below contain the specifications for developing a resume query using PRDBX.

A sample request for resume search is shown below and is also located at this location: http://integrations.monster.com/MonsterWebServiceToolKit/RealtimePosting/Sample/Inventory_Query/Resume_Search_All
 

XML Inventory Query Request

Here is an example XML Inventory Query Request:message.

(Click to XML Inventory Query Request)

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header">
<mh:MonsterData>
< mh:MessageId ">resume transaction inventory</ mh:MessageId>
< mh:Timestamp ">2011-07-31T07:00:02Z</ mh:Timestamp>>
</mh:MonsterData>
</mh:MonsterHeader>
<cat:CompanyAuthHeader xmlns:cat="http://webservices.monster.com/MonsterPortal">
<cat:CompanyAccessTicket>1:EASAMPLE_CATAQNK19Zi8kdxE_7.2LP2sn7DLgd_JOKfxI4ATbFPZUNtvHo-</cat:CompanyAccessTicket>
</cat:CompanyAuthHeader>
</SOAP-ENV:Header>
</SOAP-ENV:Body>
<InventoriesQuery xmlns:cat="http://schemas.monster.com/Monster xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<LicenseFilter monsterId="3">All </LicenseFilter>
<LicenseType monsterId="4">ResumeTransaction </LicenseType>
</InventoriesQuery>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


 

Monster provides Inventory Query response

A response to the inventory query is provided in Monster's standard XML format. The response includes information such as the types of licenses available, the quantity of inventory for each type of license, the locations of the resume view inventory, etc. This information should be presented to the user such that they know their available inventory.

(Click to XML Inventory Query response)
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header">
<MonsterHeader xmlns="http://schemas.monster.com/MonsterHeader/">
<ChannelId xmlns=""http://schemas.monster.com/MonsterHeader/">58 </ChannelId>
<MonsterData>
< MessageId >1818545626775038223296_qax4bgwweb201</ MessageId>
< Timestamp>2011-08-02T14:43:54.452-05:00</ Timestamp>
<RefToMessageId xmlns="http://schemas.monster.com/MonsterHeader/"> </RefToMessageId>
</MessageData>
</MonsterHeader>
</SOAP-ENV:Header>
</SOAP-ENV:Body>
<InventoriesQuery xmlns:cat="http://schemas.monster.com/Monster xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
</Inventories>
</Inventories>
<Inventory monsterId="99869046">
<ResourceLicenseInfo>
<ResourceAclID monsterId="353">6Sense_Resume_Transactions </ResourceAclID>
<ResourceLicenseTypeID monsterId="4">Transaction limited </ResourceLicenseTypeID>
</ResourceLicenseInfo>
<Quantity>
< TotalPurchased>10000</ TotalPurchased>
< TotalAvailable>9998</ TotalAvailable>
</Quantity>
<InventoryDates>
< InventoryActiveDate>10000</ InventoryActiveDate>
< InventoryExpireDate>9998</ InventoryExpireDate>
</InventoryDates>
<InventoryAttrs>
<AttrTypeId monsterId="47">ChannelID </ChannelID>
<Numeric1>
< Value>5555</ Value>
</Numeric1>
</AttrValue>
</InventoryAttr>
<InventoryAttr>
<AttrTypeId monsterId="14">LicenseProvisionMethod </AttrTypeId>
<AttrValue>
<Numeric1>
< Value>1</ Value>
</Numeric1>
< Value>0</ Value>
</Numeric2>
</AttrValue>
</InventoryAttr>
</InventoryAttrs>
</Inventory>
</Inventories>
</InventoriesQueryResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

 

Sample XML Resume Response

A response to the inventory query is provided in Monster's standard XML format. The response includes information such as the types of licenses available, the quantity of inventory for each type of license, the locations of the resume view inventory, etc. This information should be presented to the user such that they know their available inventory.

(Click to XML Inventory Query response)
<Monster>
<Resume Found ="1000" Returned ="1" Status ="0">
<Resume SID ="asamplea3ttuj">
<Relevance>0.910687</Relevance>
<ResumeTitle>Java / Software Developer</ResumeTitle>
<DateModified Date="2010-12-14T20:13:00">
<DateCreated Date="2011-05-08T11:54:13">
<TotalYearsExperience>15.6</TotalYearsExperience>
<EducationLevel/>
<CareerLevel/>
<Boards>
<Board ID="1">Monster </ResourceAclID>
</Boards>
</Icons>
<PersonalData>
< Confidential>0</ Confidential>
< Name>
< First>Janey<</ First>
<Middle/>
< Last>Smithson</ Last>
</Name>
<Address>
<Country>US</ Country>
<State>CA</State>
<City>Smith City</</City>
<Location>US-CA-smithCity<</Location>
<PostalCode>99888<</PostalCode>
</Address>
<MilitaryExperience>
<ServiceFlag>99888</ServiceFlag>
<MilitaryInvolvement>0</MilitaryInvolvement>
</MilitaryExperience>
</PersonalData>
<Target>
<JobTitle/>
<Relocation ID="1">Will Relocate</ </Relocation>
<Salary>
<Min/>
<Max>CA</Max>
<Type ID="1">yr</ </Type>
<Currency ID="1">USD</Currency>
</Salary>
<JobTypes>
<JobType ID="5">Part Time</JobType>
<JobType ID="2">Temporary/Contract/Project</JobType>
<JobType ID="1">Employee</JobType>
<JobType ID="4">Full Time</JobType>
</JobTypes>
</Target>
<Experiences>
<Experience>
<Matches>
<Label Group="5" Criteria="Engineer">Engineer</JobType>
<Label Group="5" Criteria="Engineer">Engineer</JobType>
</Matches>
<Company>
<Name>UtmostCorporation</Name>
<Job>
<Title JellyDot="true">Software Engineer </Title>
<CareerLevel/>
</Job>
<DateFrom Year="2005" Month="4"/>
<DateFrom Year="2300" Month="3"/>
<Years>6.0</Years>
</Experience>
</Experience>
<Experience>
<Matches>
<Label Group="5" Criteria="Engineer">Engineer</label>
<Label Group="5" Criteria="Engineer">Engineer</Label>
</Matches>
<Company>
<Name>BestSoftware</Name>
<Job>
<Title JellyDot="true">Software Engineer </Title>
<CareerLevel/>
</Job>
<DateFrom Year="2002" Month="4"/>
<DateFrom Year="2005" Month="4"/>
<Years>2.9</Years>
</Experience>
</Experience>
<Experience>
<Matches>
<Label Group="5" Criteria="Engineer">Engineer</JobType>
<Label Group="5" Criteria="Engineer">Engineer</JobType>
</Matches>
<Company>
<Name>PerfectSystems</Name>
<Job>
<Title JellyDot="true">Software Engineer </Title>
<CareerLevel/>
</Job>
<DateFrom Year="1996" Month="1"/>
<DateFrom Year="2000" Month="6"/>
<Years>4.5</Years>
</Experience>
</Experience>
<Experience>
<Matches>
<Label Group="5" Criteria="Engineer">Engineer</JobType>
<Label Group="5" Criteria="Engineer">Engineer</JobType>
</Matches>
<Skills>
<Skill>
<Matches/>
<Name>Unix Operating Systems</Name>
<LastUsed>2000-06-30T23:00:00</LastUsed>
<YrsUsed>4.5</YrsUsed>
</Skill>
<Skill>
<Matches/>
<Name>C++ Programming Language</</Name>
<LastUsed>2000-06-30T23:00:00</LastUsed>
<YrsUsed>4.5</YrsUsed>
</Skill>
<Skill>
<Matches/>
<Name>Test Design</</</Name>
<LastUsed>2000-06-30T23:00:00</LastUsed>
<YrsUsed>4.5</YrsUsed>
</Skill>
<Skill>
<Matches/>
<Name>Unix Operating System</</</Name>
<LastUsed>2000-06-30T23:00:00</LastUsed>
<YrsUsed>6.2</YrsUsed>
</Skill>
</Skills>
<Skills>
<Skill>
<Matches>
<Label Group="Name" Criteria="java">Java</label>
<Matches/>
<Name JellyDot="true">Enterprise JavaBeans</Name>
<LastUsed>2000-06-30T23:00:00</LastUsed>
<YrsUsed>8.2</YrsUsed>
<Matches>
<Label Group="Name" Criteria="java">Java</label>
<Matches/>
<Name JellyDot="true">JavaServer Pages</Name>
<LastUsed>2000-06-30T23:00:00</LastUsed>
<YrsUsed>13.2</YrsUsed>
<Matches>
<Label Group="Name" Criteria="java">Java</label>
<Matches/>
<Name JellyDot="true">Component Frameworks</Name>
<LastUsed>2000-06-30T23:00:00</LastUsed>
<YrsUsed>2.4</YrsUsed>
<Matches>
<Label Group="Name" Criteria="java">Java</label>
<Matches/>
<Name JellyDot="true">Java Servlets</Name>
<LastUsed>2000-06-30T23:00:00</LastUsed>
<YrsUsed>11.2</YrsUsed>
</Skill>
<Skill>
<WorkAuths>
<WorkAuth>
<Country ID="164">US</Country>
<AuthType ID="1">Authorized</AuthType>
</WorkAuth>
</WorkAuths>
<GlobalSecurityClearances/>
<VeteranStatus>0</VeteranStatus>
<LegalStatuses/>
</Resume>
</Resumes>
</Monster>

 
<mh:MonsterHeader xmlns:mh "http://schemas.monster.com/MonsterHeader"">
<From>
<PartyId partyType = "organization"> <PartyId >
</From>
<ChannelId>58</ChannelId>
<To>
<PartyId partyType = "organization">237431<PartyId >
</To>
< MessageData">
< MessageId "> id1229006779008_QA3BGWWEB201 < MessageId "/>
< Timestamp "> 2009-09-09T14:41:44Z </Timestamp>
< RefToMessageId "> 90805_090855AM_90805_090855AM </RefToMessageId>
< MessageData">
< / MonsterHeader ">
< SOAP-ENV:Header ">
<SOAP-ENV:Body xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<QueriesResponse xmlns="http://schemas.monster.com/Monster">
< / ProcessingReceipt> ">
<JobSeekers xmlnsENV="http://schemas.monster.com/Monster">
<JobSeeker seekerId="11111111/"> seekerScope= "normal"status="active"xmlns="http://schemas.monster.com/Monster">
<Channel alias = "CHAN monsterId="1111""> </Channel >
<PersonalData>
<Contact>
<StructuredName>
<GivenName> test First Name/<GivenName>
<MiddleName/>
<FamilyName> test First Name/<FamilyName>
</StructuredName>
<Address>
<StreetAddress> test Home Address/<StreetAddress>
<StreetAddress2> test Home Address/<StreetAddress2>
<City> Praha/<City>
<State> PRAG</State>
<CountryCode> CZ</CountryCode>
<PostalCode> 1411</PostalCode>
</Address>
<Phones>
<Phone phoneType = "work" priority="primary">0123456789 </Phone >
<Phone phoneType = "mobile" priority="secondary">987654321 </Phone >
</Phones>
<E-mail>test_email@monster.com</E-mail>
</Contact>
</PersonalData>
<Account>
<Confidential>0</Confidential>
</Account>
<Profile>
<CareerLevel monsterId ="12">Experienced (Non-Manager) </Channel />
<Availability>
<AvailableTimeStart monsterId ="1">Immediately </AvailableTimeStart />
</Availability>
<ContactPreference monsterId ="0">
<TotalYearsWorkExperience monsterId ="6">10+ to 15 Years </TotalYearsWorkExperience />
<HighestEducationDegree monsterId ="6">Master's Degree </HighestEducationDegree />
<TargetJobTitle>
<Title>MPS</Title>
<OccupationalClassification occupationId ="101521">
</TargetJobTitle>
</Profile>


<Resumes>
<Resume textResumeId ="ababababababab">
<BoardName monsterId ="1">Monster </BoardName />
<ResumeTitle>Monster test resume title</ResumeTitle>
<ResumeModDate>2008-12-11T09:46:00-05:00</ResumeModDate>
<ResumeCreateDate>2008-12-11T09:41:00-05:00</ResumeCreateDate>
<DetailedSearchExtras>
<WillingToRelocate>true</WillingToRelocate>
<JobStatus monsterId="4">Full Time</JobStatus>
<JobType monsterId="1">WantsPermanent<</JobType>
<JobType monsterId="2">WantsContract<</JobType>
<JobType monsterId="4">WantsTemp</JobType>
<GeographicPrefs>
<GeographicPref>
<CountryCode>France</CountryCode>
<Continent>EU</Continent>
</GeographicPref>
<GeographicPrefs>
<CountryCode>US</CountryCode>
<Continent>NA</Continent>
</GeographicPref>
<GeographicPrefs>
</DetailedSearchExtras>
<WorkAuthorizations>
<WorkAuthorization>
<AuthStatus monsterId="1">I am authorized to work in this country for any employer.</AuthStatus>
<CountryCode>France</CountryCode>
</WorkAuthorization>
<WorkAuthorization>
<AuthStatus monsterId="1">I am authorized to work in this country for any employer.</AuthStatus>
<CountryCode>US</CountryCode>
</WorkAuthorization>
</WorkAuthorization>
<DesiredCompensation>
<CompensationType monsterId="1">Per Year</CompensationType>
<Currency monsterId="1">USD</Currency>
<Rate>60000</Rate>
</DesiredCompensation>
<DesiredEmployer>
<TargetEmployerCategories>
<TargetEmployerCategory monsterId="660">IT/Software Development</TargetEmployerCategory>
</TargetEmployerCategories>
<TargetEmployerOccupations>
<TargetEmployerOccupation categoryId="660"monsterId="11754">
<Name>Computer/Network Security </Name>
</TargetEmployerOccupation>

 
<TargetEmployerOccupation categoryId="660"monsterId="11787">
<Name>Enterprise Software Implementation & Consulting</Name>
</TargetEmployerOccupation>

 
<TargetEmployerOccupation categoryId="660"monsterId="11969">
<Name>Software/System Architecture</Name>
</TargetEmployerOccupation>

 
</TargetEmployerOccupation>
</TargetEmployerOccupations>
<TargetJobIndustries>
<Industry>
<IndustryName monsterId="8">Biotechnology/Pharmaceuticals</IndustryName>
</Industry>
<Industry>
<IndustryName monsterId="29">Advertising and PR Services</IndustryName>
</Industry>
<Industry>
<IndustryName monsterId="30">Architectural and Design Services</IndustryName>
</Industry>
</TargetJobIndustries>
</DesiredEmployer>
<TargetJobTitles>
<TargetJobTitlestype="desired">
<Title>test Job Title1</Title>
</TargetJobTitle>
<TargetJobTitles type="alternate">
<Title>test Job Title 2</Title>
</TargetJobTitle>
</TargetJobTitles>
<EmploymentHistory>
<Position monsterId="280889215">
<EmployerName>test Most Recent Job Title</EmployerName>
<PositionTitle>test Most Recent Job Title</PositionTitle>
<EmploymentLocation>,</EmploymentLocation>
<IndustryName monsterId="0">All</IndustryName>
</ExperienceIndustry>
</Position>
</EmploymentHistory>
<WorkPreferences>
<Weekend monsterId="0">No</IndustryName>
<Overtime>false</Overtime>
</WorkPreferences>
<TextResume>Resume Test Body</TextResume>
<Weekend monsterId="4"/>
<Channel alias="CHAN" monsterId="4425">CHANNEL</CHANNEL>
</Resume>
</Resumes>

<CustomQuestions customQuestionId="1144" displaySequence="1" >
<CQInternalPromptText>P/L Experience</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1145" displaySequence="2" >
<CQInternalPromptText>Largest Budget Managed</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1146" displaySequence="3" >
<CQInternalPromptText># of People Managed</CQInternalPromptText>
<CustomQuestions customQuestionId="1147" displaySequence="4" >
<CQInternalPromptText>Turn-Around Experience</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1148" displaySequence="5" >
<CQInternalPromptText>Turn-Around ExperienceAccomplishments</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1149" displaySequence="6" >
<CQInternalPromptText>IPO Experience</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1150" displaySequence="7" >
<CQInternalPromptText>IPO Experience Accomplishments</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1151" displaySequence="8" >
<CQInternalPromptText>Start-up Experience</CQInternalPromptText>
</CustomQuestion>
</CustomQuestion>
<CustomQuestions customQuestionId="1152" displaySequence="9" >
<CQInternalPromptText>Start-up Experience Accomplishments</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1153" displaySequence="10" >
<CQInternalPromptText>Mergers & Acquisitions</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1154" displaySequence="11" >
<CQInternalPromptText>Mergers & Acquisitions</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1155" displaySequence="12" >
<CQInternalPromptText>Entrepreneurial Experience</CQInternalPromptText>
</CustomQuestion>
<CustomQuestions customQuestionId="1156" displaySequence="13" >
<CQInternalPromptText>Entrepreneurial Experience Accomplishments</CQInternalPromptText>
</CustomQuestion>
</CustomQuestions>
</JobSeeker>
</JobSeekers>
</QueriesResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

 

Monster PRDBX Parameters

Parameter Licenses
If a search term is suffixed with an asterisk (*) then it requires an access license. Please contact your Monster resource to have the license enabled.
 

Input Parameters

Parameter Format

All input parameters should be sent using HTTP GET. Care should be taken to URL-encode all parameters correctly. Malformed parameters will be misinterpreted and may give rise to unexpected results or an error For example:

0xA0002000 - Invalid Input Parameter error

Parameters listed as "multi-valued" accept multiple values and may be internally delimited as follows (subject to URL encoding):
Delimiter Meaning
, Restrict the search to jobs containing one or more of the supplied values
Search URL Encoding Instructions

Encoding standard for all parameters is: UE(UE(val1),UE(val2),UE(val3))
Encoding standard for all parameters with importance (required (req)/nice to have (nth)) specified: UE(UE(val1),UE(val2) req,UE(val3) nth)
Special cases still follow the general rule:
  • Single value (e.g. candidate name): UE(UE(val))
  • IDs, Booleans, other values which do not require encoding: UE(UE(id1),UE(id2),UE(id3)) = UE(id1,id2,id3)
 

Required Parameters

ver (Version number)
The ver parameter is required for PRDBX and specifies the version of the Monster Resume Search service that you are accessing. The following are the valid versions:
Value Description
1.0 2.0
The following is an example call to access version 2.0 of Power Resume Search : http://prdbx.monster.com/query.ashx?q=test&ver=2.0&cat=…

If the version is excluded the following error XML will be returned:

<Monster>
<Errror>
<Error Number="0xA0000999">
<Message>Invalid version specified</Message>
</Errors>
</Monster>

cat (Company Access Ticket)

The cat parameter which is required for PRDBX should be populated with the Company Access Ticket received from Monster.
For example:
http/prdbx.monster.com/query.ashx?q=test&ver=2.0&cat=[your cat]

Your Company Access Ticket (CAT) is case-sensitive and should be supplied in its entirety.
It is valid only under the terms and conditions of your contract with Monster. Restrictions may include, but are not limited to, IP address, date range and access to specific search functionality.

TIP: If you supply an invalid CAT to the Search Service, you will receive one of the CAT errors described in the Errors section of this document.

rb (Resume Board)

The rb parameter is a multi-valued parameter which restricts the search to resumes in the specified boards. The value(s) are IDs and may only be a subset of the resume boards to which the recruiter has access.

For example:
rb=1%2C6143 (%2C is a url-encoded comma.)
 

Optional Parameters

q (Keyword query)

The q parameter restricts the search to resumes containing the supplied list of keywords.

TIP: Use double-quotes (ASCII 22) to surround keyword phrases. A keyword phrase matches resumes only where the words appear in the same contiguous order in the resume.

clvid (career level ID)

The clvid parameter allows a recruiter to search for seekers based on the Career Level ID.

The possible values are as follows:
Career Level ID Meaning
1 President
2 Executive Level
3 General Manager
4 Vice President
5 Director
6 Head
7 Manager
8 Lead
9 Other
10 Analyst
11 Representative
12 Specialist
13 Clerk
14 Coordinator
15 Assistant
For example:
clvid=1

cname (Candidate name)

The cname parameter allows a recruiter to search for seekers based on the candidate's name.

For example:
cname=candidate_name (subject to url-encoding.)

jt (Job title)

The jt parameter allows a recruiter to search for seekers based on the job title. Several titles may be used in the search by submitting a comma-delimited list. For example:
jt= programmer%2Cdeveloper (%2C is a url-encoded comma.)

comp (Company name)

The comp parameter allows a recruiter to search for seekers based on the most recent company that they were employed with.
For example: comp=Monster%2bWorldwide (%2b is space url-encoded twice.)

sk (Skill)

The sk parameter allows a recruiter to search for seekers based on the job skill description. Several skill descriptions may be used in the search by submitting a comma-delimited list. This parameter allows specification of criterion requirement level (nice to have/ required).
For example: sk=c%252b%252b+req%2cjava%2bbeans+nth ( url-encoding explained: UE(UE(c++) req,UE(java beans) nth) )

sch (School name)

The sch parameter allows a recruiter to search for seekers that have attended a specific school. Several school names may be used in the search by submitting a comma-delimited list.
For example: sch= Harvard%2CYale (%2C is a url-encoded comma.)

page (Page number)

The page parameter indicates which page of results to return. The default is 1, which will return the first page of results.

pagesize (Size of result pages)

The pagesize parameter indicates the maximum number of results to return per query. The default is 20, which will return 20 records at a time.

mdatemaxage (Modified date maximum age)
The mdatemaxage parameter restricts the search to resumes that have been modified or reactivated within the specified number of minutes.

TIP: Use 1440 for one day, 10080 for one week, 525600 for one year etc.

mdateminage (Modified date minimum age)

The mdateminage parameter restricts the search to resumes that have been modified or reactivated from the specified number of minutes.
TIP: Use 1440 for one day, 10080 for one week, 525600 for one year etc.

minedulvid (Minimum Education Level ID)

The minedulvid parameter restricts the search to resumes that contain the supplied list of education levels.
Possible values include: http://integrations.monster.com/Toolkit/Enumeration/EducationLevel

rv (ResumeValue)

The rv parameter is a multi-valued parameter that restricts the search to resumes with one or more of the supplied list of ResumeValues.

tjtid (Target Job Type ID)

The tjtid parameter, restricts the search to resumes with owners who have expressed an interest in working in a specified type of position. The possible values are as follows:
Target Job Type ID Meaning
1 Permanent
2 Contract
3 Intern
4 Temp
5 Seasonal
6 FullTime
7 PartTime
8 Statutaire
9 PerDiem

relo (Relocate)

The relo parameter has the following possible values and meanings:
Value Meaning
false Show resumes where user is not willing to relocate for employment
true Show resumes where user is willing to relocate for employment

wa (Work Authorization)

The wa parameter is a compound, multi-valued parameter that restricts the search to resumes containing one or more of the supplied list of work authorization statuses. This is a compound parameter with two components separated by a hyphen: CountryID (from Appendix B) and WorkStatusID (below).

Possible values are found here:
http://integrations.monster.com/Toolkit/Enumeration/EducationLevel For example, the query wa=164-1%2c160-1 will query for resumes with owners who are authorized to work in the US or the UK for any employer.

tsalcur (Target Salary Currency)

The tsalcur parameter restricts the search to resumes with desired salary in the currency supplied. The possible values the currency's abbreviation.
For example: http://prdbx.monster.com/query.ashx?q=java&tsni=0&tnsalmax=25000&tsalcur=USD

tnsalmin (Target Normalized Salary Minimum)

The tnsalmin parameter restricts the search to resumes with desired normalized (annualized) salary greater than or equal to the supplied value.

tnsalmax (Target Normalized Salary Maximum)

The tnsalmax parameter restricts the search to resumes with desired normalized (annualized) salary less than or equal to the supplied value.

tsni (Target salary not included)

The tsni parameter is a flag that indicates whether resumes that do not specify a target salary should be included in the search results (0: Do not include resumes, 1: Include resumes). This is only applicable when the tnsalmin and or the tnsalmax parameters are used.

edumjr (Education Major)

The edumjr parameter allows a user to restrict a query based on a seekers education major. One or more education majors may be specified and the resume must match one of the requested values.

ten (Job Tenure)

The ten parameter restricts the search to resumes with specified job tenure. The value is a number (of years) combined with one of the following operators. URL encoding is required.
Example Meaning Encoded form
">3" ten=%3E3 Authorized to work for any employer
"<10" ten=%3C10 Authorized to work for any employer
"20+" ten=20%2B Authorized to work for any employer
"10-20" ten=10-20 Authorized to work for any employer

wtt (Willingness to Travel)

The wtt (Willingness to Travel) parameter is an optional parameter that restricts the search to candidates percentage willingness to travel. The possible values are as follows:
wtt ID Meaning
1 No willing to travel
2 25% willing to travel
3 50% willing to travel
4 75% willing to travel
5 100% willing to travel

For Example: the following specifies up to 25% willing to travel: wtt=2

yex (Years experience)

The yex parameter is an optional parameter that restricts the search to resumes with the specified years of experience.
For Example: the following specifies 5 years of experience: yex=5

gsc (Global Security Clearance)

The gsc parameter is a compound, multi-valued parameter that restricts the search to resumes containing one or more Security Clearance for authorized employers. This is a compound parameter with two components separated by a hyphen: CountryID (from Appendix B) and SecurityClearanceID (below). The possible values for SecurityClearanceID are as follows:
SecurityClearance ID Meaning
11 None
12 Active Confidential
13 Active Secret
14 Active Top Secret
15 Inactive Confidential
16 Inactive Secret
17 Inactive Top Secret

Global Security Clearance search functionality requires an additional license. Please contact your Monster representative for more details.

co (Country)

The co parameter restricts search results to resumes for a particular country. These values are the country abbreviation for the particular country to search within.
For example:
http://prdbx.monster.com/query.ashx?ver=2.0&q=test&co=AU
where AU is for Australia, CA is for Canada, UK is used for the UK, and etc.

loc (Location)

The loc parameter restricts search results to resumes for a particular location with a radius specified.
For Example: the following specifies 5 years of experience:
loc=Boston-20 (search within 20 miles radius around Boston)
loc=Portland%252C%2520OR (This is UE(UE("Portland, OR")).)

lstat (Legal Status)

A comma-separated list of CountryID-LegalStatusID pairs. Restricts the search results to resumes with at least 1 of the specified statuses.
For Example:
stat=164-1%2c30-2 CountryID is defined in Appendix B.
LegalStatusID is defined as follows: 1=Citizen, 2=Permanent Resident, 3=Other

veteran (Veteran Status)

Can be used to restrict the search results to candidates with or without veteran status.
Example:
veteran=1 (return only candidates with veteran status)
veteran=0 (return only candidates without veteran status)

folderidf (folder ID filter)

Restricts the search results to resumes in the specified folder(s). A folder is specified using a folderID. Use commas to separate multiple folderIDs.
For example:
folderidf=888 (results from folderID 888 only)
folderidf=888%2C999 (results from folderID 888 or 999 only)

rvi (resume values to include)

The search results will include all resumes and only those resumes in the specified folders. Other search parameters may affect only the ordering and relevance scores. A folder is specified using a folderID. Use commas to separate multiple folderIDs.
For example:
folderidf=888 (all resumes from folderID 888 only)
folderidf=888%2C999 (all resumes folderID 888 and 999 only)

folderidi (folder ID inclusion)

The search results will include all resumes and only those resumes indicated by the rvi parameter. The rvi parameter is a comma-separated list of resume values, each of which uniquely identifies a resume. Other search parameters may affect only the ordering and relevance scores.

srcid (First Tier Resume Source ID's)

Restricts search results to resumes originating from the specified sources. Each source is identified using a Source ID that can be found here: http://integrations.monster.com/Toolkit/Enumeration/ResumeOrigin defined in the table below. 2 or more IDs may be combined using a comma-separator.
For example:
srcid=11 (Monster only)
srcid=11%2C12 (Monster or Newspapers only)

reqcode (Requisition Codes)

Restricts search results to resumes with provided requisition code.
For example:
reqcode=123abc

srefcode (Seeker Reference Codes)

Restricts search results to resumes with provided seeker reference code.
For example:
srefcode=123abc

This section covers various details, changes and new elements that might not be apparent in the XML schema.

XML encoding

The XML encoding is UTF-8. The following is the first line of the return XML:

Current Security Clearances [Licensed] *

Current security clearance and the active clearance flag are returned in the PersonalData section of the XML if the caller is licensed for this information.

Possible values are found here: http://integrations.monster.com/Toolkit/Enumeration/ClearanceLevel
 
<Monster>
<Resumes>
<Resume>
<PersonalData>
<ActiveClearance>1</ActiveClearance>
<SecurityClearance>7</SecurityClearance>
Errors

The following section outlines error values and explanations that may be returned from a search request. The following illustrates the structure of the error XML:
<?xml version="1.0" encoding="UTF-8"?>
<Monster>
<Errror>
<Error Number="ERROR_NUMBER_IN_HEXADECIMAL">
<Message>ERROR_MESSAGE</Message>
</Errors>
</Monster>

The following is an example error:

<?xml version="1.0" encoding="UTF-8"?>
<Monster>
<Errror>
<Error Number="0xA0000999">
<Message>Processing error</Message>
</Errors>
</Monster>
When an error occurs please retry your search and or contact Monster support
 

Example Queries

This section contains example query URLs (without the required cat parameter) that may be submitted to the Monster Power Resume Search Service.

Query Example #1 - Basic Keyword filtering

http://prdbx.monster.com/query.ashx?q=film%2bactor&ver=2.0
Returns resumes containing the word "film" and the word "actor".

Query Example #2 - Date filtering

http://prdbx.monster.com/query.ashx?q=%22auto%2bmechanic%22& ver=2.0&mdatemaxage=1440
Returns resumes containing the phrase "auto mechanic" posted or modified within the last day (1440 minutes).

Query Example #3 - Target Job Type ID filtering

http://prdbx.monster.com/query.ashx?q=cook%2cchef&ver=2.0&tjtid=1
Returns resumes containing the word "cook" or "chef" where the resume owner has expressed an interest in working for Job Type ID 1 (tjtid=1).

Query Example #4 - Education filtering

http://prdbx.monster.com/query.ashx?q=%22Director%2bof%2bSales%22& ver=2.0&minedulvid=6,7
Returns resumes containing the phrase "Director of Sales" where the resume owner has a Doctorate (edulv=7) or a Master's (edulv=6) degree.

Query Example #5 - Work Authorization filtering

http://prdbx.monster.com/query.ashx?q=%22marketing%2bguru%22&ver=2.0&wa=160-1
Returns resumes containing the phrase "marketing guru" where the resume owner authorized to work for any employer in the UK (wa=160-1).
 

Appendix - Monster Country ID List

(Click to Appendix - Monster Country ID List)
Country ID
Afghanistan 1
Albania 2
Algeria 3
American Samoa 178
Andorra 4
Angola 5
Anguilla 176
Antarctica 177
Antigua and Barbuda 175
Argentina 6
Armenia 7
Aruba 179
Australia 8
Austria 9
Azerbaidjan 10
Bahamas 11
Bahrain 12
Bangladesh 13
Barbados 14
Djibouti 44
Dominica 186
Dominican Republic 187
East Timor 233
Ecuador 45
Egypt 46
El Salvador 47
Equatorial Guinea 48
Eritrea 49
Estonia 50
Ethiopia 51
Falkland  
Islands 189
Faroe Islands 191
Fiji 52
Finland 53
Former USSR 228
France 54
France (European Territory) 55
French Guyana 193
20 Other
20 Other
20 Other
Country ID
Belarus 15
Belgium 16
Belize 17
Benin 18
Bermuda 19
Bhutan 20
Bolivia 21
Bosnia-Herzegovina 22
Botswana 23
Bouvet Island 181
Brazil 24
British Indian Ocean Territory 201
Brunei Darussalam 180
Bulgaria 25
Burkina Faso 26
Burundi 27
Cambodia 28
Cameroon 29
Canada 30
French Southern Territories 230
Gabon 56
Gambia 57
Georgia 58
Germany 59
Ghana 60
Gibraltar 198
Greece 49
Greenland 50
Grenada 192
Guadeloupe (French) 196
Guam 62
Guatemala 198
Guinea 63
Guinea Bissau 64
Guyana 65
Haiti 200
Heard and McDonald Islands 199
Honduras 66
Hong Kong 67
Mongolia 104
Montserrat 211
Morocco 105
Mozambique 106
Myanmar, Union of (Burma) 242
Namibia 107
Nauru 215
Nepal 108
Netherlands 109
Netherlands Antilles 110
Neutral Zone 216
New Caledonia (French) 213
New Zealand 111
Nicaragua 112
Niger 113
Nigeria 114
Niue 217
Norfolk Island 214
North Korea 115
Northern Mariana Islands 209
Sri Lanka Other
Sudan 144
Suriname 145
Svalbard and Jan Mayen Islands 146
Swaziland 225
Sweden 148
Switzerland 149
Syria 150
Tadjikistan 151
Taiwan 152
Tanzania 153
Thailand 154
Togo 155
Tokelau 231
Tonga 232
Trinidad and Tobago 234
Tunisia 156
Turkey 157
Turkmenistan 158
Turks and Caicos Islands 229
Zambia 173
Country ID
Cape Verde 31
Cayman Islands 32
Central African Republic 33
Chad 34
Chile 35
China 36
Christmas Island 185
Cocos (Keeling) Islands 182
Colombia 37
Comoros 204
Congo 38
Cook Islands 183
Costa Rica 39
Croatia 40
Cuba 184
Cyprus 41
Czech Republic 42
Denmark 43
Hungary 68
Iceland 69
India 70
Indonesia 71
Iran 72
Iraq 73
Ireland 74
Israel 75
Italy 76
Ivory Coast 77
Jamaica 202
Japan 78
Jordan 79
Kazakhstan 80
Kenya 81
Kiribati 203
Kuwait 82
Kyrgyzstan 83
Laos 84
Latvia 85
Lebanon 86
Lesotho 87
Norway 116
Oman 117
Pakistan 118
Palau 222
Panama 119
Papua New Guinea 219
Paraguay 120
Peru 121
Philippines 122
Pitcairn Island 221
Poland 123
Polynesia (French) 218
Portugal 124
Qatar 126
Reunion (French) 127
Romania 128
Russian Federation 129
Rwanda 130
S. Georgia & S. Sandwich Islands 197
Saint Helena 224
Tuvalu 235
Uganda 159
UK 160
Ukraine 159
United Arab Emirates 162
Uruguay 163
US 164
USA Minor Outlying Islands 236
Uzbekistan 165
Vanuatu 239
Vatican City 166
Venezuela 167
Vietnam 168
Virgin Islands (British) 169
Virgin Islands (USA) 238
Wallis and Futuna Islands 240
Virgin Islands (British) 240
Western Sahara 188
Yemen 170
Yugoslavia 171
Zimbabwe 174
 
 

Testing your integration

Client should ignore certificate errors when testing on MITE.

Test the following activities that are part of integrated private resume board searching:
  1. Create and POST an inventories query to the BGW request
  2. Receive and view BGW response showing resume transaction inventory level.
  3. Create and POST a resume retrieval query to the BGW.
  4. Receive and view BGW response showing full resume.