0% found this document useful (0 votes)

12 views262 pages

Tbe API Guide

The Taleo Business Edition Web Services API Reference Guide provides comprehensive documentation for developers to integrate with the Taleo Business Edition platform using SOAP-based web services. It covers topics such as security, user authentication, API calls, and includes detailed information on various API elements for managing accounts, candidates, and other entities. The guide emphasizes the importance of confidentiality and is intended for Taleo customers and partners only.

Uploaded by

Lloyd Marsh

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

12 views262 pages

Tbe API Guide

Uploaded by

Lloyd Marsh

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 262

TALEO BUSINESS EDITION

WEB SERVICES API REFERENCE GUIDE

© Taleo Business Edition. All rights reserved.

CONTENTS

CONTENTS ..................................................................................................................................... 2
WELCOME ...................................................................................................................................... 6
INFORMATION CONFIDENTIALITY ...................................................................................................... 6
Confidential Information ........................................................................................................... 6
AUDIENCE AND BACKGROUND ......................................................................................................... 6
REQUIRED KNOWLEDGE AND SKILLS ............................................................................................... 7
SUPPORT ....................................................................................................................................... 7
INTRODUCTION ............................................................................................................................. 8
SECURITY AND USER AUTHENTICATION ........................................................................................... 8
OBTAINING THE TALEO BUSINESS EDITION WSDLS ......................................................................... 8
IMPORTING THE WSDLS TO YOUR DEVELOPMENT PLATFORM .......................................................... 9
GETTING STARTED ......................................................................................................................... 9
ERROR TRACING .......................................................................................................................... 10
API SIMPLE DATA OBJECTS (BEANS) ..................................................................................... 10
API BEAN OVERVIEW ................................................................................................................... 10
IMPORTANT NOTES ON DATA TRANSFER:....................................................................................... 11
REQUIRED FIELDS ........................................................................................................................ 11
XML FIELD DATA TYPES............................................................................................................... 11
FIELD CHARACTER LIMITS ............................................................................................................. 12
DATE AND TIME FIELD DESCRIPTION ............................................................................................. 12
API CALLS AND SAMPLE XML .................................................................................................. 13
ACCOUNT API CALLS ................................................................................................................... 13
accountBean Definition: ......................................................................................................... 13
createAccount Element: ......................................................................................................... 14
deleteAccount Element: ......................................................................................................... 16
getAccountById Element: ....................................................................................................... 17
getAccountHistory Element: ................................................................................................... 18
searchAccount Element: ........................................................................................................ 19
updateAccount Element: ........................................................................................................ 22
ATTACHMENT API CALLS .............................................................................................................. 24
createAttachment Element: .................................................................................................... 24
createEntityAttachment Element: ........................................................................................... 26
deleteAttachment Element: .................................................................................................... 27
getAttachment Element: ......................................................................................................... 28
getAttachmentData Element: ................................................................................................. 29
getAttachments Element: ....................................................................................................... 31
getEntityAttachments Element: .............................................................................................. 32
updateAttachment Element: ................................................................................................... 33
BACKGROUND CHECK API CALLS ................................................................................................. 34
createBackgroundCheck Element:......................................................................................... 35
deleteBackgroundCheck Element: ......................................................................................... 37

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 2

getBackgroundCheckById Element: ...................................................................................... 38
getBackgroundChecksByCandidate Element: ....................................................................... 39
updateBackgroundCheck Element:........................................................................................ 40
CANDIDATE API CALLS ................................................................................................................. 42
createCandidate Element:...................................................................................................... 44
deleteCandidate Element: ...................................................................................................... 47
getCandidateById Element:.................................................................................................... 47
getCandidateDetailsById Element: ........................................................................................ 50
getCandidateHistory Element:................................................................................................ 54
getCandidatesByRequisition Element:................................................................................... 55
getCandidateWorkHistory Element: ....................................................................................... 56
getCandReqStatus Element:.................................................................................................. 59
getRequisitions Element:........................................................................................................ 60
searchCandidate Element: ..................................................................................................... 61
submitCandidate Element: ..................................................................................................... 64
removeCandidate Element:.................................................................................................... 65
updateCandidate Element:..................................................................................................... 66
upsertCandidateToRequisitions Element:.............................................................................. 68
CONTACT API CALLS.................................................................................................................... 71
createContact Element:.......................................................................................................... 72
deleteContact Element: .......................................................................................................... 74
getContactById Element:........................................................................................................ 75
updateContact Element:......................................................................................................... 80
CONTACT LOG API CALLS ............................................................................................................ 82
createContactLog Element:.................................................................................................... 83
deleteContactLog Element: .................................................................................................... 84
getContactLogById Element:.................................................................................................. 85
getContactLogsByEntity Element:.......................................................................................... 86
updateContactLog Element:................................................................................................... 87
DEPARTMENT API CALLS .............................................................................................................. 89
createDepartment Element: ................................................................................................... 89
deleteDepartment Element:.................................................................................................... 91
getDepartmentById Element: ................................................................................................. 92
getDepartmentByName Element:........................................................................................... 93
getDepartments Element:....................................................................................................... 94
upsertDepartment Element: ................................................................................................... 97
EMAIL LOG API CALLS .................................................................................................................. 98
createEmailLog Element: ....................................................................................................... 98
createEmailSentLog Element:................................................................................................ 99
EMPLOYEE API CALLS ................................................................................................................ 101
createEmployee Element: .................................................................................................... 103
deleteEmployee Element: ................................................................................................................106
deleteEmployeeByNumber Element: ................................................................................... 107
getEmployeeById Element: .................................................................................................. 108
getEmployeeByNumber Element: ........................................................................................ 114
searchEmployee Element: ................................................................................................... 116
updateEmployee Element: ................................................................................................... 119
upsertEmployee Element: .................................................................................................... 121
EVENT API CALLS ...................................................................................................................... 124
createEvent Element: ........................................................................................................... 125
deleteEvent Element: ........................................................................................................... 127

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 3

getEventByEntity Element:................................................................................................... 128
getEventById Element:......................................................................................................... 129
getPublicEvents Element: .................................................................................................... 131
updateEvent Element: .......................................................................................................... 132
INTERVIEW API CALLS ................................................................................................................ 134
createInterview Element:...................................................................................................... 135
deleteInterview Element: ...................................................................................................... 137
getInterviewsByCandidate Element: .................................................................................... 138
getInterviewById Element:.................................................................................................... 139
updateInterview Element:..................................................................................................... 140
LINK API CALLS ......................................................................................................................... 142
createLink Element:.............................................................................................................. 142
removeLink Element:............................................................................................................ 144
LOCATION API CALLS ................................................................................................................. 145
createLocation Element:....................................................................................................... 149
deleteLocation Element:....................................................................................................... 150
getLocationById Element: .................................................................................................... 151
getLocationByName Element:.............................................................................................. 153
getLocations Element:.......................................................................................................... 154
upsertLocation Element:....................................................................................................... 156
LOGIN API CALLS ....................................................................................................................... 158
getUrl Element...................................................................................................................... 158
login Element:....................................................................................................................... 159
logout Element: .................................................................................................................... 160
getLoginToken Element: ...................................................................................................... 161
METADATA / PICKLIST API CALLS ................................................................................................ 162
getLookup Element: ............................................................................................................. 162
getMetadata Element: .......................................................................................................... 165
OFFER API CALLS ...................................................................................................................... 167
createOffer Element: ............................................................................................................ 168
deleteOffer Element: ............................................................................................................ 170
getBinaryOffer Element: ....................................................................................................... 170
getOfferByID......................................................................................................................... 171
getOffers Element: ............................................................................................................... 173
setBinaryOffer ...................................................................................................................... 174
updateOffer Element: ........................................................................................................... 175
REFERENCE API CALLS .............................................................................................................. 177
createReference Element:.................................................................................................... 178
deleteReference Element:.................................................................................................... 179
getReferencesByCandidate Element: .................................................................................. 180
getReferenceById Element: ................................................................................................. 181
updateReference Element:................................................................................................... 182
REGION API CALLS .................................................................................................................... 184
createRegion Element:......................................................................................................... 185
deleteRegion Element: ......................................................................................................... 186
getRegionById Element:....................................................................................................... 187
getRegionByName Element: ................................................................................................ 188
getRegions Element: ............................................................................................................ 190
upsertRegion Element:......................................................................................................... 192
REQUISITION API CALLS ............................................................................................................. 193
createRequisition Element: .................................................................................................. 194

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 4

createRequisitionTemplate Element: ................................................................................... 196
deleteRequisition Element:................................................................................................... 198
getRequisitionById Element: ................................................................................................ 199
getRequisitionHistory Element: ............................................................................................ 201
postRequisition Element:...................................................................................................... 203
searchRequisition Element:.................................................................................................. 205
unpostRequisition Element:.................................................................................................. 208
updateRequisition Element: ................................................................................................. 209
RESUME API CALLS ................................................................................................................... 211
getBinaryResume Element:.................................................................................................. 211
parseResume Element:........................................................................................................ 212
parseResumeIntoCandidate Element: ................................................................................. 214
setBinaryResume Element:.................................................................................................. 215
ROLLING ENTITY CALLS .............................................................................................................. 217
deleteRollingEntity Element: ................................................................................................ 218
getRollingEntities Element: .................................................................................................. 219
upsertRollingEntity Element: ................................................................................................ 223
SEARCH API CALLS.................................................................................................................... 224
SYSTEM API CALLS .................................................................................................................... 225
getEnabledServices Element: .............................................................................................. 225
getSystemProps Element:.................................................................................................... 226
TASK API CALLS ........................................................................................................................ 229
createTask Element: ............................................................................................................ 230
deleteTask Element:............................................................................................................. 232
getTaskByEntity Element: .................................................................................................... 233
getTaskById Element: .......................................................................................................... 234
getTaskByUser Element:...................................................................................................... 236
updateTask Element: ........................................................................................................... 237
USER API CALLS........................................................................................................................ 239
createUser Element:............................................................................................................. 242
createUserWithPermissions Element:.................................................................................. 243
deleteUser Element:............................................................................................................. 246
getUserById Element: .......................................................................................................... 247
getUserHistory Element: ...................................................................................................... 248
searchUser Element: ............................................................................................................ 250
updateUser Element:............................................................................................................ 252
USER ASSOCIATION CALLS ......................................................................................................... 254
getAssociatedUsers Element: .............................................................................................. 255
removeAssociatedUser Element: ......................................................................................... 256
setAssociatedUser Element: ................................................................................................ 257
REVISION CONTROL ................................................................................................................... 260
Version Details and Background .......................................................................................... 260

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 5

WELCOME

Information Confidentiality
The Taleo Business Edition Application Programming Interface (API) and its associated
documents, including this guide, are provided for Taleo customers and Taleo partners solely. This
document should not be viewed, reviewed, replicated, referred to, or reproduced by individuals
not deemed a Taleo Business Edition customer and/or partner.

It shall be agreed by the recipient of the document (hereafter referred to as “the other party”) that
confidential information disclosed by Taleo through i ts documents shall be retained in confidence
by the other party, and its respective employees, affiliates and/or subsidiaries, pursuant to the
following terms and condi t ions:

Confidential Information

For the purpose herein, the term “Confidential Information” shall mean the following:
1. Any information, know-how, data, process, technique, design, drawing, program, formula
or test data, work in process, business plan, sales, suppl iers, customer, employee,
investor or business information contained in a document, whether in written, graphic, or
electronic form; or
2. Any document, diagram, or drawing which is either conspicuously marked as
“Confidential”, known or reasonably known by the other party to be confident ial, or is of a
proprietary nature, and is learned or disclosed in the course of discussions,
demonstrations, or other collaboration undertaken between the parties.

Audience and Background

This guide is intended for developers who plan to utilize the Taleo Business Edition platform API
for integration with third-party products and services.

The Taleo Business Edition SOAP API provides programmatic access to the Taleo Business
Edition application. The API provides the same functions and capabilities as a logged in user of
the system would have access to. Developers are able to build custom applications and services
in their platform of choice that supports the open standard “Web Services” methodology via the
utilization of:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 6

 Simple Object Access Protocol (SOAP) calls
 Taleo defined Web Services Definition Language (WSDL), and
 XML Schema Definition language (XSD)

Required Knowledge and Skills

Use of this guide assumes you are already familiar with the following:
 Taleo Business Edition (click Knowledgebase & Help sections from your instance)
 HTML (details at http://www.w3schools.com/html/default.asp)
 XML and XHTML (details at http://www.w3schools.com/xml/default.asp)
 Web Services (details at http://www.w3schools.com/webservices/default.asp)
 SOAP (details at: http://www.w3schools.com/soap/default.asp)

A SOAP client can be written in a wide range of development tools and platforms, such as Java,
Visual Basic, Perl, C#, PHP, .NET, etc. As such, Taleo does not provide platform code support or
sample code to developers. The API is inherent to the application, not a supported module, and
Taleo assumes that developers are experts in their platform of choice with utilizing web services.
Simple SOAP-based sample test cases have been provided within the API Guide to provide
assistance and direction in making Taleo Business Edition API calls.

Support
Contact Taleo Business Edition Support for any technical issues as they pertain to the API. Taleo
Business Edition Support is available via:
 Email: [email protected]
 Online: Click ‘Web Support’ in the top right hand side from within Taleo Business Edition
 Telephone: Dial 1-888-560-1717 (8:00 a.m. to 8:00 p.m. ET Monday-Friday, excluding
official Taleo holidays)

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 7

INTRODUCTION
The Taleo Business Edition Web API provides for simple integration between Taleo and other
systems by means of SOAP-based web services procedure calls. The API uses SOAP over
HTTPS to receive requests and send responses, allowing seamless integration between Taleo
and other enterprise applications regardless of the programming language used by the client.

Security and User Authentication

Only Taleo Premium Service customers can access the Taleo Web API. If you are a trial
customer, or current Taleo subscriber interested in evaluating the Web API, please contact your
sales representative to request Premium Service for access.

Taleo Business Edition API exposes all SOAP methods using SSL, however an SSL certificate is
not required by the client application.

Client applications must make a login call to the Taleo Web API providing valid credentials of an
existing defined user within the Taleo Business Edition user interface. Either a new user will need
to be created within the application, or an existing user can be utilized. Client applications that
access the Taleo Business Edition API are subjected to the same Access Control restrictions as
defined within the application; please validate what controls you will need the API to use and
define a user with the appropriate controls accordingly.

Credentials needed to log in to the API include (in login call order):
 Company Code
 User Name
 Password

If login is successful, the call will return a session ID to be used in all subsequent calls to the API
as the very first parameter.

Obtaining the Taleo Business Edition WSDLs

As with all standards‐based SOAP API’s, the Taleo Business Edition API definition is available
on the Web Service as an XML‐formatted WSDL file. Two WSDL’s are required for integrating
with Taleo Business Edition:
 DispatcherAPI: http://tbe.taleo.net/wsdl/DispatcherAPI.wsdl
 WebAPI: http://tbe.taleo.net/wsdl/WebAPI.wsdl

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 8

The DispatcherAPI WSDL provides one simple function: request the organization code and
receive a response URL of where the account/zone is located in the pool of Taleo Business
Edition servers. The reason for the Dispatcher is that accounts/zones may be moved to a new
server pool for optimal load balancing. The Dispatcher ensures that the client application will
always find the organization zone URL.

The WebAPI WSDL defines all of the Taleo Business Edition calls. For more information on
WSDL(s), see: http://www.w3.org/TR/wsdl.

Importing the WSDLs to Your Development Platform

After you obtain the two Taleo Business Edition WSDLs, import them into your development
environment for building your Web service applications. The import process depends on the
development environment, programmatic language and tools. For example, the Microsoft Visual
Studio development environment handles the tasks automatically.

A good start would be to practice WSDL import and web service call initiations with a generic web
service tool prior to actual coding. Using a tool like SOAPUI (http://soapui.org), which comes in a
freeware and premium licensed version, allows users to create web service projects, practice
requests and test cases. It is highly recommended to go down this path first.

NOTE: Taleo assumes you are familiar with basic programming concepts and already have a
programming development environment set up on your computer.

Getting Started
A typical scenario of using the Taleo Web API is:
 Customer builds a SOAP client to interact with Taleo Web API.
 The very first call is made to the Dispatcher API to present valid company code and
obtain entry URL to be used in all subsequent calls. This call is always made to URL
https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter.
 SOAP client makes login call to the received company code URL and present valid
credentials of an existing user.
 Customer’s SOAP client sends various requests to the Taleo Web API This may include,
for example, searching through the candidates or requisitions database, requesting
detailed information on a particular candidate or requisition, creation of a new candidate
record, etc.
 At the end of the session, customer’s SOAP client logs out of Taleo.

Refer to the ‘Login API Calls’ section for details on logging in and logging out of Taleo Business
Edition.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 9

Error Tracing
Most issues can be resolved in minutes if the XML error can be provided. Web API errors may
occur during the communication process, which will not provide the error log within Taleo
Business Edition for Taleo’s support team to analyze. In addition, a programmer is shielded from
the XML trace. As such, it is essential to trace the communication between the client and Taleo
Business Edition API, through third-party tools like tcpmon (https://tcpmon.dev.java.net/). tcpmon
is an open-source utility for monitoring the data flowing on a TCP connection. tcpmon is used by
placing it in-between a client and a server. The client is made to connect to tcpmon, and tcpmon
forwards the data to server along-with displaying it in its GUI.

Note: It is up to the client programmer to be sure that any value assigned to a string field of a
bean is compliant with the W3C XML spec. Please ensure control or bad characters (i.e. #xC) are
shielded from field elements.

API SIMPLE DATA OBJECTS (BEANS)

API Bean Overview

The Taleo Web API uses the following simple data objects to send and receive information:
 accountBean
 attachmentBean
 backgroundCheckBean
 calendarEventBean
 candidateBean
 contactBean
 contactLogBean
 departmentBean
 employeeBean
 flexFieldBean
 historyBean
 interviewBean
 locationBean
 offerBean
 participantBean
 referenceBean
 regionBean
 requisitionBean
 searchResultBean
 taskBean
 userBean

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 10

Important Notes on Data Transfer:
 Binary candidate resumes and offer letters are sent and received as array of bytes
wrapped into ByteArray(64).
 Values from pick lists, such as candidate Source or State/Region are transferred as
strings, although on the server side they are stored as ID numbers. This is done because
server side ID numbers are meaningless for external clients. These string values can be
ERP codes assigned to lookup values or display labels. This also assumes that all values
from pick lists have unique display labels.
 To identify user Web API uses login name. For instance, to assign requisition’s
approvers, Web API takes a list of login names.
 There are several fields which cannot be modified by the client, for example: an object’s
unique id #, creation date, and last modified date. These fields are marked “read-only” in
the tables below.
 When an object is created or modified, the same policy is applied as if the object is
created/modified by a user using Taleo through the standard browser interface. For
instance, an attached file must meet security requirements, all mandatory fields specified
for a given candidate must be present, etc. If required conditions are not met in any given
transaction sent by the client, the operation will fail and a SOAP failure response will be
generated.
 Arrays of returned objects are wrapped in special beans such as SearchResultsArr and
HistoryBeanArr.

Required Fields
Fields marked as “required” in Administration section (both standard and custom) are also
required in Web API. Fields which are always required are marked in the sections below. If the
Web API client is trying to create an object without supplying all required fields, an exception will
be thrown.

XML Field Data Types

Taleo Business Edition SOAP API data types are based on the XML data types shown below.
 Boolean - A logical value, including true, false, 0, and 1.
 dateTime Date/time values (timestamps).
 double - Numeric value
 int - Numeric value
 string - Any character data
 long – Server side value

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 11

Field Character Limits
The following character limits are set for non-stringent (string) data fields:
 URL – 300 characters
 Email – 100 characters
 Text – 100 characters
 Text Area – 80000 characters

Depending on the field type chosen within the application, any additional characters will be
automatically truncated when posted via the API.

Date and Time Field Description

All timestamp formats are system derived in ISO/UTC standard format with combined date and
time depiction referenced to the equivalent nautical time zone (GMT).

Formatting of dateTime stamps are similar to the following example where date is provided first in
[YYYY]-[MM]-[DD] and followed by (T) time [hh]:[mm] :[ss] and UTC GMT (Z) code:

2009-02-09T23:03:51.430Z

Please Note: All <creationDate> and <lastUpdated> dateTime variables are system derived –
these elements cannot be written too in any create, update and upsert calls, they will need to be
removed from your SOAP request.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 12

API CALLS AND SAMPLE XML

Account API Calls

Accounts are the companies and organizations involved with your business such as employers,
customers, search firms, agencies, etc.

accountBean Definition:
Data Field Name Data Field Type Required Acceptable Values
Account’s unique
server side ID. Can be
obtained by searching
id Long Read Only the accounts’
database or by
creating a new
account.
status String No Account’s Status from
pick list
name String Yes Account’s name
parentAccountId long No ID of parent account
type String No Account’s type (from
pick list)
industry String No Industry (from pick
list)
phone String No Phone number
fax String No Fax number
website String No Web site URL
address String No Street portion of
mailing address
city String No City name
zipCode String No ZIP or postal code
state String No State, region or
province name from
pick list
country String No Country code from
pick list
description String No Account’s description
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
flexValues FlexFieldBean[] No Array of flexible
(custom) field values

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 13

flexFieldBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
FieldName String Yes Field name
Value of Text, Email, URL, Pick list, or
StringValue String No Text Area field. For Multiple Pick list use
‘|’ to separate values.
IntValue int No Value of Integer field
DoubleValue double No Value of Decimal or Currency field
BooleanValue Boolean No Value of Check Box field
DateValue Date No Value of Date field

createAccount Element:
Operation type: Request-response.
 The endpoint receives a message to create an account, and sends a correlated message
of account ID.

Input: createAccountRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status
address
city
country
description
fax
in1 accountBean * industry
name *
parent
phone
state
type
website
zipCode

Output: createAccountResponse

Data Field Name Data Field Type Required Acceptable Values

createAccountReturn Long Yes Provided Account ID

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 14

createAccount Test Case:

Input: createAccountRequest

Output: createAccountResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 15

deleteAccount Element:
Operation type: Request-response.
 The endpoint receives a message to delete an account, and sends a correlated message
only if error occurred.

Input: deleteAccountRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Account ID Yes ID of Account

Output: deleteAccountResponse

Data Field Name Data Field Type Required Acceptable Values

deleteAccountReturn

deleteAccount Test Case:

Input: deleteAccountRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteAccount>
<in0>webapi-8483625119411683650</in0>
<in1>1</in1>
</urn:deleteAccount>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteAccountResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 16

getAccountById Element:
Operation type: Request-response.
 The endpoint receives a message to get an account details, and sends a correlated
message of Account information.

Input: getAccountByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Account ID Yes ID of Account

Output: getAccountByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getAccountByIdReturn accountBean

getAccountById Test Case:

Input: getAccountByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getAccountById>
<in0>webapi-8483625119411683650</in0>
<in1>2</in1>
</urn:getAccountById>
</soapenv:Body>
</soapenv:Envelope>

Output: getAccountByIdResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 17

<country>Brazil</country>
<description>TESTING</description>
<fax>894-439-0404</fax>
<industry>Aerospace</industry>
<name>Brazil Aero</name>
<parentAccountId>0</parentAccountId>
<phone>894-439-0404</phone>
<state xsi:nil="true"/>
<type>Partner</type>
<webSite>www.brazil.com</webSite>
<zipCode xsi:nil="true"/>
</getAccountByIdReturn>
</getAccountByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getAccountHistory Element:
Operation type: Request-response.
 The endpoint receives a message to get an account history, and sends a correlated
message of Account history information.
 This object is used to fetch a history log entry which reflects a past event or action related
to accounts. History records can only be created by the server, they cannot be modified
or deleted. History log includes server side ID, test describing history record, complete
text of email message (for email events) and creation date.

Input: getAccountHistoryRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of Account

Output: getAccountHistoryResponse

Data Field Name Data Field Type Required Acceptable Values

getAccountHistoryReturn historyBean []

getAccountHistory Test Case:

Input: getAccountHistoryRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 18

Output: getAccountHistoryResponse

searchAccount Element:
Operation type: Request-response.
 The endpoint receives a message to query all accounts based on defined key (field
name) and value (data looking for), and sends a correlated message of Account ID and
associated search relevance.
 Relevance is a value between 0 and 100, which reflects how well the account matches
the search criteria
 Map of search parameters always contains:
o key: name of field to search as a string
o value: search parameter as string.
 Format of search value may differ depending on data type of the search field:
 For text, text area, email, URL fields: simple text to be found (case-insensitive) in this
field. Example:
o key=”city”, value=”Francisco” will search for all candidates with ”Francisco” in
“city” field.
 For integer, double, currency: interval between two numbers separated by ‘|’ character.
Either left (from) or right (to) side can be omitted. Example:
o key=”rank”, value=”100|” will search for all candidates with rank value no less
than 100.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 19

o key=”rank”, value=”|200” will search for all candidates with rank value no more
than 200.
o key=”rank”, value=”100|200” will search for all candidates with rank value
between 100 and 200 (inclusive).
 For date fields: interval between two dates in ISO yyyy-MM-dd format, separated by ‘|’
character. Either left (from) or right (to) side can be omitted. Example:
o key=”startDate”, value=”2004-06-01|” will search for all candidates with start date
on or after June 1st 2004.
o key=”startDate”, value=”|2004-08-01” will search for all candidates with start date
on or before August 1st 2004.
o key=”startDate”, value=”2004-06-01|2004-08-01” will search for all candidates
with start date between June 1st 2004 and August 1st 2004 (inclusive).
 For date interval fields: number of days from today to the past. Example:
o key=” addedWithin”, value=”7” will search for all candidates added to the system
within the last week.
 For single pick list: code value or name of selected item. Example:
o key=”country”, value=”US” will search for all candidates with country field equals
to “United States”.
o key=”status”, value=”available” will search for all candidates in “Available” status.
 For multiple pick list: code values or names of selected items, separated by ‘|’ character.
Example:
o key=”customMultiple”, value=”A1|B2|X5” will search for all candidates with
customMultiple field containing one or more of values: A1, B2, X5.
 For check box fields: “true” if check box must be checked, “false” is unchecked. Example:
o key=” flagged”, value=”true” will search for all candidates “flagged” for the user
currently logged in.
 Search keys names and types can be found in Administration>Customize>Account
Fields. They may include both system fields (listed below for convenience) and custom
fields. For custom fields External name is used as key name.

System Search Keys:

Data Field Name Parameter Type Description

Keyword(s) in account’s description.
keyword String Identical syntax as used in Taleo browser
interface.
name String Account’s name
parentAccountId String ID of parent account
type String Account’s type
industry String Industry
phoneAll String Any account’s phone number
city Pick list City name
State, region or province name from pick
state String
list
country String Country code from pick list
addedWithin Integer Added within N days
updatedWithin Integer Updated within N days

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 20

Input: searchAccountRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
key
in1 Item… Yes
value

Output: searchAccountResponse

Data Field Name Data Field Type Required Acceptable Values

searchAccountReturn searchResultBean []

searchAccount Test Case:

Input: searchAccountRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:searchAccount>
<in0>webapi-8483625119411683650</in0>
<in1>

<item>
<key>type</key>
<value>partner</value>
</item>
</in1>
</urn:searchAccount>
</soapenv:Body>
</soapenv:Envelope>

Output: searchAccountResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 21

</array>
</searchAccountReturn>
</searchAccountResponse>
</soapenv:Body>
</soapenv:Envelope>

updateAccount Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing account, and sends a correlated
message only if error occurred.
 Please Note: Update requests replace all data fields in the accountBean (i.e. data is not
appended or upserted). Send all elements back or the field values will be returned NULL.

Input:updateAccountRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues
id *
status
address
city
country
description
fax
in1 accountBean[] *
industry
name *
parent
phone
state
type
website
zipCode

Output: updateAccountResponse

Data Field Name Data Field Type Required Acceptable Values

updateAccountReturn

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 22

updateAccount Test Case:

Input: updateAccountRequest

Output: updateAccountResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 23

Attachment API Calls
Attachments are all of the appended files associated with any entity in Taleo Business Edition.
There is a one-to-many relationship with attachments to entities. Entities include accounts
(ACCT), candidates (CAND), contacts (CTCT), employees (EMPL), requisitions (REQU) and
users (WORK).

attachmentBean Definition:

Data Field Data Field

Required Acceptable Values
Name Type
id Long Read Only Attachment’s unique server side ID.
Type of related entity:
ACCT = accounts
CAND = candidates
entityType String CTCT = contacts
EMPL = employees
REQU = requisitions
WORK = users
entityId Long ID of associated entity
description String Description of the file
filename String Binary File Name
Text = text/plain
html = text/html
RTF = text/richtext
Word = application/msword
contentType String
DocX =
application/vnd.openxmlformats-
officedocument.wordprocessingml.document
PDF = application/pdf
data ByteArr base64Binary []
creationDate Date Read Only Date attachment was created

createAttachment Element:
Operation type: Request-response.
 The endpoint receives a message to create an attachment for a specific candidate, and
sends a correlated message of attachment ID.

Input: createAttachmentRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes Candidate ID
in2 String Yes Attachment

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 24

Description
in3 String Yes Attachment Name
in4 String Yes contentType
in5 ByteArr Yes binaryResume

Output: createAttachmentResponse

Data Field Name Data Field Type Required Acceptable Values

Provided Attachment
createAttachmentReturn Long Yes
ID

createAttachment Test Case:

Input: createAttachmentRequest

soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createAttachment>
<in0>webapi-5616904436472928038</in0>
<in1>15</in1>
<in2>test1.docx</in2>
<in3>test1.docx</in3>
<in4>application/vnd.openxmlformats-
officedocument.wordprocessingml.document</in4>
<in5>

<array>JVBERi0xLjQNJeLjz9MNCjYgMCBvYmogPDwvTGluZWFyaX==</array>
</in5>
</urn:createAttachment>
</soapenv:Body>
</soapenv:Envelope>

Output: createAttachmentResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 25

createEntityAttachment Element:
Operation type: Request-response.
 The endpoint receives a message to create an attachment for a specific ID associated
with a specific entity (i.e. Candidate, Employee, Account, etc.), and sends a correlated
message of attachment ID.

Input: createEntityAttachmentRequest

Data Field Data Field

Required Acceptable Values
Name Type
sessionId Long Read Only Attachment’s unique server side ID.
Type of related entity:
ACCT = accounts
CAND = candidates
entityType String
EMPL = employees
REQU = requisitions
WORK = users
entityId Long ID of associated entity
description String Description of the file
filename String Binary File Name
Text = text/plain
html = text/html
RTF = text/richtext
Word = application/msword
contentType String
DocX =
application/vnd.openxmlformats-
officedocument.wordprocessingml.document
PDF = application/pdf
data ByteArr base64Binary []

Output: createEntityAttachmentResponse

Data Field Name Data Field Type Required Acceptable Values

Provided Attachment
createEntityAttachmentReturn Long Yes
ID

createEntityAttachment Test Case:

Input: createEntityAttachmentRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 26

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createEntityAttachment>
<sessionId>webapi8668622358131845860</sessionId>
<entityType>REQU</entityType>
<entityId>69</entityId>
<description>pdfAttachment</description>
<fileName>new.pdf</fileName>
<contentType>application/pdf</contentType>
<data>

<array>JVBERi0xLjQNJeLjz9MNCjYgMCBvYmogPDwvTGluZWFyaXplZCAxL0wgMTg3NT==
</array>
</data>
</urn:createEntityAttachment>
</soapenv:Body>
</soapenv:Envelope>

Output: createEntityAttachmentResponse

deleteAttachment Element:
Operation type: Request-response.
 The endpoint receives a message to delete an attachment, and sends a correlated
message only if error occurred.

Input: deleteAttachmentRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of attachment

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 27

Output: deleteAttachmentResponse

Data Field Name Data Field Type Required Acceptable Values

deleteAttachmentReturn

deleteAttachment Test Case:

Input: deleteAttachmentRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteAttachment>
<in0>webapi9172860277027829324</in0>
<in1>8</in1>
</urn:deleteAttachment>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteAttachmentResponse

getAttachment Element:
Operation type: Request-response.
 The endpoint receives a message to get an attachment by attachment ID, and sends a
correlated message of attachment name, type, creation date and ID.

Input: getAttachmentRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of attachment

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 28

Output: getAttachmentResponse

Data Field Name Data Field Type Required Acceptable Values

getAttachmentReturn attachmentBean []

getAttachment Test Case:

Input: getAttachmentRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getAttachment>
<in0>webapi1673199911353581754</in0>
<in1>3</in1>
</urn:getAttachment>
</soapenv:Body>
</soapenv:Envelope>

Output: getAttachmentResponse

<soapenv:Body>
<getAttachmentResponse xmlns="urn:TBEWebAPI">
<getAttachmentReturn xmlns="">
<contentType>application/vnd.openxmlformats-
officedocument.wordprocessingml.document</contentType>
<creationDate>2009-09-04T18:33:50.830Z</creationDate>
<description>file_7896653827536535960.docx</description>
<id>3</id>
</getAttachmentReturn>
</getAttachmentResponse>
</soapenv:Body>
</soapenv:Envelope>

getAttachmentData Element:
Operation type: Request-response.
 The endpoint receives a message to get attachment data by ID, and sends the correlated
binary attachment data.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 29

Input: getAttachmentDataRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of attachment

Output: getAttachmentDataResponse

Data Field Name Data Field Type Required Acceptable Values

getAttachmentDataReturn base64Binary []

getAttachmentData Test Case:

Input: getAttachmentDataRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getAttachmentData>
<in0>webapi1673199911353581754</in0>
<in1>3</in1>
</urn:getAttachmentData>
</soapenv:Body>
</soapenv:Envelope>

Output: getAttachmentDataResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 30

getAttachments Element:
Operation type: Request-response.
 The endpoint receives a message to get attachment(s), and sends back attachment IDs.

Input: getAttachmentsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of candidate

Output: getAttachmentsResponse

Data Field Name Data Field Type Required Acceptable Values

getAttachmentReturn array of attachment IDs

getAttachments Test Case:

Input: getAttachmentsRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getAttachments>
<in0>webapi1673199911353581754</in0>
<in1>48</in1>
</urn:getAttachments>
</soapenv:Body>
</soapenv:Envelope>

Output: getAttachmentsResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 31

getEntityAttachments Element:
Operation type: Request-response.
 The endpoint receives a message to get attachment(s) associated with any Taleo
Business Edition entity that supports attachment upload, and sends back attachment IDs
associated with the entity ID.

Input: getEntityAttachmentsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
sessionID String Yes
at Login
Type of related entity:
ACCT = accounts
CAND = candidates
entityType Long Yes
EMPL = employees
REQU = requisitions
WORK = users
entityID Long Yes ID of associated entity

Output: getEntityAttachmentsResponse

Data Field Name Data Field Type Required Acceptable Values

getEntityAttachmentReturn array of attachment IDs

getEntityAttachments Test Case:

Input: getEntityAttachmentsRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getEntityAttachments>
<sessionId>webapi4356913335216569919</sessionId>
<entityType>REQU</entityType>
<entityId>69</entityId>
</urn:getEntityAttachments>
</soapenv:Body>
</soapenv:Envelope>

Output: getEntityAttachmentsResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 32

updateAttachment Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing attachment, and sends a
correlated message only if error occurred.
 Please Note: Update requests replaces the attachment file (i.e. data is not appended or
upserted).

Input: updateAttachmentRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes Attachment ID
Attachment
in2 String Yes
Description
in3 String Yes Attachment Name
in4 String Yes contentType
in5 ByteArr Yes binaryResume

Output: updateAttachmentResponse

Data Field Name Data Field Type Required Acceptable Values

updateAttachmentReturn

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 33

updateAttachment Test Case:

Input: updateAttachmentRequest

soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateAttachment>
<in0>webapi-5616904436472928038</in0>
<in1>15</in1>
<in2>test1.docx</in2>
<in3>test1.docx</in3>
<in4>application/vnd.openxmlformats-
officedocument.wordprocessingml.document</in4>
<in5>

<array>JVBERi0xLjQNJeLjz9MNCjYgMCBvYmogPDwvTGluZWFyaX==</array>
</in5>
</urn:updateAttachment>
</soapenv:Body>
</soapenv:Envelope>

Output: updateAttachmentResponse

Background Check API Calls

Background checks provides background check information that may have occurred for a specific
candidate in Taleo Business Edition. There is a one-to-many relationship with candidates to
background checks.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 34

backgroundCheckBean Definition:

Data Field Name Data Field Type Required Acceptable Values

Id long Account’s unique
server side ID. Can be
obtained by searching
Read Only the accounts’
database or by
creating a new
account.
Status String No Account’s Status from
pick list
Creator String Yes Creator’s login name
CandidateId long Yes ID of candidate
CheckerName String Yes Name of the checker
CheckerPhone String No Phone of the checker
CheckerEmail String No Email of the checker
Comments String No Comments
CreationDate Date Read Only Creation date
LastUpdated Date Read Only Last updated date
FlexValues FlexFieldBean[] No Array of flexible
(custom) field values

flexFieldBean Definition:

createBackgroundCheck Element:
Operation type: Request-response.
 The endpoint receives a message to create a background check, and sends a correlated
message of background check ID.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 35

Input:createBackgroundCheckRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
CandidateId *
CheckerName *
in1 backgroundCheckBean * CheckerPhone
CheckerEmail
Comments *
Status

Output: createBackgroundCheckResponse

Data Field Name Data Field Type Required Acceptable Values

Provided
createBackgroundCheckReturn Long Yes Background Check
ID

createBackgroundCheck Test Case:

Input: createBackgroundCheck Request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createBackgroundCheck>
<in0>webapi1673199911353581754</in0>
<in1>
<flexValues>

</flexValues>
<candidateId>48</candidateId>
<checkerEmail>[email protected]</checkerEmail>
<checkerName>Intellius Background</checkerName>
<checkerPhone>630-345-6978</checkerPhone>
<comments>Package 1 background check process</comments>
</in1>
</urn:createBackgroundCheck>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 36

Output: createBackgroundCheckResponse

deleteBackgroundCheck Element:
Operation type: Request-response.
 The endpoint receives a message to delete a background check instance, and sends a
correlated message only if error occurred.

Input: deleteBackgroundCheckRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
ID of Background
in1 Background Check ID Yes
Check

Output: deleteBackgroundCheckResponse

Data Field Name Data Field Type Required Acceptable Values

deleteBackgroundCheckReturn

deleteBackgroundCheck Test Case:

Input: deleteBackgroundCheckResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteBackgroundCheck>
<in0>webapi1673199911353581754</in0>
<in1>3</in1>
</urn:deleteBackgroundCheck>
</soapenv:Body>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 37

</soapenv:Envelope>

Output: deleteBackgroundCheckResponse

getBackgroundCheckById Element:
Operation type: Request-response.
 The endpoint receives a message to get a specific background check by ID, and sends a
correlated message of information associated with that background check instance.

Input: getBackgroundCheckByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
ID of Background
in1 BackgroundCheck ID Yes
Check

Output: getBackgroundCheckByIdResponse

Required Acceptable
Data Field Name Data Field Type
Values
getBackgroundCheckByIdReturn backgroundCheckBean

getBackgroundCheckById Test Case:

Input: getBackgroundCheckByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getBackgroundCheckById>
<in0>webapi1673199911353581754</in0>
<in1>4</in1>
</urn:getBackgroundCheckById>
</soapenv:Body>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 38

</soapenv:Envelope>

Output: getBackgroundCheckByIdResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getBackgroundCheckByIdResponse xmlns="urn:TBEWebAPI">
<getBackgroundCheckByIdReturn xmlns="">
<creationDate>2009-09-10T01:38:24.470Z</creationDate>
<flexValues>
<item>
<fieldName>BackgroundCheckURL</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong>www.intellius.com/report</valueLong>
<valueStr xsi:nil="true"/>
</item>
</flexValues>
<id>4</id>
<lastUpdated>2009-09-10T01:38:24.470Z</lastUpdated>
<status>Submitted</status>
<candidateId>48</candidateId>
<checkerEmail>[email protected]</checkerEmail>
<checkerName>Intellius Background Checks</checkerName>
<checkerPhone>630-345-6978</checkerPhone>
<comments>Package 3 background check process</comments>
<creator>skarim</creator>
</getBackgroundCheckByIdReturn>
</getBackgroundCheckByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getBackgroundChecksByCandidate Element:
Operation type: Request-response.
 The endpoint receives a message to get all background checks for a specific Candidate
ID, and sends a message of all background check IDs.

Input: getBackgroundChecksByCandidateRequest

Data Field Name Data Field Type Required Acceptable Values

in0 String Yes Session ID received

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 39

at Login
in1 Candidate ID Yes ID of Candidate

Output: getBackgroundChecksByCandidateResponse

Required Acceptable
Data Field Name Data Field Type
Values
Background
getBackgroundChecksByCandidateReturn
Check ID(s)

getBackgroundChecksByCandidate Test Case:

Input: getBackgroundChecksByCandidateRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getBackgroundChecksByCandidate>
<in0>webapi1673199911353581754</in0>
<in1>48</in1>
</urn:getBackgroundChecksByCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: getBackgroundChecksByCandidateResponse

updateBackgroundCheck Element:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 40

Operation type: Request-response.
 The endpoint receives a message to update an existing backgroundcheck instance, and
sends a correlated message only if error occurred.
 Please Note: Update requests replace all data fields in the backgroundCheckBean (i.e.
data is not appended or upserted). Send all elements back or the field values will be
returned NULL.

Input:updateBackgroundCheckRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
ID
candidateID
flexValues []
candidateId *
checkerName *
in1 backgroundCheckBean *
checkerPhone
checkerEmail
comments *
status
creator

Output: updateBackgroundCheckResponse

Data Field Name Data Field Type Required Acceptable Values

updateBackgroundCheckReturn

updateBackgroundCheck Test Case:

Input: updateBackgroundCheckRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateBackgroundCheck>
<in0>webapi1673199911353581754</in0>
<in1>
<id>4</id>
<status>Submitted</status>
<candidateId>48</candidateId>
<checkerEmail>[email protected]</checkerEmail>
<checkerName>Intellius</checkerName>
<checkerPhone>323-434-3434</checkerPhone>
<comments>Package 8</comments>
<creator>skarim</creator>
</in1>
</urn:updateBackgroundCheck>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 41

</soapenv:Body>
</soapenv:Envelope>

Input: updateBackgroundCheckRequest

Candidate API Calls

Candidates are all of the people you want to track in Taleo Business Edition who are (either)
applicants, employee referrals, sourced prospects, agency submissions, etc.

candidateBean Definition:

Data Field Name Data Field Type Required Acceptable Values

Id long Candidate’s unique
server side ID. Can be
obtained by searching
Read Only the candidate
database or by
creating a new
candidate.
status String Yes Candidate’s Status
name from pick list
firstName String No First name
middleInitial String No Middle name
lastName String Yes Last name
address String No Street portion of
mailing address
city String No City name
zipCode String No ZIP or postal code
state String No State, region or
province name from
pick list
country String No Country code from
pick list
email String Yes Candidate’s email
address

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 42

phone String No Phone number
cellPhone String No Mobile phone number
source String No Candidate’s Source
name from pick list
submittedBy String No Login name of agency
which has submitted
this candidate
referredBy String No Name of the
employee who has
referred this candidate
legalStatus String No Candidate’s legal
status name from pick
list
gender String No Gender name from
pick list
race String No Race name from pick
list
veteran String No Veteran status name
from pick list
rank int No Candidate’s rank
based on ranking
criteria
hiredDate Date No Date of hire
startDate Date No Start of employment
date
textResume String No Text resume and/or
cover letter
resumeFileName String Read Only Binary resume file
name
reasonRejected String No Candidate’s reason
for rejection from pick
list
cwsPassword String No Password chosen on
Careers Web Site
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
flexValues FlexFieldBean[] No Array of flexible
(custom) field values
birthDate encryptedDate No *** ACCESSIBLE
WITHIN FLEX FIELD
BEAN
ssn encryptedString No *** ACCESSIBLE
WITHIN FLEX FIELD
BEAN

candidateDetailsBean Definition:
(This object is used to fetch detailed candidate information, including related objects)

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 43

Data Field Name Data Field Type Required Acceptable Values
candidateBean candidateBean [] Yes Candidate information
requisitionBean requisitionBean[] No Requisitions
associated with the
candidate
interviewBean interviewBean[] No Interviews associated
with the candidate
referenceBeans referenceBean[] No References
associated with the
candidate
historyBean historyBean[] No History records
associated with the
candidate
attachmentBean attachmentBean[] No Attachments
associated with the
candidate
offerBean offerBean [] No Offers associated with
the candidate

flexFieldBean Definition:

createCandidate Element:
Operation type: Request-response.
 The endpoint receives a message to create a candidate, and sends a correlated
message of candidate ID.

Input:createCandidateRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 44

flexValues []
status *
address
cellPhone
city
country
email *
firstName
gender
hiredDate
lastName *
legalStatus
middleInitial
password
in1 candidateBean[] * phone
race
rank
reasonRejected
referredBy
resumeFileName
source
startDate
state
submittedBy
textResume
veteren
zipCode
ssn
dateofbirth

Output: createCandidateResponse

Data Field Name Data Field Type Required Acceptable Values

Provided Candidate
createCandidateReturn Long Yes
ID

createCandidate Test Case:

Input:createCandidateRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 45

<fieldName>ssn</fieldName>
<valueStr>23423452</valueStr>
</item>
<item>
<fieldName>birthdate</fieldName>
<valueDate>2009-10-01T23:01:26.493Z</valueDate>
</item>
</flexValues>
<status>Hired</status>
<address>2323 Macaroni Road</address>
<cellPhone>999-343-2344</cellPhone>
<city>Jason</city>
<country>US-CA</country>
<email>[email protected]</email>
<firstName>Jessica</firstName>
<gender>Choose Not to Disclose</gender>
<hiredDate>2009-09-04T18:33:50.830Z</hiredDate>
<lastName>Karim</lastName>
<legalStatus>My status to work in this country is unknown</legalStatus>
<middleInitial>H</middleInitial>
<password>jason</password>
<phone>748-232-2323</phone>
<race>Hispanic or Latino</race>
<rank>100</rank>
<reasonRejected>Position was canceled</reasonRejected>
<referredBy>skarim</referredBy>
<source>Other</source>
<startDate>2009-09-04T18:33:50.830Z</startDate>
<state>US-CA</state>
<submittedBy>skarim</submittedBy>
<textResume>Skilled in after school specials</textResume>
<veteran>Armed Forces Service Medal Veterans</veteran>
<zipCode>93045</zipCode>
</in1>
</urn:createCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: createCandidateResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 46

deleteCandidate Element:
Operation type: Request-response.
 The endpoint receives a message to delete a candidate, and sends a correlated
message only if error occurred.

Input: deleteCandidateRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Candidate ID Yes ID of Candidate

Output: deleteCandidateResponse

Data Field Name Data Field Type Required Acceptable Values

deleteCandidateReturn

deleteCandidate Test Case:

Input: deleteCandidateRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteCandidate>
<in0>webapi1964799883250105794</in0>
<in1>46</in1>
</urn:deleteCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteCandidateResponse

getCandidateById Element:
Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 47

 The endpoint receives a message to get a candidate general information by ID, and
sends a correlated message of Candidate information.
 For full candidate details, including offers, references, attachments, etc., use
getCandidateDetailsById call.

Input: getCandidateByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Candidate ID Yes ID of Candidate

Output: getCandidateByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getCandidateByIdReturn candidateBean

getCandidateById Test Case:

Input: getCandidateByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getCandidateById>
<in0>webapi-7865850650124675561</in0>
<in1>48</in1>
</urn:getCandidateById>
</soapenv:Body>
</soapenv:Envelope>

Output: getCandidateByIdResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 48

<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr/>
</item>
<item>
<fieldName>birthdate</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName/>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>Associates Degree</valueStr>
</item>
<item>
<fieldName>Other (Specify Source)</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr/>
</item>
<item>
<fieldName>Current Salary</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>ssn</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
</flexValues>
<id>48</id>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 49

<lastUpdated>2009-09-04T18:33:46.463Z</lastUpdated>
<status>NEW</status>
<address>12016 194 B Street</address>
<cellPhone/>
<city>Pitt Meadows</city>
<country>Canada</country>
<email>[email protected]</email>
<firstName>Alisha</firstName>
<gender>Female</gender>
<hiredDate xsi:nil="true"/>
<lastName>Smith</lastName>
<legalStatus>I am authorized to work in this country for any employer</legalStatus>
<middleInitial>Alexandra</middleInitial>
<password>basketball</password>
<phone>6043754603</phone>
<race>Asian (not Hispanic or Latino)</race>
<rank>0</rank>
<reasonRejected xsi:nil="true"/>
<referredBy xsi:nil="true"/>
<resumeFileName>resume_48.docx</resumeFileName>
<source>Careers Website</source>
<startDate xsi:nil="true"/>
<state>US-AL</state>
<submittedBy xsi:nil="true"/>
<textResume/>
<veteran>Armed Forces Service Medal Veterans</veteran>
<zipCode>60606</zipCode>
</getCandidateByIdReturn>
</getCandidateByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getCandidateDetailsById Element:
Operation type: Request-response.
 The endpoint receives a message to get candidate detailed information by ID, and sends
a correlated message of detail Candidate information.
 For general candidate record details, use getCandidateById call.

Input: getCandidateDetailsByIdRequest

Data Field Name Data Field Type Required Acceptable Values

in0 String Yes Session ID
in1 candidateId - Long Yes Candidate ID
in2 includeRequisitions – Yes True
Boolean False
in3 includeInterviews – Yes True
Boolean False

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 50

in4 includeReferences – Yes True
Boolean False
in5 includeHistory – Boolean Yes True
False
in6 includeAttachments – Yes True
Boolean False
in7 includeOffers - Boolean Yes True
False

Output: getCandidateDetailsByIdResponse

Required Acceptable
Data Field Name Data Field Type
Values
getCandidateDetailsByIdReturn candidateDetailsBean

getCandidateDetailsById Test Case:

Input: getCandidateDetailsByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getCandidateDetailsById>
<in0>webapi-1081039353966410322</in0>
<in1>48</in1>
<in2>True</in2>
<in3>True</in3>
<in4>True</in4>
<in5>True</in5>
<in6>True</in6>
<in7>True</in7>
</urn:getCandidateDetailsById>
</soapenv:Body>
</soapenv:Envelope>

Output: getCandidateDetailsByIdResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 51

<creationDate>2009-09-04T18:39:26.620Z</creationDate>
<emailText>From: [email protected]
To: [email protected]
Subject: Thank you

Thank you for submitting your resume. Our management team is reviewing your
qualifications and will contact you if there is a match with our current open positions.

Meanwhile, using your email address and password, you can login to our careers website
anytime to update your application information.

We appreciate your interest in TaleoSK and wish you the best of luck in your job search.

-------------------------------
Powered by Taleo
www.taleo.com</emailText>
<id>542</id>
<text>Email message Thank you sent to [email protected]</text>
<userName xsi:nil="true"/>
</item>
<item>
<creationDate>2009-09-04T18:34:46.883Z</creationDate>
<emailText xsi:nil="true"/>
<id>528</id>
<text>Candidate (id: 48) (id: 48) Alisha Alexandra Smith has been evaluated
against requisition (id: 14) (id: 14) Bartender - [98079] for a score of: 0.</text>
<userName xsi:nil="true"/>
</item>
</historyBeans>
<interviewBeans xmlns=""/>
<referenceBeans xmlns=""/>
<attachmentBeans xmlns="">
<item>
<contentType>text/plain</contentType>
<creationDate>2009-09-09T23:43:40.050Z</creationDate>
<description>ConCall Details.txt</description>
<id>4</id>
</item>
</attachmentBeans>
<requisitionBeans xmlns="">
<item>
<creationDate>2009-02-09T23:03:51.430Z</creationDate>
<flexValues>
</flexValues>
<id>11</id>
<lastUpdated>2009-02-18T22:22:18.317Z</lastUpdated>
<status>Open</status>
<city>Dublin</city>
<description><![CDATA[The Pre-Sales Engineer, reporting to the Canadian
Delivery Manager, will be responsible for providing solution architect support to our

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 52

client's services sales and pre-sales teams. Solutions are primarily in the area of
Electronic Content Management, Imaging and Document Process Outsourcing. 
 
This is a role intended to extend the governance of the Delivery organization into the pre-
sales area. This resource will be responsible for defining and validating solutions to be
proposed to new and existing customers. 
 ]]></description>
<duration>FULLTIME</duration>
<filledDate xsi:nil="true"/>
<jobCategory>(2) Professionals</jobCategory>
<jobCode>12345</jobCode>
<location>Headquarters</location>
<numOpen>1</numOpen>
<openedDate>2009-02-09T00:00:00.000Z</openedDate>
<payRange/>
<state>US-CA</state>
<title>Sales Engineer</title>
</item>
</requisitionBeans>
<candidateBean xmlns="">
<creationDate>2009-09-04T18:33:46.463Z</creationDate>
<flexValues>
<item>
<fieldName>Current Salary</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
</flexValues>
<id>48</id>
<lastUpdated>2009-09-04T18:33:46.463Z</lastUpdated>
<status>NEW</status>
<address>12032 194 B Street</address>
<cellPhone/>
<city>Pitt Meadows</city>
<country>Canada</country>
<email>[email protected]</email>
<firstName>Alisha</firstName>
<gender>Female</gender>
<hiredDate xsi:nil="true"/>
<lastName>Smith</lastName>
<legalStatus>I am authorized to work in this country for any
employer</legalStatus>
<middleInitial>Alexandra</middleInitial>
<password>basketball</password>
<phone>6043754606</phone>
<resumeFileName>resume_48.docx</resumeFileName>
<source>Careers Website</source>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 53

<startDate xsi:nil="true"/>
<state>US-AL</state>
<submittedBy xsi:nil="true"/>
<textResume/>
<veteran>Armed Forces Service Medal Veterans</veteran>
<zipCode>60606</zipCode>
</candidateBean>
</getCandidateDetailsByIdReturn>
</getCandidateDetailsByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getCandidateHistory Element:
Operation type: Request-response.
 The endpoint receives a message to get a Candidate transaction history, and sends a
correlated message of transaction history for the specific candidate ID.
 This object is used to fetch a history log entry which reflects a past event or action related
to candidates. History records can only be created by the server, they cannot be modified
or deleted. History log includes server side ID, test describing history record, complete
text of email message (for email events) and creation date.

Input: getCandidateHistoryRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Candidate ID Yes ID of Candidate

Output: getCandidateHistoryResponse

Data Field Name Data Field Type Required Acceptable Values

getCandidateHistoryReturn historyBean []

getCandidateHistory Test Case:

Input: getCandidateHistoryRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getCandidateHistory>
<in0>webapi-1081039353966410322</in0>
<in1>43</in1>
</urn:getCandidateHistory>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 54

Output: getCandidateHistoryResponse

getCandidatesByRequisition Element:
Operation type: Request-response.
 The endpoint receives a message to get all candidates by Requisition ID, and sends a
correlated message of Candidate IDs associated with a specific requisition.

Input: getCandidatesByRequisitionRequest

Data Field Name Data Field Type Required Acceptable Values

in0 String Yes Session ID
in1 String Yes Requisition ID

Output: getCandidatesByRequisitionResponse

Required Acceptable
Data Field Name Data Field Type
Values

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 55

getCandidatesByRequisitionReturn candidate ID(s)

getCandidatesByRequisition Test Case:

Input: getCandidatesByRequisitionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getCandidatesByRequisition>
<in0>webapi-1081039353966410322</in0>
<in1>14</in1>
</urn:getCandidatesByRequisition>
</soapenv:Body>
</soapenv:Envelope>

Output: getCandidatesByRequisitionResponse

getCandidateWorkHistory Element:
Operation type: Request-response.
 The endpoint receives a message to get the rolling entity specific to a candidate’s work
history form details, and sends a correlated message of work history information.
 The getRollingEnitities request can also be used.
 This is a manually filled in dynamic form that may not be activated in some customer
zones (i.e. configured ON).

Input: getCandidateWorkHistoryRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 56

Data Field Name Data Field Type Required Acceptable Values
Session ID received
sessionId String Yes
at Login
candidateId Long Yes ID of Candidate

Output: getCandidateWorkHistoryResponse

Required Acceptable
Data Field Name Data Field Type
Values
candidateWorkHistoryBean
getCandidateWorkHistoryReturn
[]

getCandidateWorkHistory Test Case:

Input: getCandidateWorkHistoryRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getCandidateWorkHistory>
<sessionId>webapi-1081039353966410322</sessionId>
<candidateId>48</candidateId>
</urn:getCandidateWorkHistory>
</soapenv:Body>
</soapenv:Envelope>

Output: getCandidateWorkHistoryResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 57

<lastUpdated>2009-09-04T18:33:46.463Z</lastUpdated>
<status xsi:nil="true"/>
<entityId>48</entityId>
<seqNo>2</seqNo>
<jobTitle>Dr</jobTitle>
<companyName/>
<dateFrom>2009-07-01T00:00:00.000Z</dateFrom>
<dateTo>2009-09-01T00:00:00.000Z</dateTo>
<jobDescription/>
<companyStreetAddress/>
<companyCityState/>
<phone/>
<directSupervisor/>
<supervisorTitle/>
<explanation/>
<finalRateOfPay/>
<okToContact>false</okToContact>
<reasonForLeaving>Terminated</reasonForLeaving>
</item>
<item>
<creationDate>2009-09-04T18:33:46.463Z</creationDate>
<flexValues>
<item>
<fieldName>Starting Rate Of Pay</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
</flexValues>
<id>27</id>
<lastUpdated>2009-09-04T18:33:46.463Z</lastUpdated>
<status xsi:nil="true"/>
<entityId>48</entityId>
<seqNo>1</seqNo>
<jobTitle>Dr.</jobTitle>
<companyName/>
<dateFrom>2005-01-01T00:00:00.000Z</dateFrom>
<dateTo>2009-06-01T00:00:00.000Z</dateTo>
<jobDescription/>
<companyStreetAddress/>
<companyCityState/>
<phone/>
<directSupervisor/>
<supervisorTitle/>
<explanation/>
<finalRateOfPay/>
<okToContact>false</okToContact>
<reasonForLeaving xsi:nil="true"/>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 58

</item>
</array>
</getCandidateWorkHistoryReturn>
</getCandidateWorkHistoryResponse>
</soapenv:Body>
</soapenv:Envelope>

getCandReqStatus Element:
Operation type: Request-response.
 The endpoint receives a message to get a status of a requisition for a particular
candidate, and sends a correlated message of the candidate’s specific requisition status.
 Candidate Requisition Status is picklist created and derived from Taleo Business Edition.

Input: getCandReqStatusRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of Candidate
in2 Long Yes ID of requisition

Output: getCandReqStatusResponse

Data Field Name Data Field Type Required Acceptable Values

Candidate Requisition
getCandReqStatusReturn Long
Status Picklist Values

getCandReqStatus Test Case:

Input: getCandReqStatusRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getCandReqStatus>
<in0>webapi-1081039353966410322</in0>
<in1>48</in1>
<in2>13</in2>
</urn:getCandReqStatus>
</soapenv:Body>
</soapenv:Envelope>

Output: getCandReqStatusResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 59

getRequisitions Element:
Operation type: Request-response.
 The endpoint receives a message to get requisition(s) associated with any Taleo
Business Edition candidate, and sends back requisition IDs associated with the candidate
ID.

Input: getRequisitionsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of candidate

Output: getRequisitionsResponse

Data Field Name Data Field Type Required Acceptable Values

getRequisitionsReturn array of requisition IDs

getRequisitions Test Case:

Input: getRequisitionsRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getRequisitions>
<in0>webapi-8638387102069848283</in0>
<in1>48</in1>
</urn:getRequisitions>
</soapenv:Body>
</soapenv:Envelope>

Output: getRequisitionsResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 60

searchCandidate Element:
Operation type: Request-response.
 The endpoint receives a message to query all candidates based on defined key (field
name) and value (data looking for), and sends a correlated message of Candidate ID and
associated search relevance.
 Relevance is a value between 0 and 100, which reflects how well the account matches
the search criteria
 Map of search parameters always contains:
o key: name of field to search as a string
o value: search parameter as string.
 Format of search value may differ depending on data type of the search field:
 For text, text area, email, URL fields: simple text to be found (case-insensitive) in this
field. Example:
o key=”city”, value=”Francisco” will search for all candidates with ”Francisco” in
“city” field.
 For integer, double, currency: interval between two numbers separated by ‘|’ character.
Either left (from) or right (to) side can be omitted. Example:
o key=”rank”, value=”100|” will search for all candidates with rank value no less
than 100.
o key=”rank”, value=”|200” will search for all candidates with rank value no more
than 200.
o key=”rank”, value=”100|200” will search for all candidates with rank value
between 100 and 200 (inclusive).
 For date fields: interval between two dates in ISO yyyy-MM-dd format, separated by ‘|’
character. Either left (from) or right (to) side can be omitted. Example:
o key=”startDate”, value=”2004-06-01|” will search for all candidates with start date
on or after June 1st 2004.
o key=”startDate”, value=”|2004-08-01” will search for all candidates with start date
on or before August 1st 2004.
o key=”startDate”, value=”2004-06-01|2004-08-01” will search for all candidates
with start date between June 1st 2004 and August 1st 2004 (inclusive).
 For date interval fields: number of days from today to the past. Example:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 61

o key=” addedWithin”, value=”7” will search for all candidates added to the system
within the last week.
 For single pick list: code value or name of selected item. Example:
o key=”country”, value=”US” will search for all candidates with country field equals
to “United States”.
o key=”status”, value=”available” will search for all candidates in “Available” status.
 For multiple pick list: code values or names of selected items, separated by ‘|’ character.
Example:
o key=”customMultiple”, value=”A1|B2|X5” will search for all candidates with
customMultiple field containing one or more of values: A1, B2, X5.
 For check box fields: “true” if check box must be checked, “false” is unchecked. Example:
o key=” flagged”, value=”true” will search for all candidates “flagged” for the user
currently logged in.
 Search keys names and types can be found in Administration>Customize>Candidate
Fields. They may include both system fields (listed below for convenience) and custom
fields. For custom fields External name is used as key name.

System Search Keys:

Data Field Name Parameter Type Description

Keyword(s) in candidate’s resume.
keyword String Identical syntax as used in Taleo browser
interface
candid Integer ID of candidate
firstName String First name
lastName String Last name
middleInitial String Middle name
address String Street address
city String City
state Pick list State/Region
zipCode String ZIP/Postal code
country Pick list Country name
phone String Phone #
cellPhone String Mobile #
phoneAll String Any phone
email String Email
legalStatus Pick list Legal status
status Pick list Status name
source Pick list Source name
lastUpdated Date Last updated date
creationDate Date Added to system date
gender Pick list Gender
race Pick list Race name
veteran Pick list Veteran/Disability
rank Integer Rank (%)
referredBy String Referred By
Ids of requisitions (‘|’ – separated) this
requisitions Custom
candidate is submitted to
addedWithin Integer Added within N days

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 62

updatedWithin Integer Updated within N days
flagged Check Box Flagged candidates only
reasonRej Pick list Reason for rejection
hiredDate Date Hired date
startDate Date Start date
intStatus String Supported value: “hired”

Input: searchCandidateRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
key
in1 Item… Yes
value

Output: searchCandidateResponse

Data Field Name Data Field Type Required Acceptable Values

searchCandidateReturn searchResultBean []

searchCandidate Test Case:

Input: searchCandidateRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:searchCandidate>
<in0>webapi-1081039353966410322</in0>
<in1>

<item>
<key>country</key>
<value>Canada</value>
</item>
</in1>
</urn:searchCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: searchCandidateResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 63

submitCandidate Element:
Operation type: Request-response.
 The endpoint receives a message to submit a candidate to a requisition(s), and sends a
correlated message only if error occured.
 Please Note: Submit requests replace all previous requisitions that the candidate has
been tied too previously (i.e. data is not appended or upserted). Send all previous
requisitions back if simply adding an additional requisition or use
upsertCandidateToRequisitions call.

Input: submitCandidateRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of Candidate
Array of requisition
in2 Long Yes
IDs

Output: submitCandidateResponse

Data Field Name Data Field Type Required Acceptable Values

submitCandidateReturn

submitCandidate Test Case:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 64

Input: submitCandidateRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:submitCandidate>
<in0>webapi-1081039353966410322</in0>
<in1>48</in1>
<in2>
<array>

<item>15</item>
</array>
</in2>
</urn:submitCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: submitCandidateResponse

removeCandidate Element:
Operation type: Request-response.
 The endpoint receives a message to remove an existing candidate assignment from a
requisition (both based on ID variables), and sends a correlated message only if error
occurred.

Input: removeCandidateRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes Candidate ID
in2 Long Yes Requisition ID

Output: removeCandidateResponse

Data Field Name Data Field Type Required Acceptable Values

removeCandidateReturn

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 65

removeCandidate Test Case:

Input: removeCandidateRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:removeCandidate>
<in0>webapi-3736131371583618769</in0>
<in1>48</in1>
<in2>15</in2>
</urn:removeCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: removeCandidateResponse

updateCandidate Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing candidate, and sends a
correlated message only if error occurred.
 Please Note: Update requests replace all data fields in the candidateBean (i.e. data is not
appended or upserted). Send all elements back or the field values will be returned NULL.

Input:updateCandidateRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
id
status *
in1 candidateBean[] *
address
cellPhone
city

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 66

country
email *
firstName
gender
hiredDate
lastName *
legalStatus
middleInitial
password
phone
race
rank
reasonRejected
referredBy
resumeFileName
source
startDate
state
submittedBy
textResume
veteren
zipCode

Output: updateCandidateResponse

Data Field Name Data Field Type Required Acceptable Values

updateCandidateReturn

updateCandidate Test Case:

Input: updateCandidateRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateCandidate>
<in0>webapi6675924402134546238</in0>
<in1>
<flexValues>

</flexValues>
<Id>48</Id>
<status>Hired</status>
<address>2323 Macaroni Road</address>
<city>Jason</city>
<country>US-CA</country>
<email>[email protected]</email>
<firstName>Jessica</firstName>
<gender>Choose Not to Disclose</gender>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 67

<hiredDate>2009-09-04T18:33:50.830Z</hiredDate>
<lastName>Karim</lastName>
<legalStatus>My status to work in this country is unknown</legalStatus>
<middleInitial>H</middleInitial>
<password>jason</password>
<cellPhone>892-232-2334</cellPhone>
<phone>748-232-2323</phone>
<race>Hispanic or Latino</race>
<rank>100</rank>
<reasonRejected>Position was canceled</reasonRejected>
<referredBy>skarim</referredBy>
<source>Other</source>
<startDate>2009-09-04T18:33:50.830Z</startDate>
<state>US-CA</state>
<submittedBy>skarim</submittedBy>
<textResume>Skilled in after school specials</textResume>
<veteran>Armed Forces Service Medal Veterans</veteran>
<zipCode>93045</zipCode>
</in1>
</urn:updateCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: updateCandidateResponse

upsertCandidateToRequisitions Element:

Operation type: Request-response.

 The endpoint receives a message to upsert, or append a candidate to a requisition, and
sends a correlated message only if error occured.
 Please Note: Definition of client-side statusIDs and reasonIDs will be needed when
passing these attributes (descriptive text is not supported).
 Please Note: ReasonIDs are required when a ‘Rejected’ Status ID has been selected.
 Please Note: doRanking element is Boolean True/False, which forces the system to
recalculate the candidate’s rank for that requisition on upsert.

 Please Note: As each client may be able to customize status and reasons, a standard list
of ID’s has not been provided. The easiest way to find a client’s status and reason IDs is
to go into the application and:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 68

o Select a candidate
o Attach the candidate to any requisition at the top of the screen
o Select ‘Rejected’ under the ‘Requisition-specific status:’ picklist
o When the ‘Requisition-specific reason for rejection:’ picklist appears, right click
the page and select ‘View Source’.
o From here you will find a list of appropriate ID values for both sources (sourceID)
and reasons (reasonID).

Input: upsertCandidateToRequisitionsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
sessionId String Yes
at Login
candidateId Long Yes ID of Candidate
Array of requisition
requistionIds LongArr Yes
IDs

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 69

ID of status or
statusId Long Yes requisition-specific
status ID
ID of reasonRej or
Yes if statusID =
reasonId Long requisition rejected
“Rejected”
status ID
True
doRanking Boolean No
False

Output: upsertCandidateToRequisitionsResponse

Required Acceptable
Data Field Name Data Field Type
Values
upsertCandidateToRequisitionsReturn

upsertCandidateToRequisitions Test Case:

Input: upsertCandidateToRequisitionsRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:upsertCandidateToRequisitions>
<sessionId>webapi-1081039353966410322</sessionId>
<candidateId>48</candidateId>
<requisitionIds>
<array>

<item>15</item>
</array>
</requisitionIds>
<statusId>14</statusId>
<reasonId>476</reasonId>
<doRanking>True</doRanking>
</urn:upsertCandidateToRequisitions>
</soapenv:Body>
</soapenv:Envelope>

Output: upsertCandidateToRequisitionsResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 70

Contact API Calls
Contacts are all of the individuals associated with your Accounts that you need to track in Taleo
Business Edition.

contactBean Definition:

Data Field Name Data Field Type Required Acceptable Values

Contact’s unique
server side ID. Can be
obtained by searching
ID Long Read Only the accounts’
database or by
creating a new
account.
status String Yes Contact’s Status from
pick list
firstName String No Contact’s first name
lastName String Yes Contact’s first name
accounted long No ID of parent account
title String No Contact’s title
department String No Contact’s department
reportsToId long No ID of parent contact
phone String No Phone number
cellPhone String No Cell phone number
fax String No Fax number
email String No Email address
assistantName String No Assistant’s name
assistantPhone String No Assistant’s phone
assistantEmail String No Assistant’s email
address String No Street portion of
mailing address
city String No City name
zipCode String No ZIP or postal code
state String No State, region or
province name from
pick list
country String No Country code from
pick list
description String No Contact’s description
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
flexValues FlexFieldBean[] No Array of flexible

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 71

(custom) field values

flexFieldBean Definition:

createContact Element:
Operation type: Request-response.
 The endpoint receives a message to create a contact, and sends a correlated message
of contact ID.
 Using accountID element allows the contact to be tied to a specific Account.

Input:createContactRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status
accountId
address
assistantEmail
assistantName
assistantPhone
cellPhone
city
contactType
in1 contactBean[] *
country
department
description
email
fax
firstName
lastName *
phone
reportsToId
state

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 72

title
zipCode

Output: createContactResponse

Data Field Name Data Field Type Required Acceptable Values

createContactReturn Long Yes Provided Contact ID

createContact Test Case:

Input: createContactRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createContact>
<in0>webapi6675924402134546238</in0>
<in1>
<flexValues>

</flexValues>
<accountId>2</accountId>
<address>82 Taleo Drive</address>
<assistantEmail>[email protected]</assistantEmail>
<assistantName>Shakir Karim</assistantName>
<assistantPhone>604-761-0087</assistantPhone>
<cellPhone>604-920-3949</cellPhone>
<city>Dublin</city>
<contactType>?</contactType>
<country>United States</country>
<department>Sales</department>
<description>Head of Partners and Alliances</description>
<email>[email protected]</email>
<fax>604-323-2323</fax>
<firstName>Don</firstName>
<lastName>Darrah</lastName>
<phone>583-903-3434</phone>
<state>US-CA</state>
<title>Manager</title>
<zipCode>90210</zipCode>
</in1>
</urn:createContact>
</soapenv:Body>
</soapenv:Envelope>

Output: createContactResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 73

deleteContact Element:
Operation type: Request-response.
 The endpoint receives a message to delete a contact, and sends a correlated message
only if error occurred.

Input: deleteContactRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Contact ID Yes ID of Contact

Output: deleteContactResponse

Data Field Name Data Field Type Required Acceptable Values

deleteContactReturn

deleteContact Test Case:

Input: deleteContactRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteContact>
<in0>webapi6675924402134546238</in0>
<in1>1</in1>
</urn:deleteContact>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteContactResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 74

getContactById Element:
Operation type: Request-response.
 The endpoint receives a message to get a contact details, and sends a correlated
message of Contact information.

Input: getContactByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Contact ID Yes ID of Contact

Output: getContactByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getContactByIdReturn contactBean []

getContactById Test Case:

Input: getContactByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getContactById>
<in0>webapi6675924402134546238</in0>
<in1>1</in1>
</urn:getContactById>
</soapenv:Body>
</soapenv:Envelope>

Output: getContactByIdResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 75

<soapenv:Body>
<getContactByIdResponse xmlns="urn:TBEWebAPI">
<getContactByIdReturn xmlns="">
<creationDate>2009-08-21T22:04:14.597Z</creationDate>
<flexValues/>
<id>1</id>
<lastUpdated>2009-08-21T22:09:35.259Z</lastUpdated>
<status xsi:nil="true"/>
<accountId>2</accountId>
<address>82 Taleo Drive</address>
<assistantEmail>[email protected]</assistantEmail>
<assistantName>Sonia Jason</assistantName>
<assistantPhone>604-894-9487</assistantPhone>
<cellPhone>604-920-3949</cellPhone>
<city>Dublin</city>
<contactType xsi:nil="true"/>
<country>United States</country>
<creator xsi:nil="true"/>
<department>Sales</department>
<description>Head of Partners and Alliances</description>
<email>[email protected]</email>
<fax>604-323-2323</fax>
<firstName>Don</firstName>
<lastName>Darrah</lastName>
<phone>583-903-3434</phone>
<reportsToId>0</reportsToId>
<state>US-CA</state>
<title>Manager</title>
<zipCode>90210</zipCode>
</getContactByIdReturn>
</getContactByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getContactHistory Element:

Operation type: Request-response.

 The endpoint receives a message to get a Contact transaction history, and sends a
correlated message of transaction history for contact information.
 This object is used to fetch a history log entry which reflects a past event or action related
to contacts. History records can only be created by the server, they cannot be modified or
deleted. History log includes server side ID, test describing history record, complete text
of email message (for email events) and creation date.

Input: getContactHistoryRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 76

in1 Contact ID Yes ID of Contact

Output: getContactHistoryResponse

Data Field Name Data Field Type Required Acceptable Values

getContactHistoryReturn historyBean []

getContactHistory Test Case:

Input: getContactHistoryRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getContactHistory>
<in0>webapi-2722388699079508905</in0>
<in1>2</in1>
</urn:getContactHistory>
</soapenv:Body>
</soapenv:Envelope>

Output: getContactHistoryResponse

searchContact Element:

Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 77

 The endpoint receives a message to query all contacts based on defined key (field name)
and value (data looking for), and sends a correlated message of Contact ID and
associated search relevance.
 Relevance is a value between 0 and 100, which reflects how well the account matches
the search criteria
 Map of search parameters always contains:
o key: name of field to search as a string
o value: search parameter as string.
 Format of search value may differ depending on data type of the search field:
 For text, text area, email, URL fields: simple text to be found (case-insensitive) in this
field. Example:
o key=”city”, value=”Francisco” will search for all candidates with ”Francisco” in
“city” field.
 For integer, double, currency: interval between two numbers separated by ‘|’ character.
Either left (from) or right (to) side can be omitted. Example:
o key=”rank”, value=”100|” will search for all candidates with rank value no less
than 100.
o key=”rank”, value=”|200” will search for all candidates with rank value no more
than 200.
o key=”rank”, value=”100|200” will search for all candidates with rank value
between 100 and 200 (inclusive).
 For date fields: interval between two dates in ISO yyyy-MM-dd format, separated by ‘|’
character. Either left (from) or right (to) side can be omitted. Example:
o key=”startDate”, value=”2004-06-01|” will search for all candidates with start date
on or after June 1st 2004.
o key=”startDate”, value=”|2004-08-01” will search for all candidates with start date
on or before August 1st 2004.
o key=”startDate”, value=”2004-06-01|2004-08-01” will search for all candidates
with start date between June 1st 2004 and August 1st 2004 (inclusive).
 For date interval fields: number of days from today to the past. Example:
o key=” addedWithin”, value=”7” will search for all candidates added to the system
within the last week.
 For single pick list: code value or name of selected item. Example:
o key=”country”, value=”US” will search for all candidates with country field equals
to “United States”.
o key=”status”, value=”available” will search for all candidates in “Available” status.
 For multiple pick list: code values or names of selected items, separated by ‘|’ character.
Example:
o key=”customMultiple”, value=”A1|B2|X5” will search for all candidates with
customMultiple field containing one or more of values: A1, B2, X5.
 For check box fields: “true” if check box must be checked, “false” is unchecked. Example:
o key=” flagged”, value=”true” will search for all candidates “flagged” for the user
currently logged in.
 Search keys names and types can be found in Administration>Customize>Contact
Fields. They may include both system fields (listed below for convenience) and custom
fields. For custom fields External name is used as key name.

System Search Keys:

Data Field Name Parameter Type Description

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 78

Keyword(s) in contact’s description.
keyword String Identical syntax as used in Taleo browser
interface.
firstName String Contact’s first name
lastName String Contact’s last name
accountId String ID of parent account
title String Contact’s title
department String Department
reportsToId String ID of parent contact
phoneAll String Any contact’s phone number
email String Email address
city Pick list City name
State, region or province name from pick
state String
list
country String Country code from pick list
addedWithin Integer Added within N days
updatedWithin Integer Updated within N days

Input: searchContactRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
key
in1 Item… Yes
value

Output: searchContactResponse

Data Field Name Data Field Type Required Acceptable Values

searchContactReturn searchResultBean []

searchContact Test Case:

Input: searchContactRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:searchContact>
<in0>webapi6675924402134546238</in0>
<in1>

<item>
<key>description</key>
<value>Partners</value>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 79

</item>
</in1>
</urn:searchContact>
</soapenv:Body>
</soapenv:Envelope>

Output: searchContactResponse

updateContact Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing contact, and sends a correlated
message only if error occurred.
 Please Note: Update requests replace all data fields in the contactBean (i.e. data is not
appended or upserted). Send all elements back or the field values will be returned NULL.

(**) PLEASE NOTE, KNOWN BUG FOR <CREATOR> FIELD: (BUG 10290): API overwrites
defined creator field with API logged in session userName value during integration.

Input:updateContactRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status
accountId *
in1 contactBean[] *
address
assistantEmail
assistantName

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 80

assistantPhone
cellPhone
city
contactType
country
department
description
email
fax
firstName
lastName *
phone
reportsToId
state
title
zipCode

Output: updateContactResponse

Data Field Name Data Field Type Required Acceptable Values

updateContactReturn

updateContact Test Case:

Input: updateContactRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateContact>
<in0>webapi6675924402134546238</in0>
<in1>
<flexValues>

</flexValues>
<accountId>2</accountId>
<address>82 Taleo Drive</address>
<assistantEmail>[email protected]</assistantEmail>
<assistantName>Sonia Jason</assistantName>
<assistantPhone>604-894-9487</assistantPhone>
<cellPhone>604-920-3949</cellPhone>
<city>Dublin</city>
<contactType>?</contactType>
<country>United States</country>
<department>Sales</department>
<description>Head of Partners and Alliances</description>
<email>[email protected]</email>
<fax>604-323-2323</fax>
<firstName>Don</firstName>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 81

<lastName>Darrah</lastName>
<phone>583-903-3434</phone>
<state>US-CA</state>
<title>Manager</title>
<zipCode>90210</zipCode>
</in1>
</urn:updateContact>
</soapenv:Body>
</soapenv:Envelope>

Output: updateContactResponse

Contact Log API Calls

Contact logs are a running trail of communication stored within a specific entity of Taleo Business
Edition. There is a one-to-many relationship with contact logs to entities. Entities include accounts
(ACCT), candidates (CAND), contacts (CTCT), employees (EMPL), requisitions (REQU) and
users (WORK).

contactLogBean Definition:

Data Field Data Field

Required Acceptable Values
Name Type
id long Read Only Contact log’s unique server side ID.
creator String Login name of user who has created this
Yes
record (**)
typeNo int Type of contact log:
1 = email
Yes
2 = phone call
3 = response
entityType String Type of related entity:
ACCT = accounts
CAND = candidates
Yes CTCT = contacts
EMPL = employees
REQU = requisitions
WORK = users
entityId long Yes ID of related entity

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 82

subject String Yes Log’s subject
comments String No Log’s comments or email body
contactDate Date No Contact date
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date

(**) PLEASE NOTE, KNOWN BUG FOR <CREATOR> FIELD: (BUG 9470): API overwrites
defined creator field with API logged in session userName value during integration.
createContactLog Element:
Operation type: Request-response.
 The endpoint receives a message to create a contact log, and sends a correlated
message of contact log ID.

Input: createContactLogRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
creator * (**)
typeNo *
entityType *
in1 contactLogBean[] * entityId *
subject *
comments
contactDate

Output: createContactLogResponse

Data Field Name Data Field Type Required Acceptable Values

Provided Contact Log
createContactLogReturn Long Yes
ID

createContactLog Test Case:

Input: createContactLogRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createContactLog>
<in0>webapi-1081039353966410322</in0>
<in1>
<comments>Unable to Get a Hold of Candidate</comments>
<contactDate>2009-06-30T23:01:26.493Z</contactDate>
<creator>skarim</creator>
<entityId>48</entityId>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 83

<entityType>CAND</entityType>
<subject>Phone Screen</subject>
<typeNo>2</typeNo>
</in1>
</urn:createContactLog>
</soapenv:Body>
</soapenv:Envelope>

Output: createContactLogResponse

deleteContactLog Element:
Operation type: Request-response.
 The endpoint receives a message to delete a contact log, and sends a correlated
message only if error occurred.

Input: deleteContactLogRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Contact Log ID Yes ID of Contact Log

Output: deleteContactLogResponse

Data Field Name Data Field Type Required Acceptable Values

deleteContactLogReturn

deleteContactLog Test Case:

Input: deleteContactLogRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 84

Output: deleteContactLogResponse

getContactLogById Element:
Operation type: Request-response.
 The endpoint receives a message to get a contact log details by contact log ID, and
sends a correlated message of contact log information.

Input: getContactLogByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Contact Log ID Yes ID of Contact Log

Output: getContactLogByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getContactLogByIdReturn contactLogBean []

getContactLogById Test Case:

Input: getContactLogByIdRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 85

</soapenv:Envelope>

Output: getContactLogByIdResponse

getContactLogsByEntity Element:
Operation type: Request-response.
 The endpoint receives a message to get contact log(s) associated with any Taleo
Business Edition entity that supports storing of contact logs, and sends back contact log
IDs associated with the entity ID.

Input: getContactLogsByEntity Request

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
Type of related entity:
ACCT = accounts
CAND = candidates
in1 Long Yes
EMPL = employees
REQU = requisitions
WORK = users
in2 Long Yes ID of associated entity

Output: getContactLogsByEntityResponse

Data Field Name Data Field Type Required Acceptable Values

getContactLogsByEntity array of contact log IDs

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 86

Return

getContactLogsByEntity Test Case:

Input: getContactLogsByEntity Request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getContactLogsByEntity>
<in0>webapi-6706128845720983299</in0>
<in1>CAND</in1>
<in2>48</in2>
</urn:getContactLogsByEntity>
</soapenv:Body>
</soapenv:Envelope>

Output: getContactLogsByEntityResponse

updateContactLog Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing contact log, and sends a
correlated message only if error occurred.
 Please Note: Update requests replace all data fields in the contactLogBean (i.e. data is
not appended or upserted). Send all elements back or the field values will be returned
NULL.

Input: updateContactLogRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 87

Data Field Name Data Field Type Required Acceptable Values
Session ID received
in0 String Yes
at Login
comments
contactDate
creator
entityId *
in1 contactLogBean[] *
entityType *
id *
subject *
typeNo *

Output: updateContactLogResponse

Data Field Name Data Field Type Required Acceptable Values

updateContactLogReturn

updateContactLog Test Case:

Input: updateContactLogRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateContactLog>
<in0>webapi-6706128845720983299</in0>
<in1>
<comments>Phone Interview was rescheduled</comments>
<contactDate>2009-06-30T23:01:26.493Z</contactDate>
<creator>destey</creator>
<entityId>48</entityId>
<entityType>CAND</entityType>
<id>4</id>
<subject>Interview</subject>
<typeNo>2</typeNo>
</in1>
</urn:updateContactLog>
</soapenv:Body>
</soapenv:Envelope>

Output: updateContactLogResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 88

</soapenv:Body>
</soapenv:Envelope>

Department API Calls

Department’s are organization cost centers used through your careers site and throughout your
Taleo Business Edition system.

departmentBean Definition:

Data Field Name Data Field Type Required Acceptable Values

Account’s unique
server side ID. Can be
obtained by searching
departmentId Long Read Only the accounts’
database or by
creating a new
account.
departmentNme String Yes Department’s name
defaultApprovers Long[] No Array of user ID’s

**Allows you to
identify which users
are assigned to this
Department
associatedUsers Long[] No Array of user ID’s

**Allows you to
identify which users
will be set as the
default Requisition
Approver for any
requisition created
within this Department
additionalProperties map No Used for expansion
calls
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date

createDepartment Element:
Operation type: Request-response.
 The endpoint receives a message to create a department, and sends a correlated
message of department ID.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 89

Input: createDepartmentRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
AdditionalProperties[]
departmentName
in1 departmentBean *
associatedUsers
defaultApprovers

Output: createDepartmentResponse

Data Field Name Data Field Type Required Acceptable Values

Provided Department
createDepartmentReturn Long Yes
ID

createDepartmentTest Case:

Input: createDepartmentRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createDepartment>
<sessionId>webapi-464745806681923416</sessionId>
<bean>
<departmentName>Sales Operations</departmentName>
<associatedUsers>

<item>2</item>
<item>5</item>
<item>19</item>
</associatedUsers>
<defaultApprovers>

<item>19</item>
<item>18</item>
</defaultApprovers>
</bean>
</urn:createDepartment>
</soapenv:Body>
</soapenv:Envelope>

Output: createDepartmentResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 90

deleteDepartment Element:
Operation type: Request-response.
 The endpoint receives a message to delete a department, and sends a correlated
message only if error occurred.

Input: deleteDepartmentRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Department ID Yes ID of Department

Output: deleteDepartmentResponse

Data Field Name Data Field Type Required Acceptable Values

deleteDepartmentReturn

deleteDepartment Test Case:

Input: deleteDepartmentRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteDepartment>
<sessionId>webapi-464745806681923416</sessionId>
<departmentId>13</departmentId>
</urn:deleteDepartment>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteDepartmentResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 91

getDepartmentById Element:
Operation type: Request-response.
 The endpoint receives a message to get a Department details, and sends a correlated
message of Department information.

Input: getDepartmentByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Department ID Yes ID of Department

Output: getDepartmentByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getDepartmentByIdReturn departmentBean

getDepartmentById Test Case:

Input: getDepartmentByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getDepartmentById>
<in0>webapi-464745806681923416</in0>
<in1>4</in1>
</urn:getDepartmentById>
</soapenv:Body>
</soapenv:Envelope>

Output: getDepartmentByIdResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 92

<getDepartmentByIdReturn>
<additionalProperties xmlns="">
<item xmlns:ns1="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string">19,18,</value>
</item>
</additionalProperties>
<creationDate xmlns="">2008-11-25T00:00:00.000Z</creationDate>
<departmentId xmlns="">4</departmentId>
<departmentName xmlns="">Customer Service</departmentName>
<lastUpdated xmlns="">2009-03-13T00:00:00.000Z</lastUpdated>
<associatedUsers xmlns="">
<item>2</item>
<item>5</item>
<item>19</item>
</associatedUsers>
<defaultApprovers xmlns="">
<item>19</item>
<item>18</item>
</defaultApprovers>
</getDepartmentByIdReturn>
</getDepartmentByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getDepartmentByName Element:
Operation type: Request-response.
 The endpoint receives a message to get a Department details, and sends a correlated
message of Department information.

Input: getDepartmentByNameRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Department Name Yes Name of Department

Output: getDepartmentByNameResponse

Data Field Name Data Field Type Required Acceptable Values

getDepartmentByIdReturn departmentBean

getDepartmentByName Test Case:

Input: getDepartmentByNameRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 93

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getDepartmentByName>
<in0>webapi-464745806681923416</in0>
<in1>Customer Service</in1>
</urn:getDepartmentByName>
</soapenv:Body>
</soapenv:Envelope>

Output: getDepartmentByNameResponse

getDepartments Element:
Operation type: Request-response.
 The endpoint receives a message to get all Departments and sends a correlated
message of Department information. This functions similar to getLookUp Request.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 94

Input: getDepartmentsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login

Output: getDepartmentsResponse

Data Field Name Data Field Type Required Acceptable Values

getDepartmentsReturn departmentArray []

getDepartments Test Case:

Input: getDepartmentsRequest

Output: getDepartmentsResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 95

</associatedUsers>
<defaultApprovers>
<item>16</item>
<item>13</item>
<item>18</item>
</defaultApprovers>
</item>
<item>
<additionalProperties>
<item xmlns:ns11="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string"/>
</item>
</additionalProperties>
<creationDate>2008-11-25T00:00:00.000Z</creationDate>
<departmentId>7</departmentId>
<departmentName>Human Resources</departmentName>
<lastUpdated>2008-11-25T00:00:00.000Z</lastUpdated>
<associatedUsers>
<item>18</item>
</associatedUsers>
<defaultApprovers xsi:nil="true"/>
</item>
<item>
<additionalProperties>
<item xmlns:ns12="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string">12,18,</value>
</item>
</additionalProperties>
<creationDate>2008-12-08T00:00:00.000Z</creationDate>
<departmentId>12</departmentId>
<departmentName>Product Management</departmentName>
<lastUpdated>2009-03-11T00:00:00.000Z</lastUpdated>
<associatedUsers>
<item>2</item>
<item>8</item>
<item>11</item>
<item>12</item>
</associatedUsers>
<defaultApprovers>
<item>12</item>
<item>18</item>
</defaultApprovers>
</item>
</array>
</getDepartmentsReturn>
</getDepartmentsResponse>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 96

upsertDepartment Element:
Operation type: Request-response.
 The endpoint receives a message to update or create a department instance, and sends
a correlated message only if error occurred.
 Please Note: Upsert is used to both create or update data within a specific department.
Using the department ID AND department Name attribute updates or replaces existing
department details. Requires both.

Input:upsertDepartmentRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
AdditionalProperties[]
departmentID*
in1 departmentBean * departmentName*
associatedUsers
defaultApprovers

Output: upsertDepartmentResponse

Data Field Name Data Field Type Required Acceptable Values

upsertDepartmentReturn

upsertDepartmentTest Case:

Input: upsertDepartmentRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 97

<item>5</item>
</associatedUsers>
<defaultApprovers>

<item>5</item>
</defaultApprovers>
</bean>
</urn:upsertDepartment>
</soapenv:Body>
</soapenv:Envelope>

Output: upsertDepartmentResponse

Email Log API Calls

Email API calls allow a log to be created in Taleo Business Edition when an email is created
outside of the system. Requires a valid email address stored within the system (i.e. Candidate,
User, Contact). Email API calls provide a contact log ID as a response.

createEmailLog Element:
Operation type: Request-response.
 The endpoint receives a message to create a contact record that somebody sent an
email to the user (INBOUND EMAIL). Tries to match incoming email address against
candidate, then contact, then user.
 First match is where this contact log gets created within the Session ID (obtained at API
login).

Input:createEmailLogRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
Email address of
in1 String Yes candidate, contact, or
user (must already

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 98

exist)
Subject of email
in2 String Yes
message
Body of email
in3 String Yes
message
Calendar of email
in4 Date Yes
message

Output: createEmailLogResponse

Data Field Name Data Field Type Required Acceptable Values

Provided Contact Log
createEmailLogReturn Long Yes
ID

createEmailLog Test Case:

Input: createEmailLogRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createEmailLog>
<in0>webapi-516132820785594972</in0>
<in1>[email protected]</in1>
<in2>Test_Subject</in2>
<in3>Test_Body</in3>
<in4>2009-06-30T23:01:26.493Z</in4>
</urn:createEmailLog>
</soapenv:Body>
</soapenv:Envelope>

Output: createEmailLogResponse

createEmailSentLog Element:
Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 99

 The endpoint receives a message to create a contact record that the user sent somebody
an email (OUTBOUND EMAIL). Tries to match outgoing email address against
candidate, then contact, then user.
 First match is where this contact log gets created within the Session ID (obtained at API
login).

Input:createEmailSentLogRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
Email address of
candidate, contact, or
in1 String Yes
user (must already
exist)
Subject of email
in2 String Yes
message
Body of email
in3 String Yes
message
Calendar of email
in4 Date Yes
message

Output: createEmailSentLogResponse

Data Field Name Data Field Type Required Acceptable Values

Provided Contact Log
createEmailSentLogReturn Long Yes
ID

createEmailSentLog Test Case:

Input: createEmailSentLogRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createEmailSentLog>
<in0>webapi-516132820785594972</in0>
<in1>[email protected]</in1>
<in2>Test_Subject</in2>
<in3>Test_Body</in3>
<in4>2009-06-30T23:01:26.493Z</in4>
</urn:createEmailSentLog>
</soapenv:Body>
</soapenv:Envelope>

Output: createEmailLogResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 100
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<createEmailSentLogResponse xmlns="urn:TBEWebAPI">
<createEmailSentLogReturn xmlns="">8</createEmailSentLogReturn>
</createEmailSentLogResponse>
</soapenv:Body>
</soapenv:Envelope>

Employee API Calls

Employees are all the people employed by the company and can be managed by Taleo Business
Edition. Employees in the Taleo Business Edition system are uniquely identified by email
address.

employeeBean Definition:

Data Field Name Data Field Type Required Acceptable Values

Candidate’s unique
server side ID. Can
be obtained by
id Long Read Only searching the
candidate database
or by creating a new
candidate.
Picklist derived
employee status
(terminated, etc.) . As
these are
status String Yes configurable, view
source on add/edit
employee page to
find values (search
for ‘status’)
city String No City name
Street portion of
address String No
address
zipCode String No Zip or postal code
State, region or
state String No province name from
pick list
Country code from
country String No
pick list
Employee telephone
phone String No
number
employeeNumber String Yes Configurable

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 101
employee number
email String No Email of employee
firstName String No First name
middleInitial String No Middle name
lastName String Yes Last name
Employees mobile or
cellPhone String No
cell phone number
Date of which the
hiredDate dateTime No
employee was hired.
Date of
startDate dateTime No
commencement
Race name from pick
race String No
list
Gender name from
gender String No
pick list
True to lock
employee access
lockedFromEws Boolean No
from the employee
website
Picklist derived
department of
employee . As these
are configurable, view
departmentId Long No
source on add/edit
employee page to
find values (search
for ‘department’)
Managers ID that is
managerId Long No the direct superior of
employee
Picklist derived
location of employee .
As these are
configurable, view
locationId Long No
source on add/edit
employee page to
find values (search
for ‘location’)
Employee website
ewsLogin String Yes
login name
Password chosen on
ewsPassword String Yes
Employee Web Site
jobTitle String No Employee’s job title
Employees defined
jobCode String No
job code value
Employees defined
salaryGrade String No
salary grade
Employees defined
salary Double No
salary amount.
payFrequency String No Picklist derived

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 102
payment frequency
(monthly, etc.) . As
these are
configurable, view
source on add/edit
employee page to
find values (search
for ‘payFrequency’)
Require the
employee to change
changePswdOnEwsLogin Boolean No their password when
first login to employee
portal website (EWS)
creationDate dateTime Read Only Creation date
lastUpdated dateTime Read Only Last updated date
Array of flexible
(future standard) field
values.
additionalEntities additionalEntitiesBean [] No
** PLACEHOLDER
FOR FUTURE USE
Array of flexible
flexValues flexFieldBean [] No
(custom) field values
*** ACCESSIBLE
birthDate encryptedDate No WITHIN FLEX FIELD
BEAN
*** ACCESSIBLE
ssn encryptedString No WITHIN FLEX FIELD
BEAN

flexFieldBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
FieldName String Yes Field name
Value of Text, Email, URL, Pick list, or
StringValue String No Text Area field. For Multiple Pick list use
‘|’ to separate values.
IntValue int No Value of Integer field
DoubleValue double No Value of Decimal or Currency field
BooleanValue boolean No Value of Check Box field
DateValue Date No Value of Date field

createEmployee Element:
Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 103
 The endpoint receives a message to create a employee, and sends a correlated
message of employee ID.

Input:createEmployeeRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received at
sessionID String Yes
Login
flexValues []
status *
city
address
zipCode
state
country
phone
employeeNumber *
email
firstName
middleInitial
lastName *
cellPhone
hiredDate
startDate
bean employeeBean[] *
race
gender
lockedFromEws
reviewManagerId
departmentId
managerId
locationId
ewsLogin *
ewsPassword *
jobTitle
jobCode
salaryGrade
salary
payFrequency
changePswdOnEwsLogin
additionalEntities []

Output: createEmployeeResponse

Data Field Name Data Field Type Required Acceptable Values

createEmployeeReturn Long Yes Provided Employee ID

createEmployee Test Case:

Input:createEmployeeRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 104
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createEmployee>
<sessionId>webapi4901801771281067756</sessionId>
<bean>
<flexValues>

<item>
<fieldName>ssn</fieldName>
<valueStr>23423452</valueStr>
</item>
<item>
<fieldName>birthdate</fieldName>
<valueDate>2009-10-01T23:01:26.493Z</valueDate>
</item>
</flexValues>
<status>Employed</status>
<city>Seattle</city>
<address>234 Sandra Ave</address>
<zipCode>578937</zipCode>
<state>US-WA</state>
<country>United States</country>
<phone>754-343-2323</phone>
<employeeNumber>S-54896</employeeNumber>
<email>[email protected]</email>
<firstName>Sharon</firstName>
<middleInitial>A</middleInitial>
<lastName>Darrah</lastName>
<cellPhone>230-234-5895</cellPhone>
<hiredDate>2009-06-30T23:01:26.493Z</hiredDate>
<startDate>2009-10-01T23:01:26.493Z</startDate>
<race>Hispanic or Latino</race>
<gender>Female</gender>
<lockedFromEws>False</lockedFromEws>
<reviewManagerId>4</reviewManagerId>
<departmentId>2</departmentId>
<managerId>4</managerId>
<locationId>2</locationId>
<ewsLogin>sand</ewsLogin>
<ewsPassword>sand</ewsPassword>
<jobTitle>Consultant</jobTitle>
<jobCode>Consulting</jobCode>
<salaryGrade>Level 1</salaryGrade>
<salary>5600</salary>
<payFrequency>Monthly</payFrequency>
<changePswdOnEwsLogin>False</changePswdOnEwsLogin>
<additionalEntities>

<item>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 105
</item>
</additionalEntities>
</bean>
</urn:createEmployee>
</soapenv:Body>
</soapenv:Envelope>

Output: createEmployeeResponse

deleteEmployee Element:

Operation type: Request-response.

 The endpoint receives a message to delete an employee, and sends a correlated
message only if error occurred.

Input: deleteEmployeeRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
sessionID String Yes
at Login
employeeID Employee ID Yes ID of Employee

Output: deleteEmployeeResponse

Data Field Name Data Field Type Required Acceptable Values

deleteEmployeeReturn

deleteEmployee Test Case:

Input: deleteEmployeeRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 106
<urn:deleteEmployee>
<sessionId>webapi4901801771281067756</sessionId>
<employeeId>134</employeeId>
</urn:deleteEmployee>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteEmployeeResponse

deleteEmployeeByNumber Element:
Operation type: Request-response.
 The endpoint receives a message to delete an employee by employee number, and
sends a correlated message only if error occurred.

Input: deleteEmployeeByNumberRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
sessionID String Yes
at Login
employeeNumber Employee Number Yes Number of Employee

Output: deleteEmployeeByNumberResponse

Data Field Name Data Field Type Required Acceptable Values

deleteEmployeeByNumberReturn

deleteEmployeeByNumber Test Case:

Input: deleteEmployeeByNumberRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 107
</urn:deleteEmployeeByNumber>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteEmployeeByNumberResponse

getEmployeeById Element:
Operation type: Request-response.
 The endpoint receives a message to get employee general information by ID, and sends
a correlated message of Employee information.

Input: getEmployeeByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
sessionID String Yes
at Login
employeeID Employee ID Yes ID of Employee

Output: getEmployeeByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getEmployeeByIdReturn employeeBean []

getEmployeeById Test Case:

Input: getEmployeeByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getEmployeeById>
<sessionId>webapi4901801771281067756</sessionId>
<employeeId>137</employeeId>
<additionalEntities>

<item></item>
</additionalEntities>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 108
</urn:getEmployeeById>
</soapenv:Body>
</soapenv:Envelope>

Output: getEmployeeByIdResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getEmployeeByIdResponse xmlns="urn:TBEWebAPI">
<getEmployeeByIdReturn xmlns="">
<creationDate>2009-09-15T17:19:43.153Z</creationDate>
<flexValues>
<item>
<fieldName>ssn</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr/>
</item>
<item>
<fieldName>birthdate</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>District</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Add Email Recipients</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr/>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 109
</item>
<item>
<fieldName>Candidate Resume</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>CandidateID</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Career Ambitions</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Critical Experience</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr/>
</item>
<item>
<fieldName>Critical Position</fieldName>
<valueBool>false</valueBool>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Desired Advancement</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 110
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Desired Mobility</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Flight Risk Reason:</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr/>
</item>
<item>
<fieldName>Flight Risk?</fieldName>
<valueBool>false</valueBool>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>High Performer</fieldName>
<valueBool>false</valueBool>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Highest Education Level</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Languages Spoken</fieldName>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 111
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr/>
</item>
<item>
<fieldName>Leadership Qualities</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr/>
</item>
<item>
<fieldName>Next Level Position Ranki</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Potential</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Preferred Locations</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr/>
</item>
<item>
<fieldName>Promotion Readiness</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 112
</item>
<item>
<fieldName>Role in department</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Willingness to Re Locate</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>department</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong>7</valueLong>
<valueStr>Human Resources</valueStr>
</item>
</flexValues>
<id>3</id>
<lastUpdated>2009-12-17T22:49:45.553Z</lastUpdated>
<status>Employed</status>
<city>b</city>
<address>12 Fineman Avenue</address>
<zipCode>93038</zipCode>
<state/>
<country>US</country>
<employeeNumber>EMP110479</employeeNumber>
<email>[email protected]</email>
<firstName>Sandra</firstName>
<middleInitial>b</middleInitial>
<lastName>Sujan</lastName>
<cellPhone>978-658-2353</cellPhone>
<title xsi:nil="true"/>
<hiredDate>2001-01-02T00:00:00.000Z</hiredDate>
<startDate>2001-01-02T00:00:00.000Z</startDate>
<race xsi:nil="true"/>
<gender xsi:nil="true"/>
<reviewManagerId>28</reviewManagerId>
<departmentId>7</departmentId>
<hierarchyPath>m.1c.m.1c.2j.6</hierarchyPath>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 113
<managerId>6</managerId>
<locationId>3</locationId>
<ewsLogin>10479</ewsLogin>
<ewsPassword>2762290428252901316429404006414531003189==</ewsPassword>
<jobTitle>Benefits Analyst</jobTitle>
<jobCode>2073</jobCode>
<salaryGrade/>
<salary>0.0</salary>
<payFrequency xsi:nil="true"/>
<changePswdOnEwsLogin>true</changePswdOnEwsLogin>
<additionalEntities/>
<phone>781-436-9794</phone>
</getEmployeeByIdReturn>
</getEmployeeByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getEmployeeByNumber Element:
Operation type: Request-response.
 The endpoint receives a message to get employee general information by Number, and
sends a correlated message of Employee information.

Input: getEmployeeByNumberRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
sessionID String Yes
at Login
Defined Employee
employeeNumber String Yes
Number

Output: getEmployeeByNumberResponse

Data Field Name Data Field Type Required Acceptable Values

getEmployeeByNumberReturn employeeBean []

getEmployeeByNumber Test Case:

Input: getEmployeeByNumberRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getEmployeeByNumber>
<sessionId>webapi4901801771281067756</sessionId>
<employeeNumber>S-54896</employeeNumber>
<additionalEntities>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 114

<item></item>
</additionalEntities>
</urn:getEmployeeByNumber>
</soapenv:Body>
</soapenv:Envelope>

Output: getEmployeeByNumberResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getEmployeeByNumberResponse xmlns="urn:TBEWebAPI">
<getEmployeeByNumberReturn xmlns="">
<creationDate>2009-09-15T17:19:43.153Z</creationDate>
<flexValues>
<item>
<fieldName>District</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
</flexValues>
<id>137</id>
<lastUpdated>2009-09-15T17:19:43.153Z</lastUpdated>
<status>Employed</status>
<city>Seattle</city>
<address>234 Sandra Ave</address>
<zipCode>578937</zipCode>
<state>US-WA</state>
<country>US</country>
<employeeNumber>S-54896</employeeNumber>
<email>[email protected]</email>
<firstName>Sharon</firstName>
<middleInitial>A</middleInitial>
<lastName>Darrah</lastName>
<cellPhone>230-234-5895</cellPhone>
<title xsi:nil="true"/>
<hiredDate>2009-06-30T23:01:26.493Z</hiredDate>
<startDate>2009-10-01T23:01:26.493Z</startDate>
<race>Hispanic or Latino</race>
<gender>Female</gender>
<reviewManagerId>4</reviewManagerId>
<departmentId>2</departmentId>
<hierarchyPath>ae</hierarchyPath>
<managerId>4</managerId>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 115
<locationId>2</locationId>
<ewsLogin>S-54896</ewsLogin>
<ewsPassword>3101290627273108292727644022402228412763==</ewsPassword>
<jobTitle>Consultant</jobTitle>
<jobCode>Consulting</jobCode>
<salaryGrade>Level 1</salaryGrade>
<salary>5600.0</salary>
<payFrequency>Monthly</payFrequency>
<changePswdOnEwsLogin>true</changePswdOnEwsLogin>
<additionalEntities/>
<phone>754-343-2323</phone>
</getEmployeeByNumberReturn>
</getEmployeeByNumberResponse>
</soapenv:Body>
</soapenv:Envelope>

searchEmployee Element:
Operation type: Request-response.
 The endpoint receives a message to query all employees based on defined key (field
name) and value (data looking for), and sends a correlated message of Employee ID and
associated search relevance.
 Relevance is a value between 0 and 100, which reflects how well the account matches
the search criteria
 Map of search parameters always contains:
o key: name of field to search as a string
o value: search parameter as string.
 Format of search value may differ depending on data type of the search field:
 For text, text area, email, URL fields: simple text to be found (case-insensitive) in this
field. Example:
o key=”city”, value=”Francisco” will search for all candidates with ”Francisco” in
“city” field.
 For integer, double, currency: interval between two numbers separated by ‘|’ character.
Either left (from) or right (to) side can be omitted. Example:
o key=”rank”, value=”100|” will search for all candidates with rank value no less
than 100.
o key=”rank”, value=”|200” will search for all candidates with rank value no more
than 200.
o key=”rank”, value=”100|200” will search for all candidates with rank value
between 100 and 200 (inclusive).
 For date fields: interval between two dates in ISO yyyy-MM-dd format, separated by ‘|’
character. Either left (from) or right (to) side can be omitted. Example:
o key=”startDate”, value=”2004-06-01|” will search for all candidates with start date
on or after June 1st 2004.
o key=”startDate”, value=”|2004-08-01” will search for all candidates with start date
on or before August 1st 2004.
o key=”startDate”, value=”2004-06-01|2004-08-01” will search for all candidates
with start date between June 1st 2004 and August 1st 2004 (inclusive).
 For date interval fields: number of days from today to the past. Example:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 116
o key=” addedWithin”, value=”7” will search for all candidates added to the system
within the last week.
 For single pick list: code value or name of selected item. Example:
o key=”country”, value=”US” will search for all candidates with country field equals
to “United States”.
o key=”status”, value=”available” will search for all candidates in “Available” status.
 For multiple pick list: code values or names of selected items, separated by ‘|’ character.
Example:
o key=”customMultiple”, value=”A1|B2|X5” will search for all candidates with
customMultiple field containing one or more of values: A1, B2, X5.
 For check box fields: “true” if check box must be checked, “false” is unchecked. Example:
o key=” flagged”, value=”true” will search for all candidates “flagged” for the user
currently logged in.
 Search keys names and types can be found in Administration>Customize>Employee
Fields. They may include both system fields (listed below for convenience) and custom
fields. For custom fields External name is used as key name.

System Search Keys:

Data Field Name Parameter Type Description

Keyword(s) in candidate’s resume.
keyword String Identical syntax as used in Taleo browser
interface
emplid Integer ID of candidate
employeeNumber String Configured ID of Employee
jobCode String Job Code Value
firstName String First name
lastName String Last name
middleInitial String Middle name
address String Street address
city String City
state Pick list State/Region
zipCode String ZIP/Postal code
country Pick list Country name
phone String Phone #
cellPhone String Mobile #
phoneAll String Any phone
email String Email
status Pick list Status name
lastUpdated Date Last updated date
creationDate Date Added to system date
gender Pick list Gender
race Pick list Race name
salary Currency salary amount
salaryGrade Picklist grade of salary payment
addedWithin Integer Added within N days
updatedWithin Integer Updated within N days
flagged Check Box Flagged candidates only

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 117
hiredDate Date Hired date
startDate Date Start date

Input: searchEmployeeRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
sessionID String Yes
at Login
key
searchParams Item… Yes
value

Output: searchEmployeeResponse

Data Field Name Data Field Type Required Acceptable Values

searchEmployeeReturn searchResultBean []

searchEmployee Test Case:

Input: searchEmployeeRequest

Output: searchEmployeeResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 118
<array>
<item>
<id>4</id>
<relevance>1.0</relevance>
</item>
<item>
<id>6</id>
<relevance>1.0</relevance>
</item>
<item>
<id>8</id>
<relevance>1.0</relevance>
</item>
</array>
</searchEmployeeReturn>
</searchEmployeeResponse>
</soapenv:Body>
</soapenv:Envelope>

updateEmployee Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing employee, and sends a
correlated message only if error occurred.
 Please Note: Update requests replace all data fields in the employeeBean (i.e. data is not
appended). Send all elements back or the field values will be returned NULL.

Input:updateEmployeeRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received at
sessionID String Yes
Login
flexValues []
id *
status *
city
address
zipCode
state
country
bean employeeBean[] *
phone
employeeNumber *
email
firstName
middleInitial
lastName *
cellPhone
hiredDate

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 119
startDate
race
gender
lockedFromEws
reviewManagerId
departmentId
managerId
locationId
ewsLogin *
ewsPassword *
jobTitle
jobCode
salaryGrade
salary
payFrequency
changePswdOnEwsLogin
additionalEntities []

Output: updateEmployeeResponse

Data Field Name Data Field Type Required Acceptable Values

updateEmployeeReturn

updateEmployee Test Case:

Input: updateEmployeeRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 120
<email>[email protected]</email>
<firstName>Sharon</firstName>
<middleInitial>A</middleInitial>
<lastName>Darrah</lastName>
<cellPhone>230-234-5895</cellPhone>
<hiredDate>2009-06-30T23:01:26.493Z</hiredDate>
<startDate>2009-10-01T23:01:26.493Z</startDate>
<race>Hispanic or Latino</race>
<gender>Female</gender>
<lockedFromEws>False</lockedFromEws>
<reviewManagerId>4</reviewManagerId>
<departmentId>2</departmentId>
<managerId>4</managerId>
<locationId>2</locationId>
<ewsLogin>sand</ewsLogin>
<ewsPassword>sand</ewsPassword>
<jobTitle>Consultant</jobTitle>
<jobCode>Consulting</jobCode>
<salaryGrade>Level 1</salaryGrade>
<salary>5600</salary>
<payFrequency>Monthly</payFrequency>
<changePswdOnEwsLogin>False</changePswdOnEwsLogin>
<additionalEntities>

<item>
</item>
</additionalEntities>
</bean>
</urn:updateEmployee>
</soapenv:Body>
</soapenv:Envelope>

Output: updateEmployeeResponse

upsertEmployee Element:
Operation type: Request-response.
 The endpoint receives a message to upsert an existing employee record (create new
andor update existing), and sends a correlated message of the employee ID that has
their data record/elements updated.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 121
 Upsert is the universal create and update command for Taleo Business Edition API.
When using upsertEmployee as create command, use all the field exept for employeeID,
When using upsertEmployee as update command, use all fields or fields will be defined
NULL (same as updateEmployee).

Input:upsertEmployeeRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received at
sessionID String Yes
Login
Defined Employee
employeeNumber String Yes
Number
flexValues []
id *
status *
city
address
zipCode
state
country
phone
email
firstName
middleInitial
lastName *
cellPhone
hiredDate
startDate
bean employeeBean[] *
race
gender
lockedFromEws
reviewManagerId
departmentId
managerId
locationId
ewsLogin *
ewsPassword *
jobTitle
jobCode
salaryGrade
salary
payFrequency
changePswdOnEwsLogin
additionalEntities []

Output: upsertEmployeeResponse

Data Field Name Data Field Type Required Acceptable Values

upsertEmployeeReturn Long Employee ID

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 122
upsertEmployee Test Case:

Input: upsertEmployeeRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:upsertEmployee>
<sessionId>webapi7073868042459393355</sessionId>
<bean>
<flexValues>

<item>
<fieldName>District</fieldName>
<valueStr>Store1</valueStr>
</item>
</flexValues>
<id>137</id>
<status>Employed</status>
<city>Seattle</city>
<address>234 Sandra Ave</address>
<zipCode>578937</zipCode>
<state>US-WA</state>
<country>United States</country>
<phone>754-343-2323</phone>
<employeeNumber>S-54896</employeeNumber>
<email>[email protected]</email>
<firstName>Sharon</firstName>
<middleInitial>A</middleInitial>
<lastName>Darrah</lastName>
<cellPhone>230-234-5895</cellPhone>
<hiredDate>2009-06-30T23:01:26.493Z</hiredDate>
<startDate>2009-10-01T23:01:26.493Z</startDate>
<race>Hispanic or Latino</race>
<gender>Female</gender>
<lockedFromEws>False</lockedFromEws>
<reviewManagerId>4</reviewManagerId>
<departmentId>2</departmentId>
<managerId>4</managerId>
<locationId>2</locationId>
<ewsLogin>sand</ewsLogin>
<ewsPassword>sand</ewsPassword>
<jobTitle>Consultant</jobTitle>
<jobCode>Consulting</jobCode>
<salaryGrade>Level 1</salaryGrade>
<salary>5600</salary>
<payFrequency>Monthly</payFrequency>
<changePswdOnEwsLogin>False</changePswdOnEwsLogin>
<additionalEntities>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 123

<item>
</item>
</additionalEntities>
</bean>
</urn:upsertEmployee>
</soapenv:Body>
</soapenv:Envelope>

Output: upsertEmployeeResponse

Event API Calls

Events are calendar tasks stored within a specific entity of Taleo Business Edition. There is a
one-to-many relationship with events to entities. Entities include accounts (ACCT), candidates
(CAND), contacts (CTCT), employees (EMPL), requisitions (REQU) and users (WORK).

calendarEventBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
Account’s unique server side ID. Can be
id long Read Only obtained by searching the accounts’
database or by creating a new account.
status String Yes Account’s Status from pick list
creator String Yes Creator’s login name
entityType String Yes Type of related entity:
ACCT = accounts
CAND = candidates
CTCT = contacts
EMPL = employees
REQU = requisitions
WORK = users
entityId long Yes ID of associated entity
location String No Location of event
subject String Yes Subject of event

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 124
“Private event” flag
isPrivate Boolean No True
False
startDate Date Yes Date and time of event begin
duration long Yes Duration of event (in ms)
description String No Description
participants ParticipantBean[] Yes Array of events’ participants
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
flexValues FlexFieldBean[] No Array of flexible (custom) field values

participantBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
PersonId long Read Only ID of person (user or contact)
Type of person object: WORK=user,
CTCT=contact. Use appropriate API to
PersonType String Yes
extract actual person object using
person’s ID
ID of event (interview, calendar event, or
EventId long Yes
task)
Type of event object: INTV=interview,
CLDEV=calendar event, TASK=task. Use
EventType String Yes
appropriate API to extract actual event
object using event’s ID
StartDate Date No Event's start date for given participant.
EndDate Date No Event's end date for given participant.

flexFieldBean Definition:

createEvent Element:
Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 125
 The endpoint receives a message to create an event, and sends a correlated message of
event ID.

Input: createEventRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status *
creator
description
duration *
entityId *
entityType *
isPrivate type
location
calendarEventBean[]
in1 * startDate *
participantBean []
subject

participants []
endDate
eventId *
eventType *
personId *
personType *
startDate

Output: createEventResponse

Data Field Name Data Field Type Required Acceptable Values

createEventReturn Long Yes Provided Event ID

createEvent Test Case:

Input: createEventRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createEvent>
<in0>webapi7774524514047942379</in0>
<in1>
<flexValues>

</flexValues>
<status>New</status>
<creator>skarim</creator>
<description>Face to face Interview</description>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 126
<duration>50000</duration>
<entityId>48</entityId>
<entityType>CAND</entityType>
<isPrivate>True</isPrivate>
<location>Meeting Room 1</location>
<participants>

<item>
<endDate>2009-06-30T23:01:26.493Z</endDate>
<eventType>CLDEV</eventType>
<personId>7</personId>
<personType>WORK</personType>
<startDate>2009-06-30T23:01:26.493Z</startDate>
</item>
</participants>
<startDate>2009-06-30T23:01:26.493Z</startDate>
<subject>Interview</subject>
</in1>
</urn:createEvent>
</soapenv:Body>
</soapenv:Envelope>

Output: createEventResponse

deleteEvent Element:
Operation type: Request-response.
 The endpoint receives a message to delete an event instance, and sends a correlated
message only if error occurred.

Input: deleteEventRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Event ID Yes ID of Event

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 127
Output: deleteEventResponse

Data Field Name Data Field Type Required Acceptable Values

deleteEventReturn

deleteEvent Test Case:

Input: deleteEventRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteEvent>
<in0>webapi5722630372091424901</in0>
<in1>2</in1>
</urn:deleteEvent>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteEventResponse

getEventByEntity Element:
Operation type: Request-response.
 The endpoint receives a message to get event(s) associated with any Taleo Business
Edition entity that supports storing/creation of calendar events, and sends back event IDs
associated with the entity ID.

Input: getEventByEntityRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
Type of related entity:
ACCT = accounts
CAND = candidates
in1 Long Yes
EMPL = employees
REQU = requisitions
WORK = users

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 128
in2 Long Yes ID of associated entity

Output: getEventByEntityResponse

Data Field Name Data Field Type Required Acceptable Values

getEventByEntityReturn array of event IDs

getEventByEntity Test Case:

Input: getEventByEntityRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getEventByEntity>
<in0>webapi7774524514047942379</in0>
<in1>CAND</in1>
<in2>48</in2>
</urn:getEventByEntity>
</soapenv:Body>
</soapenv:Envelope>

Output: getEventByEntityResponse

getEventById Element:
Operation type: Request-response.
 The endpoint receives a message to get event details by event ID, and sends a
correlated message of event information.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 129
Input: getEventByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Event ID Yes ID of Event Instance

Output: getEventByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getEventByIdReturn calendarEventBean []

getEventById Test Case:

Input: getEventByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getEventById>
<in0>webapi7774524514047942379</in0>
<in1>1</in1>
</urn:getEventById>
</soapenv:Body>
</soapenv:Envelope>

Output: getEventByIdResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 130
<item>
<endDate>2009-06-30T02:00:00.000Z</endDate>
<eventId>1</eventId>
<eventType>CLDEV</eventType>
<personId>7</personId>
<personType>WORK</personType>
<startDate>2009-06-30T00:00:00.000Z</startDate>
</item>
</participants>
<startDate>2009-06-30T00:00:00.000Z</startDate>
<subject>Interview</subject>
</getEventByIdReturn>
</getEventByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getPublicEvents Element:
Operation type: Request-response.
 The endpoint receives a message to get all public events within a start date and end
date, and sends a correlated message array of event IDs.

Input: getPublicEventsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
Start of start date
in1 dateTime Yes
interval
End of start date
in2 dateTime Yes
interval

Output: getPublicEventsResponse

Data Field Name Data Field Type Required Acceptable Values

getPublicEventsReturn array of Event IDs

getPublicEvents Test Case:

Input: getPublicEventsRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 131
<in2>2010-06-30T00:00:00.000Z</in2>
</urn:getPublicEvents>
</soapenv:Body>
</soapenv:Envelope>

Output: getPublicEventsResponse

Input: updateEventRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
id *
status *
creator
description
duration *
entityId *
entityType *
in1 calendarEventBean[] * isPrivate type
location
startDate *
subject

participants []
endDate
eventId *
eventType *

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 132
personId *
personType *
startDate

Output: updateEventResponse

Data Field Name Data Field Type Required Acceptable Values

updateEventReturn

updateEvent Test Case:

Input: updateEventRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateEvent>
<in0>webapi5722630372091424901</in0>
<in1>
<flexValues>

</flexValues>
<id>7</id>
<status>New</status>
<creator>skarim</creator>
<description>Face to face interview</description>
<duration>500000</duration>
<entityId>48</entityId>
<entityType>CAND</entityType>
<isPrivate>False</isPrivate>
<location>Meeting Room A</location>
<participants>

<item>
<endDate>2009-06-30T02:00:00.000Z</endDate>
<eventType>TASK</eventType>
<personId>7</personId>
<personType>WORK</personType>
<startDate>2009-06-30T00:00:00.000ZZ</startDate>
</item>
</participants>
<startDate>2009-06-30T00:00:00.000Z</startDate>
<subject>Interview</subject>
</in1>
</urn:updateEvent>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 133
Output: updateEventResponse

Interview API Calls

Interview Bean is where to find details regarding an interview associated with any candidate in
Taleo Business Edition. Similar to background checks, there is a one-to-many relationship with
interviews to candidates.

interviewBean Definition:

Data Field Name Data Field Type Required Acceptable Values

Account’s unique server side ID. Can be
Id (read-only) long Read Only obtained by searching the accounts’
database or by creating a new account.
Status String Yes Account’s Status from pick list
CandidateId long Yes ID of candidate
RequisitionId long Yes ID of requisition
InterviewType String Yes Interview type (from pick list)
StartDate Date Yes Interview start date and time
InterviewRoom String No Interview room (location)
Comments String No Comments
Creator String No Creator’s login name
Participants ParticipantBean[] No Array of events’ participants
CreationDate
Date Read Only Creation date
(read-only)
LastUpdated
Date Read Only Last updated date
(read-only)
FlexValues FlexFieldBean[] No Array of flexible (custom) field values

participantBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
PersonId long Read Only ID of person (user or contact)
Type of person object: WORK=user,
PersonType String Yes
CTCT=contact. Use appropriate API to

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 134
extract actual person object using
person’s ID
ID of event (interview, calendar event, or
EventId long Yes
task)
Type of event object: INTV=interview,
CLDEV=calendar event, TASK=task. Use
EventType String Yes
appropriate API to extract actual event
object using event’s ID
StartDate Date No Event's start date for given participant.
EndDate Date No Event's end date for given participant.

flexFieldBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
FieldName String Yes Field name
Value of Text, Email, URL, Pick list, or
StringValue String No Text Area field. For Multiple Pick list use
‘|’ to separate values.
IntValue int No Value of Integer field
DoubleValue double No Value of Decimal or Currency field
BooleanValue boolean No Value of Check Box field
DateValue Date No Value of Date field

createInterview Element:
Operation type: Request-response.
 The endpoint receives a message to create an interview instance for a specific candidate,
and sends a correlated message of interview ID.

Input: createInterviewRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status *
candidateID *
comments
creator
interviewBean [] interviewRoom
in1 *
participantBean [] interviewType *
requisitionID *
startDate *

participants []

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 135
endDate
eventId
eventType
personId
personType
startDate

Output: createInterviewResponse

Data Field Name Data Field Type Required Acceptable Values

createInterviewReturn Long Yes Provided Interview ID

createInterview Test Case:

Input: createInterviewRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createInterview>
<in0>webapi411835895647962205</in0>
<in1>
<flexValues>

</flexValues>
<status>Phone Screen</status>
<candidateId>48</candidateId>
<comments>Direct Report</comments>
<creator>skarim</creator>
<interviewRoom>Whistler</interviewRoom>
<interviewType>1st Interview</interviewType>
<participants>

<item>
<endDate>2009-06-30T23:01:26.493Z</endDate>
<eventId>2</eventId>
<eventType>TASK</eventType>
<personId>7</personId>
<personType>WORK</personType>
<startDate>2009-06-30T23:01:26.493Z</startDate>
</item>
</participants>
<requisitionId>13</requisitionId>
<startDate>2009-06-30T23:01:26.493Z</startDate>
</in1>
</urn:createInterview>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 136
Output: createInterviewResponse

deleteInterview Element:
Operation type: Request-response.
 The endpoint receives a message to delete an interview instance, and sends a correlated
message only if error occurred.

Input: deleteInterviewRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Interview ID Yes ID of Interview

Output: deleteInterviewResponse

Data Field Name Data Field Type Required Acceptable Values

deleteInterviewReturn

deleteInterview Test Case:

Input: deleteInterviewRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteInterview>
<in0>webapi411835895647962205</in0>
<in1>2</in1>
</urn:deleteInterview>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteInterviewResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 137
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<deleteInterviewResponse xmlns="urn:TBEWebAPI"/>
</soapenv:Body>
</soapenv:Envelope>

getInterviewsByCandidate Element:
Operation type: Request-response.
 The endpoint receives a message to get interview(s) associated with any Taleo Business
Edition candidate, and sends back interview IDs associated for the candidate ID.

Input: getInterviewsByCandidateRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of candidate

Output: getInterviewsByCandidateResponse

Required Acceptable
Data Field Name Data Field Type
Values
getInterviewsByCandidateReturn array of interview IDs

getInterviewsByCandidate Test Case:

Input: getInterviewsByCandidateRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getInterviewsByCandidate>
<in0>webapi411835895647962205</in0>
<in1>48</in1>
</urn:getInterviewsByCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: getInterviewsByCandidateResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 138
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getInterviewsByCandidateResponse xmlns="urn:TBEWebAPI">
<getInterviewsByCandidateReturn xmlns="">
<array>
<item>2</item>
<item>1</item>
</array>
</getInterviewsByCandidateReturn>
</getInterviewsByCandidateResponse>
</soapenv:Body>
</soapenv:Envelope>

getInterviewById Element:
Operation type: Request-response.
 The endpoint receives a message to get interview details by interview ID, and sends a
correlated message of interview information.

Input: getInterviewByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
ID of Interview
in1 Interview ID Yes
Instance

Output: getInterviewByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getInterviewByIdReturn interviewBean []

getInterviewById Test Case:

Input: getInterviewByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getInterviewById>
<in0>webapi411835895647962205</in0>
<in1>1</in1>
</urn:getInterviewById>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 139
Output: getInterviewByIdResponse

updateInterview Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing interview instance, and sends a
correlated message only if error occurred.
 Please Note: Update requests replace all data fields in the interviewBean (i.e. data is not
appended or upserted). Send all elements back or the field values will be returned NULL.

Input: updateInterviewRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 140
flexValues []
id *
status *
candidateID *
comments
creator
interviewRoom
interviewType *
requisitionID *
interviewBean[]
in1 * startDate *
participantBean []

participants []
endDate
eventId
eventType
personId
personType
startDate

Output: updateInterviewResponse

Data Field Name Data Field Type Required Acceptable Values

updateInterviewReturn

updateInterview Test Case:

Input: updateInterviewRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateInterview>
<in0>webapi411835895647962205</in0>
<in1>
<flexValues>

</flexValues>
<id>1</id>
<status>Feedback Pending</status>
<candidateId>48</candidateId>
<comments>Direct Report</comments>
<creator>skarim</creator>
<interviewRoom>Whistler</interviewRoom>
<interviewType>1st Interview</interviewType>
<participants>

<item>
<endDate>2009-06-30T23:01:26.493Z</endDate>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 141
<eventId>2</eventId>
<eventType>TASK</eventType>
<personId>7</personId>
<personType>WORK</personType>
<startDate>2009-06-30T23:01:26.493Z</startDate>
</item>
</participants>
<requisitionId>13</requisitionId>
<startDate>2009-06-30T23:01:26.493Z</startDate>
</in1>
</urn:updateInterview>
</soapenv:Body>
</soapenv:Envelope>

Output: updateInterviewResponse

Link API Calls

Links are what tie one entity attribute to another. For example, linking a candidate to a requisition,
or an attachment to a candidate. Full list of entities include:
 Account = ACCT
 Candidate = CAND
 Contact = CTCT
 Requisition = REQU
 User = WORK

Where the following linkage is available:

 ACCT to REQU
 CTCT to REQU
 ACCT to CAND
 CTCT to CAND
 CAND to WORK

createLink Element:
Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 142
 The endpoint receives a message to Link an entity (by ID) to another entity (by ID) in
Taleo Business Edition, and sends a correlated message only if error occured.

Input: createLinkRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID obtained
sessionID String Yes
at login
entityType as
entityType1 String Yes
provided in above list
entityId1 String Yes ID of entity type 1
entityType as
entityType2 String Yes
provided in above list
entityId2 String Yes ID of entity type 2

Output: createLinkResponse

Data Field Name Data Field Type Required Acceptable Values

createLinkReturn

Link Test Case:

Input: createLinkRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createLink>
<sessionId>webapi-8948403736913319968</sessionId>
<entityType1>ACCT</entityType1>
<entityId1>2</entityId1>
<entityType2>REQU</entityType2>
<entityId2>16</entityId2>
</urn:createLink>
</soapenv:Body>
</soapenv:Envelope>

Output: createLinkResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 143
removeLink Element:
Operation type: Request-response.
 The endpoint receives a message to remove Linkage between two entities in Taleo
Business Edition, and sends a correlated message only if error occured.

Input: removeLinkRequest

Data Field Name Data Field Type Required Acceptable Values

Output: removeLinkResponse

Data Field Name Data Field Type Required Acceptable Values

removeLinkReturn

Link Test Case:

Input: removeLinkRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:removeLink>
<sessionId>webapi-8948403736913319968</sessionId>
<entityType1>ACCT</entityType1>
<entityId1>2</entityId1>
<entityType2>REQU</entityType2>
<entityId2>16</entityId2>
</urn:removeLink>
</soapenv:Body>
</soapenv:Envelope>

Output: removeLinkResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 144
<removeLinkResponse xmlns="urn:TBEWebAPI"/>
</soapenv:Body>
</soapenv:Envelope>

Location API Calls

Locations are office locations assigned within the system.

LocationBean Definition:

Data Field Name Data Field Type Required Acceptable Values

Account’s unique
server side ID. Can be
obtained by searching
locationId Long Read Only
the accounts’ database
or by creating a new
account.
locationName String Yes Location name
defaultApprovers long[] No Array of user ID’s

**Allows you to identify

which users are
assigned for approvals
to this Location
regionID Long No ID of region
city String No City name
address String No Street portion of mailing
address
zipCode String No ZIP or postal code
state String No State, region or
province name from
pick list
country String No Country code from pick
list
directions String No Text of location
directions
interviewRooms String No Text of interview rooms
where <item> array
denotes new room
phone String No Text of phone number
Local User Time zone
ID as derived from
timeZone String No piclklist:
'MIT' = GMT-11:00
'Pacific/Apia' = GMT-

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 145
11:00
'Pacific/Honolulu' =
GMT-10:00
'America/Anchorage' =
GMT-08:00
'America/Los_Angeles'
= GMT-07:00
'America/Denver' =
GMT-06:00
'America/Phoenix' =
GMT-07:00
'America/Tegucigalpa' =
GMT-06:00
'America/Winnipeg' =
GMT-05:00
'America/Mexico_City' =
GMT-05:00
'America/Chicago' =
GMT-05:00
'America/Costa_Rica' =
GMT-06:00
'America/Indianapolis' =
GMT-04:00
'America/New_York' =
GMT-04:00
'America/Bogota' =
GMT-05:00
'America/Montreal' =
GMT-04:00
'America/Santiago' =
GMT-04:00
'America/Caracas' =
GMT-04:30
'America/Thule' = GMT-
03:00
'America/St_Johns' =
GMT-02:30
'America/Buenos_Aires'
= GMT-03:00
'America/Sao_Paulo' =
GMT-03:00
'Atlantic/South_Georgia'
= GMT-02:00
'Atlantic/Cape_Verde' =
GMT-01:00
'Atlantic/Azores' =
GMT-00:00
'Europe/Dublin' =
GMT+01:00
'Africa/Casablanca' =
GMT-00:00

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 146
'Europe/Amsterdam' =
GMT+02:00
'Europe/Belgrade' =
GMT+02:00
'Europe/Brussels' =
GMT+02:00
'Europe/Warsaw' =
GMT+02:00
'Africa/Lagos' =
GMT+01:00
'Europe/Athens' =
GMT+03:00
'Europe/Bucharest' =
GMT+03:00
'Africa/Cairo' =
GMT+03:00
'Africa/Harare' =
GMT+02:00
'Europe/Helsinki' =
GMT+03:00
'Asia/Jerusalem' =
GMT+03:00
'Asia/Baghdad' =
GMT+03:00
'Asia/Kuwait' =
GMT+03:00
'Europe/Moscow' =
GMT+04:00
'Africa/Nairobi' =
GMT+03:00
'Asia/Tehran' =
GMT+04:30
'Asia/Dubai' =
GMT+04:00
'Asia/Baku' =
GMT+05:00
'Asia/Kabul' =
GMT+04:30
'Asia/Yekaterinburg' =
GMT+06:00
'Asia/Karachi' =
GMT+06:00
'Asia/Calcutta' =
GMT+05:30
'Asia/Katmandu' =
GMT+05:45
'Asia/Almaty' =
GMT+06:00
'Asia/Dhaka' =
GMT+07:00
'Asia/Colombo' =

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 147
GMT+05:30
'Asia/Rangoon' =
GMT+06:30
'Asia/Bangkok' =
GMT+07:00
'Asia/Krasnoyarsk' =
GMT+08:00
'Asia/Hong_Kong' =
GMT+08:00
'Asia/Irkutsk' =
GMT+09:00
'Asia/Kuala_Lumpur' =
GMT+08:00
'Australia/Perth' =
GMT+08:00
'Asia/Taipei' =
GMT+08:00
'Asia/Tokyo' =
GMT+09:00
'Asia/Seoul' =
GMT+09:00
'Asia/Yakutsk' =
GMT+10:00
'Australia/Adelaide' =
GMT+09:30
'Australia/Darwin' =
GMT+09:30
'Australia/Brisbane' =
GMT+10:00
'Australia/Sydney' =
GMT+10:00
'Pacific/Guam' =
GMT+10:00
'Australia/Hobart' =
GMT+10:00
'Asia/Vladivostok' =
GMT+11:00
'Asia/Magadan' =
GMT+12:00
'Pacific/Auckland' =
GMT+12:00
'Pacific/Fiji' =
GMT+12:00
'Pacific/Tongatapu' =
GMT+13:00
additionalProperties map No Used for expansion
calls
flexValues FlexFieldBean[] No Array of flexible
(custom) field values
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 148
createLocation Element:
Operation type: Request-response.
 The endpoint receives a message to create a Location, and sends a correlated message
of Location ID.

Input: createLocationRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
locationName
city
address
zipCode
state
country
in1 locationBean *
directions
regionID
timeZone
interviewRooms
phone
defaultApprovers

Output: createLocationResponse

Data Field Name Data Field Type Required Acceptable Values

createLocationReturn Long Yes Provided Location ID

createLocationTest Case:

Input: createLocationRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createLocation>
<sessionId>webapi-464745806681923416</sessionId>
<bean>
<city xmlns="">Los Angeles</city>
<address xmlns="">1A James st</address>
<zipCode xmlns="">92111</zipCode>
<state xmlns="">CA</state>
<country xmlns="">US</country>
<directions xmlns="">Take the 101 until you find us</directions>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 149
<locationName xmlns="">Los Angeles</locationName>
<regionId xmlns="">3</regionId>
<timeZone xmlns="">America/Los_Angeles</timeZone>
<interviewRooms xmlns="">
<item>Mount Rainier</item>
<item>Mount Adams</item>
<item>Mount Baker</item>
</interviewRooms>
<defaultApprovers xmlns="">
<item>8</item>
</defaultApprovers>
<phone>800-783-3789</phone>
</bean>
</urn:createLocation>
</soapenv:Body>
</soapenv:Envelope>

Output: createLocationResponse

deleteLocation Element:
Operation type: Request-response.
 The endpoint receives a message to delete a Location, and sends a correlated message
only if error occurred.

Input: deleteLocationRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Location ID Yes ID of Location

Output: deleteLocationResponse

Data Field Name Data Field Type Required Acceptable Values

deleteLocationReturn

deleteLocation Test Case:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 150
Input: deleteLocationRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteLocation>
<sessionId>webapi-464745806681923416</sessionId>
<locationId>4</locationId>
</urn:deleteLocation>
</soapenv:Body>
</soapenv:Envelope>
Output: deleteLocationResponse

getLocationById Element:
Operation type: Request-response.
 The endpoint receives a message to get a Location details, and sends a correlated
message of Location information.

Input: getLocationByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Location ID Yes ID of Location

Output: getLocationByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getLocationByIdReturn LocationBean

getLocationById Test Case:

Input: getLocationByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getLocationById>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 151
<in0>webapi-464745806681923416</in0>
<in1>3</in1>
</urn:getLocationById>
</soapenv:Body>
</soapenv:Envelope>

Output: getLocationByIdResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getLocationByIdResponse xmlns="urn:TBEWebAPI">
<getLocationByIdReturn>
<creationDate xsi:nil="true" xmlns=""/>
<flexValues xmlns=""/>
<id xmlns="">3</id>
<lastUpdated xsi:nil="true" xmlns=""/>
<status xsi:nil="true" xmlns=""/>
<city xmlns="">Seattle</city>
<address xmlns="">8979 Redwood Road</address>
<zipCode xmlns="">98101</zipCode>
<state xmlns="">WA</state>
<country xmlns="">US</country>
<additionalProperties xmlns="">
<item xmlns:ns1="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string">8,</value>
</item>
</additionalProperties>
<directions xmlns="">From I-5 North,take the Seneca Street exit (exit 165) on the left.
Turn slight left onto Seneca Street. Turn left onto 5th Avenue. Turn left onto Marion
Street.</directions>
<locationId xmlns="">3</locationId>
<locationName xmlns="">Seattle Office</locationName>
<regionId xmlns="">3</regionId>
<timeZone xmlns="">America/Los_Angeles</timeZone>
<interviewRooms xmlns="">
<item>Mount Rainier</item>
<item>Mount Adams</item>
<item>Mount Baker</item>
</interviewRooms>
<defaultApprovers xmlns="">
<item>8</item>
</defaultApprovers>
<phone>800-783-3789</phone>
</getLocationByIdReturn>
</getLocationByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 152
getLocationByName Element:
Operation type: Request-response.
 The endpoint receives a message to get a Location details, and sends a correlated
message of Location information.

Input: getLocationByNameRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Location Name Yes Name of Location

Output: getLocationByNameResponse

Data Field Name Data Field Type Required Acceptable Values

getLocationByIdReturn LocationBean

getLocationByName Test Case:

Input: getLocationByNameRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getLocationByName>
<in0>webapi-464745806681923416</in0>
<in1>Boston Office</in1>
</urn:getLocationByName>
</soapenv:Body>
</soapenv:Envelope>

Output: getLocationByNameResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 153
<address xmlns="">45 Howard Street</address>
<zipCode xmlns="">01801</zipCode>
<state xmlns="">MA</state>
<country xmlns="">US</country>
<additionalProperties xmlns="">
<item xmlns:ns1="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string">2,</value>
</item>
</additionalProperties>
<directions xmlns="">Please take the highway 93 to Route 128 south, exit
22</directions>
<locationId xmlns="">2</locationId>
<locationName xmlns="">Boston Office</locationName>
<regionId xmlns="">1</regionId>
<timeZone xmlns="">America/New_York</timeZone>
<interviewRooms xmlns="">
<item>Patriots Room</item>
<item>Red Sox Room</item>
<item>Bruins Room</item>
<item>Celtics Room</item>
</interviewRooms>
<defaultApprovers xmlns="">
<item>2</item>
</defaultApprovers>
<phone>800-343-3423</phone>
</getLocationByNameReturn>
</getLocationByNameResponse>
</soapenv:Body>
</soapenv:Envelope>

getLocations Element:
Operation type: Request-response.
 The endpoint receives a message to get all Locations and sends a correlated message of
Location information. This functions similar to getLookUp Request.

Input: getLocationsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login

Output: getLocationsResponse

Data Field Name Data Field Type Required Acceptable Values

getLocationsReturn LocationArray []

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 154
getLocations Test Case:

Input: getLocationsRequest

Output: getLocationsResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getLocationsResponse xmlns="urn:TBEWebAPI">
<getLocationsReturn>
<array xmlns="">
<item>
<creationDate xsi:nil="true"/>
<flexValues/>
<id>3</id>
<lastUpdated xsi:nil="true"/>
<status xsi:nil="true"/>
<city>Seattle</city>
<address>8979 Redwood Road</address>
<zipCode>98101</zipCode>
<state>WA</state>
<country>US</country>
<additionalProperties>
<item xmlns:ns1="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string">8,</value>
</item>
</additionalProperties>
<directions>From I-5 North,take the Seneca Street exit (exit 165) on the left. Turn
slight left onto Seneca Street. Turn left onto 5th Avenue. Turn left onto Marion
Street.</directions>
<locationId>3</locationId>
<locationName>Seattle Office</locationName>
<regionId>3</regionId>
<timeZone>America/Los_Angeles</timeZone>
<interviewRooms>
<item>Mount Rainier</item>
<item>Mount Adams</item>
<item>Mount Baker</item>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 155
</interviewRooms>
<defaultApprovers>
<item>8</item>
</defaultApprovers>
<phone>800-783-3789</phone>
</item>
<item>
<creationDate xsi:nil="true"/>
<flexValues/>
<id>2</id>
<lastUpdated xsi:nil="true"/>
<status xsi:nil="true"/>
<city>Woburn</city>
<address>45 Howard Street</address>
<zipCode>01801</zipCode>
<state>MA</state>
<country>US</country>
<additionalProperties>
<item xmlns:ns2="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string">2,</value>
</item>
</additionalProperties>
<directions>Please take the highway 93 to Route 128 south, exit 22</directions>
<locationId>2</locationId>
<locationName>Boston Office</locationName>
<regionId>1</regionId>
<timeZone>America/New_York</timeZone>
<interviewRooms>
<item>Patriots Room</item>
<item>Red Sox Room</item>
<item>Bruins Room</item>
<item>Celtics Room</item>
</interviewRooms>
<defaultApprovers>
<item>2</item>
</defaultApprovers>
<phone>800-343-3423</phone>
</item>
</array>
</getLocationsReturn>
</getLocationsResponse>
</soapenv:Body>
</soapenv:Envelope>

upsertLocation Element:
Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 156
 The endpoint receives a message to update or create a Location instance, and sends a
correlated message only if error occurred.
 Please Note: Upsert is used to both create or update data within a specific Location.
Using the Location ID AND Location Name attribute updates or replaces existing
Location details.

Input:upsertLocationRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
locationName
city
address
zipCode
state
country
in1 LocationBean[] *
directions
regionID
timeZone
interviewRooms
phone
defaultApprovers

Output: upsertLocationResponse

Data Field Name Data Field Type Required Acceptable Values

upsertLocationReturn

upsertLocationTest Case:

Input: upsertLocationRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:upsertLocation>
<sessionId>webapi-464745806681923416</sessionId>
<bean>
<city>Los Angeles</city>
<address>1A James st</address>
<zipCode>92111</zipCode>
<state>CA</state>
<country>US</country>
<directions>Take the 101 until you find us</directions>
<locationName>Los Angeles</locationName>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 157
<locationId>5</locationId>
<regionId>3</regionId>
<timeZone>America/Los_Angeles</timeZone>
<interviewRooms>
<item>Hollywood</item>
</interviewRooms>
<defaultApprovers>
<item>8</item>
</defaultApprovers>
<phone>800-783-3789</phone>
</bean>
</urn:upsertLocation>
</soapenv:Body>
</soapenv:Envelope>

Output: upsertLocationResponse

Login API Calls

getUrl Element
Operation type: Request-response.
 The endpoint receives a message to get URL of a company code, or customer instance,
and sends a correlated message of URL.
 This call is always performed using URL:
https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter and requires a different
Namespace: urn:TBEDispatcherAPI (vs. urn:TBEWebAPI)

Input: getURLRequest

Data Field Name Data Field Type Required Acceptable Values

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 158
Company Code of
in0 String Yes
Taleo Customer

Output: getURLResponse

Data Field Name Data Field Type Required Acceptable Values

getURLReturn String URL

getURL Test Case:

Input: getURLRequest

<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEDispatcherAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getURL soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<orgCode xsi:type="xsd:string">TALEOSK</orgCode>
</urn:getURL>
</soapenv:Body>
</soapenv:Envelope>

Output: getURLResponse

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<ns1:getURLResponse SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:TBEDispatcherAPI">
<return xsi:type="xsd:string">https://tbe.taleo.net/NA12/ats/services/rpcrouter</return>
</ns1:getURLResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

login Element:
Operation type: Request-response.
 This and all subsequent calls are made using the URL returned by the getURL() method
described above. This call returns session ID to be used in all subsequent calls to TBE
Web API.
 The endpoint receives a message to login to the Taleo Business Edition API, and sends
a correlated message of session ID.
 An existing user needs to be created within the application first, and then can be used
with the Taleo Business Edition API.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 159
 Please Note: login credentials used are subjected to the same user abilities within the
application.

Input: loginRequest

Data Field Name Data Field Type Required Acceptable Values

in0 String Yes Company Code
in1 String Yes User ID
in2 String Yes Password

Output: loginResponse

Data Field Name Data Field Type Required Acceptable Values

loginReturn String Session ID

login Test Case:

Input: loginRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:login>
<in0>ABC_COMPANY</in0>
<in1>API_USER</in1>
<in2>API_PASSWORD</in2>
</urn:login>
</soapenv:Body>
</soapenv:Envelope>

Output: loginResponse

logout Element:
Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 160
 The endpoint receives a message to logout of the Taleo Business Edition API, and sends
a correlated message if error occurred.

Input: logoutRequest

Data Field Name Data Field Type Required Acceptable Values

in0 String Yes Session ID

Output: logoutResponse

Data Field Name Data Field Type Required Acceptable Values

logoutReturn Session ID

logout Test Case:

Input: logoutRequest

Output: logoutResponse

getLoginToken Element:
Operation type: Request-response.
 The endpoint receives a message to retrieve the token results of a login session ID
variable.

Input: getLoginTokenRequest

Data Field Name Data Field Type Required Acceptable Values

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 161
in0 String Yes Session ID

Output: getLoginTokenResponse

Data Field Name Data Field Type Required Acceptable Values

getLoginTokenReturn String Login session ID

getLoginToken Test Case:

Input: getLoginTokenRequest
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getLoginToken>
<sessionId>webapi-7677111958344909818</sessionId>
</urn:getLoginToken>
</soapenv:Body>
</soapenv:Envelope>

Output: getLoginTokenResponse

Metadata / Picklist API Calls

Metadata and picklist fields are any field (standard or custom) that associate drop-down list of
values for data consistency. These picklist values require exact replication to be associated with
the specific call in Taleo Business Edition.

getLookup Element:
Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 162
 The endpoint receives a message to lookup picklist values for a given field, and sends a
correlated message of field picklist values and integration codes (if used).
 Please Note: Response for veteran, race, source, country and state field’s list
integrationCodes (API values defined within the GUI), however these codes cannot
be used against alternative API calls – use only field values for the above
mentioned fields when making appropriate createCandidate, updateCandidate,
getCandidate calls.
 Please Note: getLookup ‘fieldName’ works for standard system fields solely.
Where custom fields require lookup, getLookup call requires actual database field
value. True database field value can be found by ‘View Source’ of the GUI page
displaying the appropriate field:

Input: getLookupRequest

Data Field Name Data Field Type Required Acceptable Values

in0 String Yes Session ID
in1 String Yes fieldName

Output: getLookupResponse

Data Field Name Data Field Type Required Acceptable Values

array of fieldname
values (display name
getLookupReturn
and integration code
name).

getLookup Test Case:

Input: getLookupRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 163
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getLookup>
<in0>webapi-6686750025617579220</in0>
<in1>race</in1>
</urn:getLookup>
</soapenv:Body>
</soapenv:Envelope>

Output: getLookupResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getLookupResponse xmlns="urn:TBEWebAPI">
<getLookupReturn xmlns="">
<array>
<item>
<displayName>Hispanic or Latino</displayName>
<integrationCode>HISP</integrationCode>
</item>
<item>
<displayName>White (not Hispanic or Latino)</displayName>
<integrationCode>WHIT</integrationCode>
</item>
<item>
<displayName>Black or African American (not Hispanic or Latino)</displayName>
<integrationCode>BLCK</integrationCode>
</item>
<item>
<displayName>Native Hawaiian or Other Pacific Islander</displayName>
<integrationCode>PACF</integrationCode>
</item>
<item>
<displayName>Asian (not Hispanic or Latino)</displayName>
<integrationCode>ASIN</integrationCode>
</item>
<item>
<displayName>American Indian or Alaska Native</displayName>
<integrationCode>INDI</integrationCode>
</item>
<item>
<displayName>Two or More Races (not Hispanic or Latino)</displayName>
<integrationCode>MULT</integrationCode>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 164
</item>
<item>
<displayName>Choose Not to Disclose</displayName>
<integrationCode>NDIS</integrationCode>
</item>
</array>
</getLookupReturn>
</getLookupResponse>
</soapenv:Body>
</soapenv:Envelope>

getMetadata Element:
Operation type: Request-response.
 The endpoint receives a message to retrieve all field values within an entity, and sends a
correlated message of all fields within the entity including:
o displayName (application field name)
o integrationName (API / external field name)
o isCustom (whether the field is a standard or custom field in TBE)
o isReadOnly (whether the field is writable or read-only)
o isRequired (whether the field is application-required for data entry)
o type (the type of field defined)

Input: getMetadataRequest

Data Field Name Data Field Type Required Acceptable Values

in0 String Yes Session ID
in1 String Yes Type of related entity:
ACCT = accounts
CAND = candidates
CTCT = contacts
EMPL = employees
REQU = requisitions
WORK = users

Output: getMetadataResponse

Data Field Name Data Field Type Required Acceptable Values

Array of fieldname
values (display name
getMetadataReturn
and integration code
name).

getMetadata Test Case:

Input: getMetadataRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 165
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getMetadata>
<in0>webapi-301034357717673686</in0>
<in1>CAND</in1>
</urn:getMetadata>
</soapenv:Body>
</soapenv:Envelope>

Output: getMetadataResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getMetadataResponse xmlns="urn:TBEWebAPI">
<getMetadataReturn xmlns="">
<array>
<item>
<item>
<displayName>Current Salary.</displayName>
<integrationName>Current Salary</integrationName>
<isCustom>true</isCustom>
<isReadOnly>false</isReadOnly>
<isRequired>false</isRequired>
<type>FieldCurrency</type>
</item>
<item>
<displayName>Current User Department</displayName>
<integrationName>currUserDept</integrationName>
<isCustom>false</isCustom>
<isReadOnly>true</isReadOnly>
<isRequired>false</isRequired>
<type>CurrUserDepartment</type>
</item>
<item>
<displayName>Last updated</displayName>
<integrationName>lastUpdated</integrationName>
<isCustom>false</isCustom>
<isReadOnly>true</isReadOnly>
<isRequired>false</isRequired>
<type>FieldDateLong</type>
</item>
<item>
<displayName>Mobile #</displayName>
<integrationName>cellPhone</integrationName>
<isCustom>false</isCustom>
<isReadOnly>false</isReadOnly>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 166
<isRequired>false</isRequired>
<type>FieldPhone</type>
</item>
<item>
<displayName>Work Authorization</displayName>
<integrationName>legalStatus</integrationName>
<isCustom>false</isCustom>
<isReadOnly>false</isReadOnly>
<isRequired>false</isRequired>
<type>FieldSingleList</type>
</item>
<item>
<displayName>ZIP/Postal code</displayName>
<integrationName>zipCode</integrationName>
<isCustom>false</isCustom>
<isReadOnly>false</isReadOnly>
<isRequired>false</isRequired>
<type>FieldTextLang</type>
</item>
</array>
</getMetadataReturn>
</getMetadataResponse>
</soapenv:Body>
</soapenv:Envelope>

Offer API Calls

Offers are details and original offer letters associated with any candidate in Taleo Business
Edition. Similar to background checks, there is a one-to-many relationship with references to
candidates.

offerBean Definition:

Data Field Name Data Field Type Required Acceptable Values

id long Offer’s unique server side ID. Can be
obtained enumerating offers for
Read Only
particular candidate or by creating a
new offer.
status String Yes Offer’s Status from pick list
manager String Yes Login name of offer’s manager
candidateId long Yes Id of candidate related to this offer
requisitioned long Yes Id of requisition related to this offer
creator String Read Only Login name of user who has created
this offer
title String Yes Title of position offered
employmentType String Type of employment (from pick list)
Yes
offered

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 167
payRate String No Pay rate (free text) offered
stockOptions String No Stock options (free text) offered
startDate Date No Date when employment will start
expirationDate Date No Date when offer will expire
offerFileName String Read Only Binary offer file name
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
flexValues FlexFieldBean[] No Array of flexible (custom) field values

flexFieldBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
FieldName String Yes Field name
Value of Text, Email, URL, Pick list, or
StringValue String No Text Area field. For Multiple Pick list use
‘|’ to separate values.
IntValue int No Value of Integer field
DoubleValue double No Value of Decimal or Currency field
BooleanValue boolean No Value of Check Box field
DateValue Date No Value of Date field

createOffer Element:
Operation type: Request-response.
 The endpoint receives a message to create an offer for a specific candidate, and sends a
correlated message of offer ID.

Input: createOfferRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status *
candidateId *
employmentType *
expirationDate
manager *
in1 offerBean [] *
offerFileName
payRate
requisitionId *
startDate
stockOptions
title *

Output: createOfferResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 168
Data Field Name Data Field Type Required Acceptable Values
createOfferReturn Long Yes Provided Offer ID

createOffer Test Case:

Input: createOfferRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createOffer>
<in0>webapi411835895647962205</in0>
<in1>
<flexValues>

</flexValues>
<status>New</status>
<candidateId>48</candidateId>
<employmentType>Full time</employmentType>
<expirationDate>2010-06-30T23:01:26.493Z</expirationDate>
<manager>skarim</manager>
<offerFileName>test1.docx</offerFileName>
<payRate>50000</payRate>
<requisitionId>13</requisitionId>
<startDate>2009-06-30T23:01:26.493Z</startDate>
<stockOptions>True</stockOptions>
<title>Offer Business Development</title>
</in1>
</urn:createOffer>
</soapenv:Body>
</soapenv:Envelope>

Output: createOfferResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 169
deleteOffer Element:
Operation type: Request-response.
 The endpoint receives a message to delete an offer instance, and sends a correlated
message only if error occurred.

Input: deleteOfferRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Offer ID Yes ID of Offer

Output: deleteOfferResponse

Data Field Name Data Field Type Required Acceptable Values

deleteOfferReturn

deleteOffer Test Case:

Input: deleteOfferRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteOffer>
<in0>webapi8016094028063300532</in0>
<in1>4</in1>
</urn:deleteOffer>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteOfferResponse

getBinaryOffer Element:
Operation type: Request-response.
 The endpoint receives a message to get the offer letter binary attachment associated with
a candidate (based on offer ID), and sends back the resume binary offer letter data.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 170
Input: getBinaryOfferRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of offer instance

Output: getBinaryResumeResponse

Data Field Name Data Field Type Required Acceptable Values

getBinaryOfferReturn base64Binary []

Input: getBinaryOfferRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn: getBinaryOffer>
<in0>webapi1673199911353581754</in0>
<in1>41</in1>
</urn: getBinaryOffer>
</soapenv:Body>
</soapenv:Envelope>

Output: getBinaryOfferResponse

getOfferByID
Operation type: Request-response.
 The endpoint receives a message to get offer details by offer ID, and sends a correlated
message of offer information.

Input: getOfferByIdRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 171
Data Field Name Data Field Type Required Acceptable Values
Session ID received
in0 String Yes
at Login
in1 Offer ID Yes ID of Offer Instance

Output: getOfferByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getOfferByIdReturn referenceBean []

getOfferById Test Case:

Input: getOfferByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getOfferById>
<in0>webapi8016094028063300532</in0>
<in1>3</in1>
</urn:getOfferById>
</soapenv:Body>
</soapenv:Envelope>

Output: getOfferByIdResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 172
<title>Offer Business Development</title>
</getOfferByIdReturn>
</getOfferByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getOffers Element:
Operation type: Request-response.
 The endpoint receives a message to get offer(s) associated with any Taleo Business
Edition candidate, and sends back offer IDs associated with the candidate ID.

Input: getOffersRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of candidate

Output: getOffersResponse

Data Field Name Data Field Type Required Acceptable Values

getOffersReturn array of offer IDs

getOffers Test Case:

Input: getOffersRequest

Output: getOffersResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 173
<getOffersReturn xmlns="">
<array>
<item>3</item>
<item>2</item>
<item>1</item>
</array>
</getOffersReturn>
</getOffersResponse>
</soapenv:Body>
</soapenv:Envelope>

setBinaryOffer
Operation type: Request-response.
 The endpoint receives a message to append an offer letter attachment by offer ID, and
sends a correlated message only if error occurred.

Input: setBinaryOfferRequest

Data Field Data Field Required

Acceptable Values
Name Type
in0 String Yes Session ID received at Login
in1 Offer ID Yes ID of Offer Instance
Filename of binary file with defined file
extension. The following MIME types are
acceptable:
Text = text/plain
html = text/html
in2 String Yes RTF = text/richtext
Word = application/msword
DocX =
application/vnd.openxmlformats-
officedocument.wordprocessingml.document
PDF = application/pdf
in3 ByteArr Yes base64Binary []

Output: setBinaryOfferResponse

Data Field Name Data Field Type Required Acceptable Values

setBinaryOfferReturn

setBinaryOffer Test Case:

Input: setBinaryOfferRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 174
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:setBinaryOffer>
<in0>webapi8016094028063300532</in0>
<in1>2</in1>
<in2>offer_letter.doc</in2>
<in3>
<array>e1xydGYxXGFuc2lcYW5zaWNwZzEyNTJcdWMxIFxkZWZmM==</array>
</in3>
</urn:setBinaryOffer>
</soapenv:Body>
</soapenv:Envelope>

Output: setBinaryOfferResponse

updateOffer Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing offer instance, and sends a
correlated message only if error occurred.
 Please Note: Update requests replace all data fields in the offerBean (i.e. data is not
appended or upserted). Send all elements back or the field values will be returned NULL.

Input: updateOfferRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
id *
status *
candidateId *
in1 offerBean[] * creator
employmentType
expirationDate
manager *
offerFileName

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 175
payRate
requisitionId *
startDate
stockOptions
title *

Output: updateOfferResponse

Data Field Name Data Field Type Required Acceptable Values

updateOfferReturn

updateOffer Test Case:

Input: updateOfferRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateOffer>
<in0>webapi-5084000498747541653</in0>
<in1>
<flexValues>

</flexValues>
<id>1</id>
<status>Draft</status>
<candidateId>48</candidateId>
<creator>destey</creator>
<employmentType>Full time</employmentType>
<expirationDate>2010-06-30T23:01:26.493Z</expirationDate>
<manager>skarim</manager>
<offerFileName>test1.docx</offerFileName>
<payRate>75000</payRate>
<requisitionId>13</requisitionId>
<startDate>2009-06-30T23:01:26.493Z</startDate>
<stockOptions>True</stockOptions>
<title>Bus Dev Manager</title>
</in1>
</urn:updateOffer>
</soapenv:Body>
</soapenv:Envelope>

Output: updateOfferResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 176
<updateOfferResponse xmlns="urn:TBEWebAPI"/>
</soapenv:Body>
</soapenv:Envelope>

Reference API Calls

References are personal references associated with any candidate in Taleo Business Edition.
Similar to background checks, there is a one-to-many relationship with references to candidates.

referenceBean Definition:

Data Field Name Data Field Type Required Acceptable Values

id long Account’s unique server side ID. Can be
Read Only obtained by searching the accounts’
database or by creating a new account.
status String Yes Account’s Status from pick list
creator String No Creator’s login name
candidateId long Yes ID of candidate
refName String Yes Reference's name
refPhone String No Reference's phone
refEmail String No Reference's email
refTitle String No Reference's title
employer String No Employer’s name
relToCandidate String No Relation to candidate
comments String No Comments
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
flexValues FlexFieldBean[] No Array of flexible (custom) field values

flexFieldBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
FieldName String Yes Field name
Value of Text, Email, URL, Pick list, or
StringValue String No Text Area field. For Multiple Pick list use
‘|’ to separate values.
IntValue int No Value of Integer field
DoubleValue double No Value of Decimal or Currency field
BooleanValue boolean No Value of Check Box field
DateValue Date No Value of Date field

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 177
createReference Element:
Operation type: Request-response.
 The endpoint receives a message to create a reference for a specific candidate, and
sends a correlated message of reference ID.

Input: createReferenceRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status *
candidateId *
comments
creator
in1 referenceBean [] * employer
refEmail
refName *
refPhone
refTitle
relToCandidate

Output: createReferenceResponse

Data Field Name Data Field Type Required Acceptable Values

Provided Reference
createReferenceReturn Long Yes
ID

createReference Test Case:

Input: createReferenceRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createReference>
<in0>webapi411835895647962205</in0>
<in1>
<flexValues>

</flexValues>
<status>New</status>
<candidateId>48</candidateId>
<comments>Candidate's major strength is selling and buying</comments>
<creator>skarim</creator>
<employer>Nordstroms</employer>
<refEmail>[email protected]</refEmail>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 178
<refName>Sally Store</refName>
<refPhone>948-234-4958</refPhone>
<refTitle>Manager</refTitle>
<relToCandidate>Direct Manager</relToCandidate>
</in1>
</urn:createReference>
</soapenv:Body>
</soapenv:Envelope>

Output: createReferenceResponse

deleteReference Element:
Operation type: Request-response.
 The endpoint receives a message to delete a reference instance, and sends a correlated
message only if error occurred.

Input: deleteReferenceRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Reference ID Yes ID of Reference

Output: deleteReferenceResponse

Data Field Name Data Field Type Required Acceptable Values

deleteReferenceReturn

deleteReference Test Case:

Input: deleteReferenceRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 179
<soapenv:Body>
<urn:deleteReference>
<in0>webapi411835895647962205</in0>
<in1>3</in1>
</urn:deleteReference>
</soapenv:Body>
</soapenv:Envelope>
Output: deleteReferenceResponse

getReferencesByCandidate Element:
Operation type: Request-response.
 The endpoint receives a message to get reference(s) associated with any Taleo Business
Edition candidate, and sends back reference IDs associated with the candidate ID.

Input: getReferencesByCandidateRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of candidate

Output: getReferencesByCandidateResponse

Required Acceptable
Data Field Name Data Field Type
Values
array of reference
getReferencesByCandidateReturn
IDs

getReferencesByCandidate Test Case:

Input: getReferencesByCandidateRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getReferencesByCandidate>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 180
<in0>webapi411835895647962205</in0>
<in1>48</in1>
</urn:getReferencesByCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: getReferencesByCandidateResponse

getReferenceById Element:
Operation type: Request-response.
 The endpoint receives a message to get reference details by reference ID, and sends a
correlated message of reference information.

Input: getReferenceByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
ID of Reference
in1 Reference ID Yes
Instance

Output: getReferenceByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getReferenceByIdReturn referenceBean []

getReferenceById Test Case:

Input: getReferenceByIdRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 181
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getReferenceById>
<in0>webapi411835895647962205</in0>
<in1>1</in1>
</urn:getReferenceById>
</soapenv:Body>
</soapenv:Envelope>

Output: getReferenceByIdResponse

updateReference Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing reference instance, and sends a
correlated message only if error occurred.
 Please Note: Update requests replace all data fields in the referenceBean (i.e. data is not
appended or upserted). Send all elements back or the field values will be returned NULL.

Input: updateReferenceRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 182
Data Field Name Data Field Type Required Acceptable Values
Session ID received
in0 String Yes
at Login
flexValues []
id *
status *
candidateId *
comments
creator
in1 referenceBean[] *
employer
refEmail
refName *
refPhone
refTitle
relToCandidate

Output: updateReferenceResponse

Data Field Name Data Field Type Required Acceptable Values

updateReferenceReturn

updateReference Test Case:

Input: updateReferenceRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateReference>
<in0>webapi411835895647962205</in0>
<in1>
<flexValues>

</flexValues>
<id>2</id>
<status>Submitted</status>
<candidateId>48</candidateId>
<comments>Reference Completed - candidate successful</comments>
<creator>skarim</creator>
<employer>Nordstroms</employer>
<refEmail>[email protected]</refEmail>
<refName>Jason Nord</refName>
<refPhone>829-239-2394</refPhone>
<refTitle>Director</refTitle>
<relToCandidate>Manager's manager</relToCandidate>
</in1>
</urn:updateReference>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 183
Output: updateReferenceResponse

Region API Calls

Regions are groupings either allocated to locations or to departments. This provides grouping
access for user’s vs single department/location permissions.

regionBean Definition:

Data Field Name Data Field Type Required Acceptable Values

Account’s unique
server side ID. Can be
obtained by searching
regionId Long Read Only the accounts’
database or by
creating a new
account.
regionName String Yes region name
defaultApprovers Long[] No Array of user ID’s

**Allows you to
identify which users
are assigned for
approvals to this
region
associatedUsers Long[] No Array of user ID’s

**Allows you to
identify which users
will be assigned to
this region
associatedLocations Long[] No Array of location
Names

**Allows you to
identify which
locations are assigned

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 184
to this region
additionalProperties Map No Used for expansion
calls
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date

createRegion Element:
Operation type: Request-response.
 The endpoint receives a message to create a Region, and sends a correlated message
of Region ID.

Input: createRegionRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
AdditionalProperties[]
regionName
in1 RegionBean * associatedLocations
associatedUsers
defaultApprovers

Output: createRegionResponse

Data Field Name Data Field Type Required Acceptable Values

createRegionReturn Long Yes Provided Region ID

createRegionTest Case:

Input: createRegionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createRegion>
<in0>webapi-464745806681923416</in0>
<in1>
<regionName xmlns="">Northwest</regionName>
<associatedLocations xmlns="">
<item>San Francisco</item>
<item>Seattle Office</item>
</associatedLocations>
<associatedUsers xmlns="">
<item>3</item>
<item>9</item>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 185
<item>10</item>
<item>15</item>
<item>28</item>
</associatedUsers>
<defaultApprovers xmlns="">
<item>3</item>
<item>28</item>
<item>15</item>
<item>10</item>
<item>9</item>
</defaultApprovers>
</in1>
</urn:createRegion>
</soapenv:Body>
</soapenv:Envelope>

Output: createRegionResponse

deleteRegion Element:
Operation type: Request-response.
 The endpoint receives a message to delete a Region, and sends a correlated message
only if error occurred.

Input: deleteRegionRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Region ID Yes ID of Region

Output: deleteRegionResponse

Data Field Name Data Field Type Required Acceptable Values

deleteRegionReturn

deleteRegion Test Case:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 186
Input: deleteRegionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteRegion>
<in0>webapi-464745806681923416</in0>
<regionId>6</regionId>
</urn:deleteRegion>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteRegionResponse

getRegionById Element:
Operation type: Request-response.
 The endpoint receives a message to get a Region details, and sends a correlated
message of Region information.

Input: getRegionByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Region ID Yes ID of Region

Output: getRegionByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getRegionByIdReturn RegionBean

getRegionById Test Case:

Input: getRegionByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 187
<urn:getRegionById>
<in0>webapi-464745806681923416</in0>
<in1>6</in1>
</urn:getRegionById>
</soapenv:Body>
</soapenv:Envelope>

Output: getRegionByIdResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getRegionByIdResponse xmlns="urn:TBEWebAPI">
<getRegionByIdReturn>
<additionalProperties xmlns="">
<item xmlns:ns1="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string">3,28,15,10,9</value>
</item>
</additionalProperties>
<creationDate xmlns="">2011-08-22T04:29:53.504Z</creationDate>
<lastUpdated xmlns="">2011-08-22T04:29:53.504Z</lastUpdated>
<regionId xmlns="">6</regionId>
<regionName xmlns="">Northwest</regionName>
<associatedLocations xmlns="">
<item>San Francisco</item>
<item>Seattle Office</item>
</associatedLocations>
<associatedUsers xmlns="">
<item>3</item>
<item>9</item>
</associatedUsers>
<defaultApprovers xmlns="">
<item>3</item>
<item>28</item>
</defaultApprovers>
</getRegionByIdReturn>
</getRegionByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getRegionByName Element:
Operation type: Request-response.
 The endpoint receives a message to get a Region details, and sends a correlated
message of Region information.

Input: getRegionByNameRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 188
Data Field Name Data Field Type Required Acceptable Values
Session ID received
in0 String Yes
at Login
in1 Region Name Yes Name of Region

Output: getRegionByNameResponse

Data Field Name Data Field Type Required Acceptable Values

getRegionByIdReturn RegionBean

getRegionByName Test Case:

Input: getRegionByNameRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getRegionByName>
<in0>webapi-464745806681923416</in0>
<in1>West</in1>
</urn:getRegionByName>
</soapenv:Body>
</soapenv:Envelope>

Output: getRegionByNameResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 189
</soapenv:Envelope>

getRegions Element:
Operation type: Request-response.
 The endpoint receives a message to get all Regions and sends a correlated message of
Region information. This functions similar to getLookUp Request.

Input: getRegionsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login

Output: getRegionsResponse

Data Field Name Data Field Type Required Acceptable Values

getRegionsReturn RegionArray []

getRegions Test Case:

Input: getRegionsRequest

Output: getRegionsResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 190
</additionalProperties>
<creationDate>2008-11-25T00:00:00.000Z</creationDate>
<lastUpdated>2008-11-25T00:00:00.000Z</lastUpdated>
<regionId>2</regionId>
<regionName>West</regionName>
<associatedLocations>
<item>San Francisco</item>
<item>Seattle Office</item>
</associatedLocations>
<associatedUsers/>
<defaultApprovers xsi:nil="true"/>
</item>
<item>
<additionalProperties>
<item xmlns:ns2="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string"/>
</item>
</additionalProperties>
<creationDate>2008-11-25T00:00:00.000Z</creationDate>
<lastUpdated>2008-11-25T00:00:00.000Z</lastUpdated>
<regionId>1</regionId>
<regionName>East</regionName>
<associatedLocations>
<item>Boston Office</item>
</associatedLocations>
<associatedUsers/>
<defaultApprovers xsi:nil="true"/>
</item>
<item>
<additionalProperties>
<item xmlns:ns3="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string"/>
</item>
</additionalProperties>
<creationDate>2008-11-25T00:00:00.000Z</creationDate>
<lastUpdated>2008-11-25T00:00:00.000Z</lastUpdated>
<regionId>4</regionId>
<regionName>South</regionName>
<associatedLocations xsi:nil="true"/>
<associatedUsers/>
<defaultApprovers xsi:nil="true"/>
</item>
<item>
<additionalProperties>
<item xmlns:ns4="http://xml.apache.org/xml-soap">
<key xsi:type="xsd:string">userRequisitionApproverIds</key>
<value xsi:type="xsd:string"/>
</item>
</additionalProperties>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 191
<creationDate>2008-11-25T00:00:00.000Z</creationDate>
<lastUpdated>2008-11-25T00:00:00.000Z</lastUpdated>
<regionId>3</regionId>
<regionName>North</regionName>
<associatedLocations xsi:nil="true"/>
<associatedUsers/>
<defaultApprovers xsi:nil="true"/>
</item>
</array>
</getRegionsReturn>
</getRegionsResponse>
</soapenv:Body>
</soapenv:Envelope>

upsertRegion Element:
Operation type: Request-response.
 The endpoint receives a message to update or create a Region instance, and sends a
correlated message only if error occurred.
 Please Note: Upsert is used to both create or update data within a specific Region. Using
the Region ID AND Region Name attribute updates or replaces existing Region details.

Input:upsertRegionRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
AdditionalProperties[]
RegionID*
RegionName*
in1 RegionBean *
associatedUsers
assocatedLocations
defaultApprovers

Output: upsertRegionResponse

Data Field Name Data Field Type Required Acceptable Values

upsertRegionReturn

upsertRegionTest Case:

Input: upsertRegionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 192
<soapenv:Body>
<urn:upsertRegion>
<sessionId>webapi-464745806681923416</sessionId>
<bean>
<regionId>3</regionId>
<regionName>North</regionName>
<associatedLocations>

<item>Seattle Office</item>
</associatedLocations>
<associatedUsers>

<item>5</item>
</associatedUsers>
<defaultApprovers>

<item>5</item>
</defaultApprovers>
</bean>
</urn:upsertRegion>
</soapenv:Body>
</soapenv:Envelope>
Output: upsertRegionResponse

Requisition API Calls

Requisitions are all of the job openings you want to track in Taleo Business Edition and post on
your careers website.

*** 11.3 enhancement now allows assignment of department and receiving department via
requistionBean. Please note, to support backwards compatability, this field is featured within the
flexFieldBean definition. For assigning departments, use flexField, either by long
<departmentID> or string <departmentName>.

requisitionBean Definition:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 193
Data Field Name Data Field Type Required Acceptable Values
Requisition’s unique server side ID. Can
be obtained by searching the requisition
id long Read Only
database or by creating a new
requisition.
status String Yes Requisition’s Status name from pick list
title String Yes Requisition’s title
Name of location (from pick list)
location String Yes
assigned to this requisition
duration String No Requisition’s type from pick list
payRange String No Pay range
description String No Requisition’s description
jobCategory String No EEO Job category name from pick list
jobCode String No Job code
numOpen int No Number of openings
openedDate Date No Date when this requisition was opened
filledDate Date No Date when this requisition was filled
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
flexValues FlexFieldBean[] No Array of flexible (custom) field values

flexFieldBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
fieldName String Yes Field name
Value of Text, Email, URL, Pick list, or
stringValue String No Text Area field. For Multiple Pick list use
‘|’ to separate values.
intValue int No Value of Integer field
doubleValue double No Value of Decimal or Currency field
booleanValue boolean No Value of Check Box field
dateValue Date No Value of Date field

createRequisition Element:
Operation type: Request-response.
 The endpoint receives a message to create a requisition, and sends a correlated
message of requisition ID.

Input: createRequisitionRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 requisitionBean [] * flexValues []

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 194
status *
description
duration
jobCategory
jobCode
location *
numOpen
openedDate
payRange
title *
filledDate

Output: createRequisitionResponse

Data Field Name Data Field Type Required Acceptable Values

Provided Requisition
createRequsitionReturn Long Yes
ID

createRequisition Test Case:

Input: createRequisitionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createRequisition>
<in0>webapi-8638387102069848283</in0>
<in1>
<flexValues>
<item>
<fieldName>department</fieldName>
<valueStr>Customer Service</valueStr>
</item>
</flexValues>
<status>Waiting for Approval</status>
<description>The Human Resources Generalist originates and leads Human
Resources practices and objectives that will provide an employee-oriented, high
performance culture that emphasizes empowerment, quality, productivity and standards,
goal attainment, and the recruitment and ongoing development of a superior workforce.
The Human Resources Generalist coordinates implementation of services, policies, and
programs through Human Resources staff; reports to the Human Resources Director, and
assists and advises company managers about Human Resources issues.</description>
<duration>Full time</duration>
<jobCategory>Professionals</jobCategory>
<jobCode>Level 1</jobCode>
<location>Headquarters</location>
<numOpen>3</numOpen>
<openedDate>2009-06-30T23:01:26.493Z</openedDate>
<payRange>50000 - 75000</payRange>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 195
<title>HR Generalist</title>
</in1>
</urn:createRequisition>
</soapenv:Body>
</soapenv:Envelope>

Output: createRequisitionResponse

createRequisitionTemplate Element:
Operation type: Request-response.
 Templates are the available jobs preloaded in Taleo for users to post easily with
consistency. They are stored in the job library.
 Click on the appropriate Template below to start the process of composing a requisition
The endpoint receives a message to create a requisition template, and sends a
correlated message of requisition ID.

Input: createRequisitionTemplateRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status *
city
description
duration
jobCategory
jobCode
in1 requisitionBean [] *
location *
numOpen
openedDate
payRange
state
title *
filledDate

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 196
Output: createRequisitionTemplateResponse

Data Field Name Data Field Type Required Acceptable Values

Provided
createRequisitionTemplateReturn Long Yes
Requisition ID

createRequisitionTemplate Test Case:

Input: createRequisitionTemplateRequest

Output: createRequisitionTemplateResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 197
</createRequisitionTemplateResponse>
</soapenv:Body>
</soapenv:Envelope>

deleteRequisition Element:
Operation type: Request-response.
 The endpoint receives a message to delete a requisition instance, and sends a correlated
message only if error occurred.

Input: deleteRequisitionRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Requisition ID Yes ID of Requisition

Output: deleteRequisitionResponse

Data Field Name Data Field Type Required Acceptable Values

deleteRequisitionReturn

deleteRequisition Test Case:

Input: deleteRequisitionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteRequisition>
<in0>webapi-8638387102069848283</in0>
<in1>22</in1>
</urn:deleteRequisition>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteRequisitionResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 198
getRequisitionById Element:
Operation type: Request-response.
 The endpoint receives a message to get requisition details by requisition ID, and sends a
correlated message of requisition information.

Input: getRequisitionByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
ID of Requisition
in1 Requisition ID Yes
Instance

Output: getRequisitionByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getRequisitionByIdReturn requisitionBean []

getRequisitionById Test Case:

Input: getRequisitionByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getRequisitionById>
<in0>webapi-8638387102069848283</in0>
<in1>13</in1>
</urn:getRequisitionById>
</soapenv:Body>
</soapenv:Envelope>

Output: getRequisitionByIdResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 199
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>Job Reason</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>Resignation</valueStr>
</item>
<item>
<fieldName>Budgeted</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>Budgeted</valueStr>
</item>
<item>
<fieldName>department</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong>4</valueLong>
<valueStr>Customer Service</valueStr>
</item>
</flexValues>
<id>13</id>
<lastUpdated>2009-02-25T23:34:37.537Z</lastUpdated>
<status>Open</status>
<city>Queens</city>
<description><![CDATA[DESCRIPTION OF JOB
DUTIES:
·     Pursue and qualify new
leads from new clients, existing clients, and other Idea offices 
·     Sell IT solutions/services from our core offerings to
the clients 
·      Build successful client relationships &
manage existing client relationships to ensure client satisfaction and identify new
opportunities within existing projects 
·     Adhere to established sales and workflow
processes 
·     Give capabilities presentations to clients

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 200
·     Work closely with the Solution Director to draft
proposals and/or statements of work 
·     Responsible for providing accurate estimates for
budgets and time lines in proposals 
·     Handle all aspects of pre-engagement activity and
the transition of projects to Project Managers 
·     Participate and collaborate in all sales meetings 
·     Provide Weekly updates to Managing Director

 
REQUIRED EXPERIENCE: 
• Have demonstrated successful experience identifying,
qualifying, and closing new business opportunities 
• Have successful sales experience focusing on commercial and/or federal sales 
• Experience successfully marketing and selling professional and IT
services/solutions in one or more of the following areas (Custom Application
Development, Data Warehousing, Security & Infrastructure, Business Intelligence, IT
Security, CRM, SAS and/or Legacy) 
• Significant knowledge of and successful experience using IT solutions sales
techniques and models 
• Minimum 7 years of business development and solutions sales
experience
 ]]></description>
<duration>FULLTIME</duration>
<filledDate xsi:nil="true"/>
<jobCategory xsi:nil="true"/>
<jobCode>452346</jobCode>
<location>NY Office</location>
<numOpen>4</numOpen>
<openedDate>2009-02-25T00:00:00.000Z</openedDate>
<payRange/>
<state>US-NY</state>
<title>Business Development Manager</title>
</getRequisitionByIdReturn>
</getRequisitionByIdResponse>
</soapenv:Body>
</soapenv:Envelope>

getRequisitionHistory Element:
Operation type: Request-response.
 The endpoint receives a message to get a Requisition transaction history, and sends a
correlated message of transaction history for the specific requisition ID.
 This object is used to fetch a history log entry which reflects a past event or action related
to requisition. History records can only be created by the server, they cannot be modified
or deleted. History log includes server side ID, test describing history record, complete
text of email message (for email events) and creation date.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 201
Input: getRequisitionHistoryRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Requisition ID Yes ID of Requisition

Output: getRequisitionHistoryResponse

Data Field Name Data Field Type Required Acceptable Values

getRequisitionHistoryReturn historyBean []

getRequisitionHistory Test Case:

Input: getRequisitionHistoryRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getRequisitionHistory>
<in0>webapi-8638387102069848283</in0>
<in1>11</in1>
</urn:getRequisitionHistory>
</soapenv:Body>
</soapenv:Envelope>

Output: getRequisitionHistoryResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 202
<text>Candidate (id: 48) (id: 48) Alisha Alexandra Smith added self to this
requisition</text>
<userName xsi:nil="true"/>
</item>
<item>
<creationDate>2009-02-09T23:03:51.623Z</creationDate>
<emailText xsi:nil="true"/>
<id>99</id>
<text>Posted on Careers Website</text>
<userName xsi:nil="true"/>
</item>
<item>
<creationDate>2009-02-09T23:03:51.430Z</creationDate>
<emailText xsi:nil="true"/>
<id>94</id>
<text>Requisition created</text>
<userName>skarim</userName>
</item>
<item>
<creationDate>2009-02-09T23:03:51.430Z</creationDate>
<emailText xsi:nil="true"/>
<id>97</id>
<text>Approver (id: 7) Karim, Sally has been added to this requisition</text>
<userName>skarim</userName>
</item>
<item>
<creationDate>2009-02-09T23:03:51.430Z</creationDate>
<emailText xsi:nil="true"/>
<id>98</id>
<text>Offer Approver has been added to this requisition</text>
<userName>skarim</userName>
</item>
</array>
</getRequisitionHistoryReturn>
</getRequisitionHistoryResponse>
</soapenv:Body>
</soapenv:Envelope>

postRequisition Element:
Operation type: Request-response.
 The endpoint receives a message to post a specific requisition to a supported posting
location, and sends back a message only if error occurred.
 Please note, requisitions will only be posted if the requisition has been approved (i.e.
status of ‘Open’) and all other requisition data elements have been completed that are
mandatory based on the application UI (i.e. Requisition Owner has been defined).

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 203
 Please Note: As each client may be able to configure multiple posting locations and
multiple application form versions, a standard list of ‘posterId’ and ‘formVersion’ variables
has not been provided. The easiest way to find these values is to go into the application
and:
o Select a requisition
o Right click the page and select ‘View Source’.
o Search for ‘Requisition Posters:’
o From here you will find a list of appropriate ID values

Input: postRequisitionRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
sessionId String Yes
at Login
requisitionId Long Yes ID of requisition
ID of the posting
location, for example
a specific Taleo
posterId Long Yes
Business Edition
Career Website
(picklist value ID #)
ID of the required
application form to be
formVersion Long Yes used within the
posting location
(picklist value ID #).

Output: postRequisitionResponse

Data Field Name Data Field Type Required Acceptable Values

postRequisitionReturn

Input: postRequisitionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:postRequisition>
<sessionId>webapi-8638387102069848283</sessionId>
<requisitionId>16</requisitionId>
<posterId>4</posterId>
<formVersion>0</formVersion>
</urn:postRequisition>
</soapenv:Body>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 204
</soapenv:Envelope>

Output: postRequisitionResponse

searchRequisition Element:
Operation type: Request-response.
 The endpoint receives a message to query all requisitions based on defined key (field
name) and value (data looking for), and sends a correlated message of Requisition ID
and associated search relevance.
 Relevance is a value between 0 and 100, which reflects how well the account matches
the search criteria
 Map of search parameters always contains:
o key: name of field to search as a string
o value: search parameter as string.
 Format of search value may differ depending on data type of the search field:
 For text, text area, email, URL fields: simple text to be found (case-insensitive) in this
field. Example:
o key=”city”, value=”Francisco” will search for all candidates with ”Francisco” in
“city” field.
 For integer, double, currency: interval between two numbers separated by ‘|’ character.
Either left (from) or right (to) side can be omitted. Example:
o key=”rank”, value=”100|” will search for all candidates with rank value no less
than 100.
o key=”rank”, value=”|200” will search for all candidates with rank value no more
than 200.
o key=”rank”, value=”100|200” will search for all candidates with rank value
between 100 and 200 (inclusive).
 For date fields: interval between two dates in ISO yyyy-MM-dd format, separated by ‘|’
character. Either left (from) or right (to) side can be omitted. Example:
o key=”startDate”, value=”2004-06-01|” will search for all candidates with start date
on or after June 1st 2004.
o key=”startDate”, value=”|2004-08-01” will search for all candidates with start date
on or before August 1st 2004.
o key=”startDate”, value=”2004-06-01|2004-08-01” will search for all candidates
with start date between June 1st 2004 and August 1st 2004 (inclusive).
 For date interval fields: number of days from today to the past. Example:
o key=” addedWithin”, value=”7” will search for all candidates added to the system
within the last week.
 For single pick list: code value or name of selected item. Example:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 205
o key=”country”, value=”US” will search for all candidates with country field equals
to “United States”.
o key=”status”, value=”available” will search for all candidates in “Available” status.
 For multiple pick list: code values or names of selected items, separated by ‘|’ character.
Example:
o key=”customMultiple”, value=”A1|B2|X5” will search for all candidates with
customMultiple field containing one or more of values: A1, B2, X5.
 For check box fields: “true” if check box must be checked, “false” is unchecked. Example:
o key=” flagged”, value=”true” will search for all candidates “flagged” for the user
currently logged in.
 Search keys names and types can be found in Administration>Customize>Requisition
Fields. They may include both system fields (listed below for convenience) and custom
fields. For custom fields External name is used as key name.

System Search Keys:

Data Field Name Parameter Type Description

Keyword(s) in requisition’s description.
keyword String Identical syntax as used in Taleo browser
interface.
reqId Integer ID of requisition
Which Career Website requisition was
cws Pick list posted on (i.e. find all jobs posted on cws
1).
jobCode String Job Code
title String Requisition’s title
location Pick list Location assigned to requisition
city String City name
state Pick list State/Region
duration Pick list Duration name
payRange String Pay range
openedDate Date Opened date
filledDate Date Filled date
jobCat Pick list EEO job category
status Pick list Requisition’s status name
lastUpdated Date Last updated date
creationDate Date Added to system date
addedWithin Integer Added within N days
updatedWithin Integer Updated within N days
owners Custom Requisition Owners
approvers Custom Requisition Approvers
offerApprs Custom Offer Approvers
viewers Custom Agencies
When isTemplate flag ‘true’, searching will
return Job Library Templates, when not
isTemplate Boolean passed AT ALL or passed as ‘false’, only
true requisitions will be searched (mutually
exclusive).

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 206
Input: searchRequisitionRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
key
in1 Item… Yes
value

Output: searchRequisitionResponse

Data Field Name Data Field Type Required Acceptable Values

searchRequisitionReturn searchResultBean []

searchRequisition Test Case:

Input: searchRequisitionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:searchRequisition>
<in0>webapi-8638387102069848283</in0>
<in1>

<item>
<key>location</key>
<value>Headquarters</value>
</item>
<item>
<key>status</key>
<value>Open</value>
</item>
<item>
<key>jobCode</key>
<value>Level 1</value>
</item>
</in1>
</urn:searchRequisition>
</soapenv:Body>
</soapenv:Envelope>

Output: searchRequisitionResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 207
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<searchRequisitionResponse xmlns="urn:TBEWebAPI">
<searchRequisitionReturn xmlns="">
<array>
<item>
<id>16</id>
<relevance>1.0</relevance>
</item>
</array>
</searchRequisitionReturn>
</searchRequisitionResponse>
</soapenv:Body>
</soapenv:Envelope>

unpostRequisition Element:
Operation type: Request-response.
 The endpoint receives a message to unpost a specific requisition to a posting location,
and sends back a message only if error occurred.
 Please Note: As each client may be able to configure multiple posting locations, a
standard list of ‘posterId’ variables has not been provided. The easiest way to find these
values is to go into the application and:
o Select a requisition
o Right click the page and select ‘View Source’.
o Search for ‘Requisition Posters:’
o From here you will find a list of appropriate ID values of posting locations
(posterId)

Input: unpostRequisitionRequest

Data Field Name Data Field Type Required Acceptable Values

Output: unpostRequisitionResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 208
Data Field Name Data Field Type Required Acceptable Values
unpostRequisitionReturn

Input: unpostRequisitionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:unpostRequisition>
<sessionId>webapi-8638387102069848283</sessionId>
<requisitionId>16</requisitionId>
<posterId>1</posterId>
</urn:unpostRequisition>
</soapenv:Body>
</soapenv:Envelope>

Output: unpostRequisitionResponse

updateRequisition Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing requisition instance, and sends a
correlated message only if error occurred.
 Please Note: Update requests replace all data fields in the requisitionBean (i.e. data is
not appended or upserted). Send all elements back or the field values will be returned
NULL.

Input: updateRequisitionRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
in1 requisitionBean[] * id *
status *

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 209
city
description
duration
jobCategory
jobCode
location *
numOpen
openedDate
payRange
state
title *
filledDate

Output: updateRequisitionResponse

Data Field Name Data Field Type Required Acceptable Values

updateRequisitionReturn

updateRequisition Test Case:

Input: updateRequisitionRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateRequisition>
<in0>webapi-3736131371583618769</in0>
<in1>
<flexValues>

<item>
</item>
</flexValues>
<id>16</id>
<status>Filled</status>
<city>San Francisco</city>
<description>The Human Resources Generalist originates and leads Human
Resources practices and objectives that will provide an employee-oriented, high
performance culture that emphasizes empowerment, quality, productivity and standards,
goal attainment, and the recruitment and ongoing development of a superior workforce.
The Human Resources Generalist coordinates implementation of services, policies, and
programs through Human Resources staff; reports to the Human Resources Director, and
assists and advises company managers about Human Resources issues.</description>
<duration>Full time</duration>
<jobCategory>Professional</jobCategory>
<jobCode>Level 1</jobCode>
<location>Headquarters</location>
<numOpen>2</numOpen>
<openedDate>2009-06-30T23:01:26.493Z</openedDate>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 210
<payRange>50000 - 75000</payRange>
<state>US-CA</state>
<title>HR Generalist</title>
<filledDate>2009-09-31T23:01:26.493Z</filledDate>
</in1>
</urn:updateRequisition>
</soapenv:Body>
</soapenv:Envelope>

Output: updateRequisitionResponse

Resume API Calls

Resumes are all of the primary CVs associated with Candidates in Taleo Business Edition.

getBinaryResume Element:
Operation type: Request-response.
 The endpoint receives a message to get the primary resume binary attachment
associated with a candidate, and sends back the resume binary resume data.

Input: getBinaryResumeRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of candidate

Output: getBinaryResumeResponse

Data Field Name Data Field Type Required Acceptable Values

getBinaryReturn base64Binary []

getBinaryResume Test Case:

Input: getBinaryResumeRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 211
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getBinaryResume>
<in0>webapi1673199911353581754</in0>
<in1>48</in1>
</urn:getBinaryResume>
</soapenv:Body>
</soapenv:Envelope>

Output: getBinaryResumeResponse

parseResume Element:
Operation type: Request-response.
 The endpoint receives a message resume binary attachment, and sends back a passed
output of resume data (using third-party provider ResumeMirror)

Input: parseResumeRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 ByteArr Yes base64Binary []

Output: parseResumeResponse

Data Field Name Data Field Type Required Acceptable Values

ResumeMirror HR-XML
parseResumeReturn
ParseResume Response

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 212
parseResume Test Case:

Input: parseResumeRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:parseResume>
<in0>webapi-3736131371583618769</in0>
<in1>
<array>0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAA==</array>
</in1>
</urn:parseResume>
</soapenv:Body>
</soapenv:Envelope>

Output: parseResumeResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 213
</PostalAddress>
</ContactMethod>
</ContactInfo>
</Resume>]]></parseResumeReturn>
</parseResumeResponse>
</soapenv:Body>
</soapenv:Envelope>

parseResumeIntoCandidate Element:
Operation type: Request-response.
 The endpoint receives a message resume binary attachment and creates a new
candidate with contact information parsed with the original resume appended to the
candidate record, and sends back:
o Candidate ID (either newly created or existing if duplicate)
o Duplicate Value where 0 equals none existing and 1 equals duplicate exists

Input: parseResumeIntoCandidateRequest

Data Field Data Field Required

Acceptable Values
Name Type
in0 String Yes Session ID received at Login
in1 ByteArr Yes base64Binary []
referredBy String No Name of referral source
Name of the resume file including extension.
The following MIME types are acceptable:
Text = text/plain
html = text/html
RTF = text/richtext
filename String Yes
Word = application/msword
DocX =
application/vnd.openxmlformats-
officedocument.wordprocessingml.document
PDF = application/pdf

Output: parseResumeIntoCandidateResponse

Required Acceptable
Data Field Name Data Field Type
Values
candidateId
parseResumeIntoCandidateReturn dup (duplicate
value)

parseResumeIntoCandidate Test Case:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 214
Input: parseResumeIntoCandidateRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:parseResumeIntoCandidate>
<in0>webapi-3736131371583618769</in0>
<in1>
<array>0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAA==</array>
</in1>
<referredBy>bdonlan</referredBy>
<fileName>resume.doc</fileName>
</urn:parseResumeIntoCandidate>
</soapenv:Body>
</soapenv:Envelope>

Output: parseResumeIntoCandidateResponse

setBinaryResume Element:
Operation type: Request-response.
 The endpoint receives a message to append a resume attachment to a candidate ID, and
sends a correlated message only if error occurred.

Input: setBinaryResumeRequest

Data Field Required

Data Field Type Acceptable Values
Name
in0 String Yes Session ID received at Login
in1 Candidate ID Yes ID of Candidate
Filename of binary file with defined file
in2 String Yes
extension. The following MIME types are

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 215
acceptable:
Text = text/plain
html = text/html
RTF = text/richtext
Word = application/msword
DocX =
application/vnd.openxmlformats-
officedocument.wordprocessingml.document
PDF = application/pdf
in3 ByteArr Yes base64Binary []

Output: setBinaryResumeResponse

Data Field Name Data Field Type Required Acceptable Values

setBinaryResumeReturn

setBinaryResume Test Case:

Input: setBinaryResumeRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:setBinaryResume>
<in0>webapi-3736131371583618769</in0>
<in1>44</in1>
<in2>solidResume.doc</in2>
<in3>
<array>0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAA==</array>
</in3>
</urn:setBinaryResume>
</soapenv:Body>
</soapenv:Envelope>

Output: setBinaryResumeResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 216
Rolling Entity Calls
Dynamic forms allowing collection of:

 Education History
 Licenses & Certifications
 Previous Residences
 References
 Work History

rollingEntityBean Definition:

Data Field Name Data Field Type Required Acceptable Values

Contact’s unique server side
ID. Can be obtained by
ID Long Read Only searching the accounts’
database or by creating a
new account.
sessionID String Yes Session ID received at Login
Rolling Entity Status from
status Long Yes
pick list
WORK_HISTORY
RESIDENCE_HISTORY
rollingEntityType String Yes EDUCATION
REFERENCES
CERTIFICATES_LICENCES
Yes CAND
entityType String
EMPL
entityID Long Yes ID of CAND or EMPL
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
attributes AttributeBean No Array of rolling entity
attribute (standard) field
values
flexValues FlexFieldBean[] No Array of flexible (custom)
field values

attributeBean Definition:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 217
flexFieldBean Definition:

deleteRollingEntity Element:
Operation type: Request-response.
 The endpoint receives a message to delete a specific rolling entity instance based on ID,
and sends a correlated message only if error occured.

Input: deleteRollingEntityRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received at
sessionID String Yes
Login
rollingEntityId String Yes ID of rolling entity

Output: deleteRollingEntityResponse

Data Field Name Data Field Type Required Acceptable Values

deleteRollingEntityReturn

deleteRollingEntity Test Case:

Input: deleteRollingEntityRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteRollingEntity>
<sessionId>webapi-3736131371583618769</sessionId>
<rollingEntityId>11</rollingEntityId>
</urn:deleteRollingEntity>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 218
Output: deleteRollingEntityResponse

getRollingEntities Element:
Operation type: Request-response.
 The endpoint receives a message to get a specific rolling entity for a candidate or
employee, and sends a correlated message of rolling entity information.
 There is no ‘ALL’ function; a call is configured for the pulling of each rolling entity type:
o WORK_HISTORY
o RESIDENCE_HISTORY
o EDUCATION
o REFERENCES
o CERTIFICATES_LICENCES

Input: getRollingEntitiesRequest

Data Field Name Data Field Type Required Acceptable Values

sessionID String Yes Session ID received at Login
WORK_HISTORY
RESIDENCE_HISTORY
rollingEntityType String Yes EDUCATION
REFERENCES
CERTIFICATES_LICENCES
entityType String Yes CAND
entityID Long Yes Candidate ID

Output: getRollingEntitiesResponse

Data Field Name Data Field Type Required Acceptable Values

getRollingEntitiesReturn rollingEntitiesBean []

getRollingEntities Test Case:

Input: getRollingEntitiesRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 219
<soapenv:Body>
<urn:getRollingEntities>
<sessionId>webapi-6894240122814704138</sessionId>
<rollingEntityType>WORK_HISTORY</rollingEntityType>
<entityType>CAND</entityType>
<entityId>45</entityId>
</urn:getRollingEntities>
</soapenv:Body>
</soapenv:Envelope>

Output: getRollingEntitiesResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getRollingEntitiesResponse xmlns="urn:TBEWebAPI">
<getRollingEntitiesReturn xmlns="">
<array>
<item>
<creationDate>2009-08-11T15:43:45.273Z</creationDate>
<flexValues>
<item>
<fieldName>Starting Rate Of Pay</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>56000</valueStr>
</item>
</flexValues>
<id>13</id>
<lastUpdated>2009-08-15T00:13:33.283Z</lastUpdated>
<status xsi:nil="true"/>
<attributes>
<item>
<fieldName>workHistJobTitle</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>Lovely Manager</valueStr>
</item>
<item>
<fieldName>workHistFrom</fieldName>
<valueBool xsi:nil="true"/>
<valueDate>2007-02-01T00:00:00.000Z</valueDate>
<valueDbl xsi:nil="true"/>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 220
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>workHistDesc</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>Was a lovely manager</valueStr>
</item>
<item>
<fieldName>workHistCoName</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>McKesson</valueStr>
</item>
<item>
<fieldName>workHistStreet</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>12 – Richmond Street</valueStr>
</item>
<item>
<fieldName>workHistCityState</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>BC</valueStr>
</item>
<item>
<fieldName>workHistPhone</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>858-304-3434</valueStr>
</item>
<item>
<fieldName>workHistSupervisor</fieldName>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 221
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>595-394-4094</valueStr>
</item>
<item>
<fieldName>workHistSuperTitle</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>Manager</valueStr>
</item>
<item>
<fieldName>workHistOkContact</fieldName>
<valueBool>true</valueBool>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
<item>
<fieldName>workHistPay</fieldName>
<valueBool xsi:nil="true"/>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr>65000</valueStr>
</item>
<item>
<fieldName>toPresent</fieldName>
<valueBool>true</valueBool>
<valueDate xsi:nil="true"/>
<valueDbl xsi:nil="true"/>
<valueInt xsi:nil="true"/>
<valueLong xsi:nil="true"/>
<valueStr xsi:nil="true"/>
</item>
</attributes>
<entityType>CAND</entityType>
<entityId>45</entityId>
<subType>WORK_HISTORY</subType>
</item>
</array>
</getRollingEntitiesReturn>
</getRollingEntitiesResponse>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 222
</soapenv:Body>
</soapenv:Envelope>

upsertRollingEntity Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing rolling entity instance, and sends
a correlated message only if error occurred.
 Please Note: Upsert is used to both create or update data within a specific rolling entity.
Using the ID attribute updates or replaces existing rolling entity instance, whereas not
using an entityId will create a new rolling entity for the entity ID.

Input: upsertRollingEntityRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
sessionID String Yes
at Login
flexValues []
attributes []
id *
rollingEntityBean rollingEntityBean [] * status *
entityId
entityType
subType

Output: upsertRollingEntityResponse

Data Field Name Data Field Type Required Acceptable Values

upsertRollingEntityReturn

upsertRollingEntity Test Case:

Input: upsertRollingEntityRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 223
<item>
<fieldName>workHistJobTitle</fieldName>
<valueStr>Senior Recruiter</valueStr>
</item>
<item>
<fieldName>workHistOkContact</fieldName>
<valueBool>False</valueBool>
</item>
</attributes>
<entityType>CAND</entityType>
<entityId>44</entityId>
<subType>WORK_HISTORY</subType>
</rollingEntityBean>
</urn:upsertRollingEntity>
</soapenv:Body>
</soapenv:Envelope>

Output: upsertRollingEntityResponse

Search API Calls

Search API calls are the results of querying of supported entities in Taleo Business Edition. This
object is used to encapsulate the ID of the entity found in Taleo during a search. By using this ID,
a Web API client can get detailed information or perform other operations on that entity. Results
are provided in an array where the ID is provided of the result and a score of relevance.

The following entities are supported for search:

 Account
 Candidate
 Contact
 Employee
 Requisition
 User

Use the search(entityName) call for the appropriate entity you are searching.

searchResultBean Definition:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 224
Data Field Name Data Field Type Required Acceptable Values
id long Read Only ID of entity found in the database
Relevance is a value between 0 and
100, which reflects how well this
relevance Double Read Only
candidate or requisition matches the
search criteria

System API Calls

All system level properties for a Taleo Business Edition client, including modules uses, system
setting values, and system URLs.

getEnabledServices Element:
Operation type: Request-response.
 The endpoint receives a message to get the all the application modules the company
code has turned on, and sends back all system modules configured where:
o 'perform' = Taleo Business Edition Perform
o 'onBoarding' = Taleo Business Edition onBoarding
o 'recruit' = Taleo Business Edition Recruit
o 'backup' = Taleo Business Edition on-Demand BackUp Service
o 'offcp' = Taleo Business Edition OFFCP Compliance Package
o 'tsc' = Taleo Schedule Center for Recruit
o 'tvr'= Taleo Voice Response for Recruit
o 'generic'= Taleo Business Edition Generic Package for Recruit
o 'staffing' = Taleo Business Edition Staffing Package for Recruit
o 'pureDiscovery' = Pure Discovery Advanced Sourcing for Recruit

Input: getEnabledServicesRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login

Output: getEnabledServicesResponse

Data Field Name Data Field Type Required Acceptable Values

String of system
getEnabledServicesReturn
modules

getEnabledServices Test Case:

Input: getEnabledServicesRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 225
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getEnabledServices>
<in0>webapi-8948403736913319968</in0>
</urn:getEnabledServices>
</soapenv:Body>
</soapenv:Envelope>

Output: getEnabledServicesResponse

getSystemProps Element:

Operation type: Request-response.

 The endpoint receives a message to get the system props of a company code using valid
session variable, and sends back all system properties configured.
 System-level properties return as string-string map:

Property Name Property Value

HiredStatuses Comma-separated ids of statuses for hired candidates
OpenedStatuses Comma-separated ids of statuses for opened requisitionss
MyViewStatuses Comma-separated ids of statuses for candidates shown on “My View”
page
PipelineStatuses Comma-separated ids of statuses for candidates shown on “Pipeline”
page

Input: getSystemPropsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 226
Output: getSystemPropsResponse

Data Field Name Data Field Type Required Acceptable Values

Array of System
getSystemPropsReturn
Property Values

getSystemProps Test Case:

Input: getSystemPropsRequest

Output: getSystemPropsResponse (truncated)

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 227
<value xsi:type="xsd:string">30</value>
</item>
<item>
<key xsi:type="xsd:string">msg.dbcp.maxActive</key>
<value xsi:type="xsd:string">20</value>
</item>
<item>
<key xsi:type="xsd:string">msg.dbcp.numTestsPerEvictionRun</key>
<value xsi:type="xsd:string">3</value>
</item>
<item>
<key xsi:type="xsd:string">MaxTransactionTime</key>
<value xsi:type="xsd:string">2</value>
</item>
<item>
<key xsi:type="xsd:string">msg.c3p0.acquireRetryDelay</key>
<value xsi:type="xsd:string">1000</value>
</item>
<item>
<key xsi:type="xsd:string">formDisplayManager.cacheSizeLimit</key>
<value xsi:type="xsd:string">50</value>
</item>
<item>
<key xsi:type="xsd:string">c3p0.initialPoolSize</key>
<value xsi:type="xsd:string">5</value>
</item>
<item>
<key xsi:type="xsd:string">formDisplayManager.commonFormExpiryTime</key>
<value xsi:type="xsd:string">1200</value>
</item>
<item>
<key xsi:type="xsd:string">msg.c3p0.maxConnectionAge</key>
<value xsi:type="xsd:string">0</value>
</item>
<item>
<key xsi:type="xsd:string">dbcp.testWhileIdle</key>
<value xsi:type="xsd:string">true</value>
</item>
<item>
<key xsi:type="xsd:string">ReqCreateTemplate</key>
<value xsi:type="xsd:string">-1</value>
</item>
<item>
<key xsi:type="xsd:string">ReviewApproverApprovesTemplate</key>
<value xsi:type="xsd:string">40</value>
</item>
<item>
<key xsi:type="xsd:string">msg.c3p0.async</key>
<value xsi:type="xsd:string">true</value>
</item>
<item>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 228
<key xsi:type="xsd:string">OfferApprovedTemplate</key>
<value xsi:type="xsd:string">-1</value>
</item>
<item>
<key xsi:type="xsd:string">sccDocSetClient.segment</key>
<value xsi:type="xsd:string">NA01A</value>
</item>
</getSystemPropsReturn>
</getSystemPropsResponse>
</soapenv:Body>
</soapenv:Envelope>

Task API Calls

Tasks are workflow tasks stored within a specific entity of Taleo Business Edition. There is a one-
to-many relationship with tasks to entities. Entities include accounts (ACCT), candidates (CAND),
contacts (CTCT), employees (EMPL), requisitions (REQU) and users (WORK).

taskBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
id long Account’s unique server side ID. Can be
Read Only obtained by searching the accounts’
database or by creating a new account.
status String Yes Account’s Status from pick list
creator String Yes Creator’s login name
entityType String No Type of related entity:
ACCT = accounts
CAND = candidates
CTCT = contacts
EMPL = employees
REQU = requisitions
WORK = users
entityId long No ID of associated entity
subject String Yes Subject of event
priority String Priority (from pick list):
Low
Yes
Normal
High
dueDate Date No Task’s due date
description String No Description
participants ParticipantBean[] Yes Array of events’ participants
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
flexValues FlexFieldBean[] No Array of flexible (custom) field values

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 229
participantBean Definition:

flexFieldBean Definition:

Data Field
Data Field Type Required Acceptable Values
Name
FieldName String Yes Field name
Value of Text, Email, URL, Pick list, or
StringValue String No Text Area field. For Multiple Pick list use
‘|’ to separate values.
IntValue int No Value of Integer field
DoubleValue double No Value of Decimal or Currency field
BooleanValue boolean No Value of Check Box field
DateValue Date No Value of Date field

createTask Element:
Operation type: Request-response.
 The endpoint receives a message to create a task, and sends a correlated message of
task ID.

Input: createTaskRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
taskBean[]
in1 * status *
participantBean []
creator *

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 230
description
dueDate
entityId
entityType
priority *
subject *

assignedTo []
endDate
eventId *
eventType *
personId *
personType *
startDate *

Output: createTaskResponse

Data Field Name Data Field Type Required Acceptable Values

createTaskReturn Long Yes Provided Task ID

createTask Test Case:

Input: createTaskRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createTask>
<in0>webapi411835895647962205</in0>
<in1>
<flexValues>

</flexValues>
<status>Not Started</status>
<assignedTo>

<item>
<endDate>2009-06-30T23:01:26.493Z</endDate>
<eventId>2</eventId>
<eventType>TASK</eventType>
<personId>7</personId>
<personType>WORK</personType>
<startDate>2009-06-30T23:01:26.493Z</startDate>
</item>
</assignedTo>
<creator>skarim</creator>
<description>Complete Interview</description>
<dueDate>2009-06-30T23:01:26.493Z</dueDate>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 231
<entityId>48</entityId>
<entityType>CAND</entityType>
<priority>High</priority>
<subject>Interview Schedule</subject>
</in1>
</urn:createTask>
</soapenv:Body>
</soapenv:Envelope>

Output: createTaskResponse

deleteTask Element:
Operation type: Request-response.
 The endpoint receives a message to delete a task instance, and sends a correlated
message only if error occurred.

Input: deleteTaskRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Task ID Yes ID of Task

Output: deleteTaskResponse

Data Field Name Data Field Type Required Acceptable Values

deleteTaskReturn

deleteTask Test Case:

Input: deleteTaskRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 232
<urn:deleteTask>
<in0>webapi411835895647962205</in0>
<in1>4</in1>
</urn:deleteTask>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteTaskResponse

getTaskByEntity Element:
Operation type: Request-response.
 The endpoint receives a message to get task(s) associated with any Taleo Business
Edition entity that supports storing/creation of task events, and sends back task IDs
associated with the entity ID.

Input: getTaskByEntityRequest

Data Field Name Data Field Type Required Acceptable Values

Output: getTaskByEntityResponse

Data Field Name Data Field Type Required Acceptable Values

getTaskByEntityReturn array of task IDs

getTaskByEntity Test Case:

Input: getTaskByEntityRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 233
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getTaskByEntity>
<in0>webapi411835895647962205</in0>
<in1>CAND</in1>
<in2>48</in2>
</urn:getTaskByEntity>
</soapenv:Body>
</soapenv:Envelope>

Output: getTaskByEntityResponse

getTaskById Element:
Operation type: Request-response.
 The endpoint receives a message to get task details by task ID, and sends a correlated
message of task information.

Input: getTaskByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Task ID Yes ID of Task Instance

Output: getTaskByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getTaskByIdReturn taskBean []

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 234
getTaskById Test Case:

Input: getTaskByIdRequest

Output: getTaskByIdResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 235
getTaskByUser Element:
Operation type: Request-response.
 The endpoint receives a message to get all tasks associated with a user, and sends a
correlated message of task IDs

Input: getTaskByUserRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes User ID
startDate interval for
in2 Date Yes
due items
endDate interval for
in3 Date Yes
due items

Output: getTaskByUserResponse

Data Field Name Data Field Type Required Acceptable Values

getTaskByUserReturn array of task IDs

getTaskByUser Test Case:

Input: getTaskByUserRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getTaskByUser>
<in0>webapi411835895647962205</in0>
<in1>7</in1>
<in2>2009-06-30T23:01:26.493Z</in2>
<in3>2009-08-30T23:01:26.493Z</in3>
</urn:getTaskByUser>
</soapenv:Body>
</soapenv:Envelope>

Output: getTaskByUserResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 236
<array>
<item>1</item>
<item>2</item>
<item>3</item>
</array>
</getTaskByUserReturn>
</getTaskByUserResponse>
</soapenv:Body>
</soapenv:Envelope>

updateTask Element:
Operation type: Request-response.
 The endpoint receives a message to update an existing task event, and sends a
correlated message only if error occurred.
 Please Note: Update requests replace all data fields in the taskBean (i.e. data is not
appended or upserted). Send all elements back or the field values will be returned NULL.

Input: updateTaskRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
id *
status *
creator *
description
dueDate
entityId
entityType
priority *
taskBean[]
in1 * subject *
participantBean []

assignedTo []
endDate
eventId *
eventType *
personId *
personType *
startDate *

Output: updateTaskResponse

Data Field Name Data Field Type Required Acceptable Values

updateTaskReturn

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 237
updateTask Test Case:

Input: updateTaskRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:updateTask>
<in0>webapi411835895647962205</in0>
<in1>
<flexValues>

</flexValues>
<id>2</id>
<status>Completed</status>
<assignedTo>

<item>
<eventId>1</eventId>
<eventType>TASK</eventType>
<personId>7</personId>
<personType>WORK</personType>
<startDate>2009-06-30T23:01:26.493Z</startDate>
</item>
</assignedTo>
<creator>skarim</creator>
<description>Complete Interview</description>
<dueDate>2009-06-30T23:01:26.493Z</dueDate>
<entityId>48</entityId>
<entityType>CAND</entityType>
<priority>High</priority>
<subject>Interview Schedule</subject>
</in1>
</urn:updateTask>
</soapenv:Body>
</soapenv:Envelope>

Output: updateTaskResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 238
User API Calls
Users are all the people with access to your Taleo Business Edition system including hiring
managers, recruiters, interviewers, staffing agencies, etc.

userBean Definition:

** Picklist values within userBean may be customized/configured. Viewing source within the edit
new user screen within Taleo Business Edition outlines picklist values for a client.

Data Field
Data Field Type Required Acceptable Values
Name
User’s unique server side ID. Can be
id long Read Only obtained by searching the user database
or by creating a new user.
User’s Status Value as derived from
picklist. View Source on add new user
status String Yes
page within the application to find values
of status Names.
firstName String No First name
middleInitial String No Middle name
lastName String Yes Last name.
title String No User’s title
Name of location (from pick list) assigned
to this user. View Source on add new
location String No
user page within the application to find
values of location IDs.
manager String No Login name of user’s manager
phone String No Phone number
cellPhone String No Cell phone number
fax String No Fax phone number
email String Yes Email address
User’s role:
'A' = Administrator
'M' = Hiring Manager
role String Yes 'R' = Recruiter
'E’ = Employee
'G' = Agency
‘-‘ = no access
loginName String Yes User’s login name
Local User Time zone ID as derived from
piclklist:
timeZoneId String No
'MIT' = GMT-11:00
'Pacific/Apia' = GMT-11:00

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 239
'Pacific/Honolulu' = GMT-10:00
'America/Anchorage' = GMT-08:00
'America/Los_Angeles' = GMT-07:00
'America/Denver' = GMT-06:00
'America/Phoenix' = GMT-07:00
'America/Tegucigalpa' = GMT-06:00
'America/Winnipeg' = GMT-05:00
'America/Mexico_City' = GMT-05:00
'America/Chicago' = GMT-05:00
'America/Costa_Rica' = GMT-06:00
'America/Indianapolis' = GMT-04:00
'America/New_York' = GMT-04:00
'America/Bogota' = GMT-05:00
'America/Montreal' = GMT-04:00
'America/Santiago' = GMT-04:00
'America/Caracas' = GMT-04:30
'America/Thule' = GMT-03:00
'America/St_Johns' = GMT-02:30
'America/Buenos_Aires' = GMT-03:00
'America/Sao_Paulo' = GMT-03:00
'Atlantic/South_Georgia' = GMT-02:00
'Atlantic/Cape_Verde' = GMT-01:00
'Atlantic/Azores' = GMT-00:00
'Europe/Dublin' = GMT+01:00
'Africa/Casablanca' = GMT-00:00
'Europe/Amsterdam' = GMT+02:00
'Europe/Belgrade' = GMT+02:00
'Europe/Brussels' = GMT+02:00
'Europe/Warsaw' = GMT+02:00
'Africa/Lagos' = GMT+01:00
'Europe/Athens' = GMT+03:00
'Europe/Bucharest' = GMT+03:00
'Africa/Cairo' = GMT+03:00
'Africa/Harare' = GMT+02:00
'Europe/Helsinki' = GMT+03:00
'Asia/Jerusalem' = GMT+03:00
'Asia/Baghdad' = GMT+03:00
'Asia/Kuwait' = GMT+03:00
'Europe/Moscow' = GMT+04:00
'Africa/Nairobi' = GMT+03:00
'Asia/Tehran' = GMT+04:30
'Asia/Dubai' = GMT+04:00
'Asia/Baku' = GMT+05:00
'Asia/Kabul' = GMT+04:30
'Asia/Yekaterinburg' = GMT+06:00
'Asia/Karachi' = GMT+06:00
'Asia/Calcutta' = GMT+05:30
'Asia/Katmandu' = GMT+05:45
'Asia/Almaty' = GMT+06:00
'Asia/Dhaka' = GMT+07:00
'Asia/Colombo' = GMT+05:30

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 240
'Asia/Rangoon' = GMT+06:30
'Asia/Bangkok' = GMT+07:00
'Asia/Krasnoyarsk' = GMT+08:00
'Asia/Hong_Kong' = GMT+08:00
'Asia/Irkutsk' = GMT+09:00
'Asia/Kuala_Lumpur' = GMT+08:00
'Australia/Perth' = GMT+08:00
'Asia/Taipei' = GMT+08:00
'Asia/Tokyo' = GMT+09:00
'Asia/Seoul' = GMT+09:00
'Asia/Yakutsk' = GMT+10:00
'Australia/Adelaide' = GMT+09:30
'Australia/Darwin' = GMT+09:30
'Australia/Brisbane' = GMT+10:00
'Australia/Sydney' = GMT+10:00
'Pacific/Guam' = GMT+10:00
'Australia/Hobart' = GMT+10:00
'Asia/Vladivostok' = GMT+11:00
'Asia/Magadan' = GMT+12:00
'Pacific/Auckland' = GMT+12:00
'Pacific/Fiji' = GMT+12:00
'Pacific/Tongatapu' = GMT+13:00
Locale code as derived from picklist:
'enAU' = English - Australia
'enAT' = English - Austria
'enBE' = English - Belgium
'enCA' = English - Canada
'enFI' = English - Finland
'enFR' = English - France
'enGR' = English - Greece
'enIE' = English - Ireland
'enIT' = English - Italy
localeCode String No
'enLU' = English - Luxembourg
'enNL' = English - Netherlands
'enNZ' = English - New Zealand
'enPT' = English - Portugal
'enGB' = English - United Kingdom
'enUS' selected = English - United States
'frCA' = French - Canada
'deDE' = German - Germany
'esMX' = Spanish - Mexico
'esES' = Spanish - Spain
lastLogin Date Read Only Last Login
creationDate Date Read Only Creation date
lastUpdated Date Read Only Last updated date
flexValues FlexFieldBean[] No Array of flexible (custom) field values

flexFieldBean Definition:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 241
Data Field
Data Field Type Required Acceptable Values
Name
fieldName String Yes Field name
Value of Text, Email, URL, Pick list, or
stringValue String No Text Area field. For Multiple Pick list use
‘|’ to separate values.
intValue int No Value of Integer field
doubleValue double No Value of Decimal or Currency field
booleanValue Boolean No Value of Check Box field
dateValue Date No Value of Date field

createUser Element:
Operation type: Request-response.
 The endpoint receives a message to create a user, and sends a correlated message of
user ID.

Input:createUserRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status *
cellPhone
email *
fax
firstName
lastName *
localeCode
in1 userBean[] *
location
loginName *
manager
middleInitial
phone
role *
timeZoneId
title

Output: createUserResponse

Data Field Name Data Field Type Required Acceptable Values

createUserReturn Long Yes Provided User ID

createUser Test Case:

Input:createUserRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 242
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createUser>
<in0>webapi-7677111958344909818</in0>
<in1>
<flexValues>

<item></item>
</flexValues>
<status>Employee</status>
<cellPhone>638-234-5364</cellPhone>
<email>[email protected]</email>
<fax>384-239-2345</fax>
<firstName>James</firstName>
<lastName>Jason</lastName>
<localeCode>Asia/Taipei</localeCode>
<location>Vancouver</location>
<loginName>JamesJason</loginName>
<manager>skarim</manager>
<middleInitial>J</middleInitial>
<phone>897-238-24854</phone>
<role>A</role>
<timeZoneId>Pacific/Apia</timeZoneId>
<title>Manager</title>
</in1>
</urn:createUser>
</soapenv:Body>
</soapenv:Envelope>

Output:createUserResponse

createUserWithPermissions Element:
Operation type: Request-response.
 The endpoint receives a message to create a user with permission attributes, and sends
a correlated message of user ID.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 243
 User permissions fall within the attributesBean where ‘approver’ elements can be sent.
These are defined based on:
o Permission to approve requisitions for Taleo RECRUIT = ‘approver’
o Permission to approve requisition hire offer for Taleo RECRUIT =
‘offerAppr’
o Permission to approve performance reviews in Taleo PERFORM =
‘reviewApprover ‘
o Permission to be an review manager approver in Taleo PERFORM =
‘reviewManager’
o Assignment to specfici department by name/string in any Taleo module =
‘department’
 User permissions can support department attribute as flex fields (FlexFieldBean) with
'department' as a key. The value can be either the department id (set on the bean as
valueLong) or department name (valueString). ID takes precedence if both supplied.

Input: createUserWithPermissionsRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received at
sessionID String Yes
Login
userBean

status *
cellPhone
email *
fax
firstName
lastName *
localeCode
location
loginName *
manager
middleInitial
userBean[] phone
userBeanToCreate *
attributesBean [] role *
timeZoneId
title

flexValues []
department(String)
departmentId (Long)

attributes
approver (Boolean)
offerAppr (Boolean)
reviewManager(Boolean)
reviewApprover(Boolean)

Output: createUserWithPermissions Response

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 244
Data Field Name Data Field Type Required Acceptable Values
createUserWithPermissions
Long Yes Provided User ID
Return

createUserWithPermissions Test Case:

Input: createUserWithPermissions Request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:createUserWithPermissions>
<sessionId>webapi-7677111958344909818</sessionId>
<userBeanToCreate>
<flexValues>

<item>
<fieldName>department</fieldName>
<valueStr>Accounting</valueStr>
</item>
<item>
<fieldName>department</fieldName>
<valueStr>Customer Service</valueStr>
</item>
</flexValues>
<status>Employee</status>
<cellPhone>638-234-5364</cellPhone>
<email>[email protected]</email>
<fax>384-239-2345</fax>
<firstName>James</firstName>
<lastName>Jason</lastName>
<localeCode>Asia/Taipei</localeCode>
<location>Vancouver</location>
<loginName>JJ1234</loginName>
<manager>skarim</manager>
<middleInitial>J</middleInitial>
<phone>897-238-24854</phone>
<role>A</role>
<timeZoneId>Pacific/Apia</timeZoneId>
<title>Manager</title>
</userBeanToCreate>
<additionalEntities>

<item>
<key>offerAppr</key>
<value>True</value>
</item>
<item>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 245
<key>approver</key>
<value>True</value>
</item>
<item>
<key>reviewManager</key>
<value>True</value>
</item>
<item>
<key>reviewApprover</key>
<value>True</value>
</item>
</additionalEntities>
</urn:createUserWithPermissions>
</soapenv:Body>
</soapenv:Envelope>

Output: createUserWithPermissionsResponse

deleteUser Element:
Operation type: Request-response.
 The endpoint receives a message to delete a user, and sends a correlated message only
if error occurred.

Input: deleteUserRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 User ID Yes ID of User

Output: deleteUserResponse

Data Field Name Data Field Type Required Acceptable Values

deleteUserReturn

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 246
deleteUser Test Case:

Input: deleteUserRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:deleteUser>
<in0>webapi-7677111958344909818</in0>
<in1>10</in1>
</urn:deleteUser>
</soapenv:Body>
</soapenv:Envelope>

Output: deleteUserResponse

getUserById Element:
Operation type: Request-response.
 The endpoint receives a message to get an User details, and sends a correlated
message of User information.

Input: getUserByIdRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 User ID Yes ID of User

Output: getUserByIdResponse

Data Field Name Data Field Type Required Acceptable Values

getUserByIdReturn UserBean

getUserById Test Case:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 247
Input: getUserByIdRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getUserById>
<in0>webapi-7677111958344909818</in0>
<in1>18</in1>
</urn:getUserById>
</soapenv:Body>
</soapenv:Envelope>

Output: getUserByIdResponse

getUserHistory Element:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 248
Operation type: Request-response.
 The endpoint receives a message to get a Users system history within Taleo Business
Edition, and sends a correlated message of User history information.
 This object is used to fetch a history log entry which reflects a past event or action related
to Users. History records can only be created by the server, they cannot be modified or
deleted. History log includes server side ID, test describing history record, complete text
of email message (for email events) and creation date.

Input: getUserHistoryRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of User

Output: getUserHistoryResponse

Data Field Name Data Field Type Required Acceptable Values

getUserHistoryReturn historyBean

getUserHistory Test Case:

Input: getUserHistoryRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getUserHistory>
<in0>webapi-7677111958344909818</in0>
<in1>18</in1>
</urn:getUserHistory>
</soapenv:Body>
</soapenv:Envelope>

Output: getUserHistoryResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 249
<text>User created</text>
<userName>skarim</userName>
</item>
<item>
<creationDate>2009-09-16T00:19:11.543Z</creationDate>
<emailText xsi:nil="true"/>
<id>655</id>
<text>Password reset</text>
<userName>skarim</userName>
</item>
</array>
</getUserHistoryReturn>
</getUserHistoryResponse>
</soapenv:Body>
</soapenv:Envelope>

searchUser Element:
Operation type: Request-response.
 The endpoint receives a message to query all Users based on defined key (field name)
and value (data looking for), and sends a correlated message of User ID and associated
search relevance.
 Relevance is a value between 0 and 100, which reflects how well the account matches
the search criteria
 Map of search parameters always contains:
o key: name of field to search as a string
o value: search parameter as string.
 Format of search value may differ depending on data type of the search field:
 For text, text area, email, URL fields: simple text to be found (case-insensitive) in this
field. Example:
o key=”city”, value=”Francisco” will search for all candidates with ”Francisco” in
“city” field.
 For integer, double, currency: interval between two numbers separated by ‘|’ character.
Either left (from) or right (to) side can be omitted. Example:
o key=”rank”, value=”100|” will search for all candidates with rank value no less
than 100.
o key=”rank”, value=”|200” will search for all candidates with rank value no more
than 200.
o key=”rank”, value=”100|200” will search for all candidates with rank value
between 100 and 200 (inclusive).
 For date fields: interval between two dates in ISO yyyy-MM-dd format, separated by ‘|’
character. Either left (from) or right (to) side can be omitted. Example:
o key=”startDate”, value=”2004-06-01|” will search for all candidates with start date
on or after June 1st 2004.
o key=”startDate”, value=”|2004-08-01” will search for all candidates with start date
on or before August 1st 2004.
o key=”startDate”, value=”2004-06-01|2004-08-01” will search for all candidates
with start date between June 1st 2004 and August 1st 2004 (inclusive).

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 250
 For date interval fields: number of days from today to the past. Example:
o key=” addedWithin”, value=”7” will search for all candidates added to the system
within the last week.
 For single pick list: code value or name of selected item. Example:
o key=”country”, value=”US” will search for all candidates with country field equals
to “United States”.
o key=”status”, value=”available” will search for all candidates in “Available” status.
 For multiple pick list: code values or names of selected items, separated by ‘|’ character.
Example:
o key=”customMultiple”, value=”A1|B2|X5” will search for all candidates with
customMultiple field containing one or more of values: A1, B2, X5.
 For check box fields: “true” if check box must be checked, “false” is unchecked. Example:
o key=” flagged”, value=”true” will search for all candidates “flagged” for the user
currently logged in.
 Search keys names and types can be found in Administration>Customize>User Fields.
They may include both system fields (listed below for convenience) and custom fields.
For custom fields External name is used as key name.

System Search Keys:

Data Field Name Parameter Type Description

Keyword(s) in user’s profile. Identical
keyword String
syntax as used in Taleo browser interface.
firstName String User’s first name
lastName String User’s last name
title String User’s title
location Pick list Location assigned to user
manager String Login name of manager assigned to user
User’s role: 'A'-admin, 'M'-hiring manager,
role String
'R'-recruiter, 'E'-employee, 'G'-agency
addedWithin Integer Added within N days
updatedWithin Integer Updated within N days

Input: searchUserRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
key
in1 Item… Yes
value

Output: searchUserResponse

Data Field Name Data Field Type Required Acceptable Values

searchUserReturn searchResultBean []

searchUser Test Case:

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 251
Input: searchUserRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:searchUser>
<in0>webapi-7677111958344909818</in0>
<in1>

<item>
<key>Role</key>
<value>Administrator</value>
</item>
</in1>
</urn:searchUser>
</soapenv:Body>
</soapenv:Envelope>

Output: searchUserResponse

updateUser Element:

Operation type: Request-response.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 252
 The endpoint receives a message to update an existing user, and sends a correlated
message only if error occurred.
 Can assign user to department via flexFields where each flexFields array appends an
additional department value. The value can be either the department id (set on the bean
as valueLong) or department name (as String).
 Please Note: Update requests replace all data fields in the userBean (i.e. data is not
appended or upserted). Send all elements back or the field values will be returned NULL.

Input: updateUserRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
flexValues []
status *
id *
cellPhone
email *
fax
firstName
lastName *
localeCode
location
in1 userBean *
loginName*
manager
middleInitial
phone
role *
timeZoneId
title

department (via
FlexField)

Output: updateUserResponse

Data Field Name Data Field Type Required Acceptable Values

updateUserReturn

updateUser Test Case:

Input: updateUserRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 253
<in1>
<flexValues>

<item>
<fieldName>department</fieldName>
<valueStr>Accounting</valueStr>
</item>
<item>
<fieldName>department</fieldName>
<valueStr>Customer Service</valueStr>
</item>
</flexValues>
<id>28</id>
<status>Employee</status>
<cellPhone>923-429-1234</cellPhone>
<email>[email protected]</email>
<fax>923-429-1234</fax>
<firstName>Ulissis</firstName>
<lastName>Castillo</lastName>
<localeCode>Asia/Taipei</localeCode>
<location>Seattle Office</location>
<loginName>ucastillo</loginName>
<manager>skarim</manager>
<middleInitial>A</middleInitial>
<phone>234-245-2350</phone>
<role>A</role>
<timeZoneId>Pacific/Apia</timeZoneId>
<title>Manager</title>
</in1>
</urn:updateUser>
</soapenv:Body>
</soapenv:Envelope>

Output: updateUserResponse

User Association Calls

User association are the elements that tie a specific user to a requisition within Taleo Business
Edition system including hiring managers, recruiters, interviewers, staffing agencies, etc.

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 254
association Definition:

Data Field
Data Field Type Required Acceptable Values
Name
sessionId String Yes Session ID obtained at login
requisitionId long Yes Requisition’s ID
Picklist of Association Values:
‘O’ = Owner
association String Yes ‘A’ = approvers (in order)
‘F’ = offer approvers (in order)
‘V’ = agencies
IDs of user associated with given
userId long Yes
requisition.
seqNo int No Sequential number for approvers

getAssociatedUsers Element:
Operation type: Request-response.
 The endpoint receives a message to get a users association within a given requistion,
and sends a correlated message array of User IDs.

Input: getAssociatedUsersRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received at
in0 String Yes
Login
in1 Long Yes Requisition ID
Picklist of Association
Values:
‘O’ = Owner
in2 String Yes ‘A’ = approvers (in order)
‘F’ = offer approvers (in
order)
‘V’ = agencies

Output: getAssociatedUsersResponse

Data Field Name Data Field Type Required Acceptable Values

getAssociatedUsersReturn Array of User IDs

getAssociatedUsers Test Case:

Input: getAssociatedUsersRequest

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 255
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:getAssociatedUsers>
<in0>webapi-6686750025617579220</in0>
<in1>15</in1>
<in2>O</in2>
</urn:getAssociatedUsers>
</soapenv:Body>
</soapenv:Envelope>

Output: getAssociatedUsersResponse

removeAssociatedUser Element:
Operation type: Request-response.
 The endpoint receives a message to remove an association of a user to a requisition, and
sends a correlated message only if error occurred.

Input: removeAssociatedUserRequest

Data Field Name Data Field Type Required Acceptable Values

Session ID received
in0 String Yes
at Login
in1 Long Yes ID of Requisition
Picklist of Association
Values:
‘O’ = Owner
in2 String Yes
‘A’ = approvers (in
order)
‘F’ = offer approvers

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 256
(in order)
‘V’ = agencies
in3 Long Yes ID of User

Output: removeAssociatedUserResponse

Data Field Name Data Field Type Required Acceptable Values

removeAssociatedUserReturn

removeAssociatedUser Test Case:

Input: removeAssociatedUserRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:removeAssociatedUser>
<in0>webapi-6686750025617579220</in0>
<in1>15</in1>
<in2>O</in2>
<in3>7</in3>
</urn:removeAssociatedUser>
</soapenv:Body>
</soapenv:Envelope>

Output: removeAssociatedUserResponse

setAssociatedUser Element:
Operation type: Request-response.
 The endpoint receives a message to set a user’s association to a requisition, and sends a
correlated message only if error occurred.

Input: setAssociatedUserRequest

Data Field Name Data Field Type Required Acceptable Values

in0 String Yes Session ID received

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 257
at Login
in1 Long Yes ID of requisition
Picklist of Association
Values:
‘O’ = Owner
‘A’ = approvers (in
in2 String Yes
order)
‘F’ = offer approvers
(in order)
‘V’ = agencies
in3 Long Yes ID of User
Sequence Number of
user to association
in4 String No value (i.e. first
approver = 1, second
approver = 2, etc.)

Output: setAssociatedUserResponse

Data Field Name Data Field Type Required Acceptable Values

setAssociatedUserReturn

setAssociatedUser Test Case:

Input: setAssociatedUserRequest

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:TBEWebAPI">
<soapenv:Header/>
<soapenv:Body>
<urn:setAssociatedUser>
<in0>webapi-6686750025617579220</in0>
<in1>15</in1>
<in2>O</in2>
<in3>7</in3>
<in4>1</in4>
</urn:setAssociatedUser>
</soapenv:Body>
</soapenv:Envelope>

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 258
Output: setAssociatedUserResponse

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 259
Revision Control
This portion of the document provides for a historic backlog of document changes, please refer
to the below table for details on document changes.

Version Details and Background

Date Document Document Changes
Sept. 2009 API Guide_sept09.doc  Complete Document re-write
 General spelling, document grammar fixes
 Page 157: Per BUG 8550, made note on integration
values (post | value defined within GUI) and in
getLookup response are not useable via the API for
Dec. 2009 API Guide_dec09.doc
source, state, country, race and veteran - only field
names can be used.
 Page 54: per BUG 6962, fixed getCandidateDetails call
to include <in7> attribute for includeOffers
 Page 72: fixed sample XML for createCandidate
(cellPhone attribute listed twice)
 Page 73: fixed sample XML for updateCandidate
Jan. 2010 API Guide_jan10.doc
(ending URN stated incorrect)
 Page 67: searchCandidate keys/values listed
"ReasonRej', changed to 'reasonRej'
 Page 97: put in comment for BUG 9470. API
Mar. 2010 API Guide_mar10.doc overwrites defined <creator> field with API logged in
session userName value
 Page 8: added Revision / Version Control Section for
document update logging
 Page 195: added ‘isTemplate’ searchRequisition
attribute per BUG 9165. API now allows searching job
library where attribute isTemplate = true.
 Page 182: removed city and state attributes from
createRequisition. City and State fields are system
May 2010 API Guide_may10.doc derived from <location> variable. Location field maps
to Taleo location organization table which
encompasses defined city and state maps for each
defined location.
 Page 157: per BUG 9662 added note for getLookup
‘fieldName’ requiring true custom database field
name versus descriptive (GUI) field name.
 Page 13: per BUG 9869 added section ‘Date and Time

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 260
Field Description’ for dateTime stamp description.
 Page 15: added Field Character Limits section.
 Page 98: put in comment for BUG 10290. API
July 2010 API Guide_aug10
overwrites defined <creator> field in updateContact
bean with API logged in session userName value
 Changed document branding
 Per version 11.3, added:
• departmentBean and associated calls
• locationBean and associated calls
• regionBean and assocated calls
 In createUserWithPermissions, added following
accessible/assignable <attributes>:
• reviewManager(Boolean)
• reviewApprover(Boolean)
 In userBean, added following new (standard
template) accessible fields:
• departmentId (String) – via FlexFieldBean
• departmentName (String) – via FlexFieldBean
 In candidateBean, added following new (standard
August 2011 API Guide_aug11
template) accessible fields:
• ssn(encryptedString) - via FlexFieldBean
• birthdate(encryptedDate) - via FlexFieldBean
 In employeeBean, added following new (standard
template) accessible fields:
• ssn(encryptedString) - via FlexFieldBean
• birthdate(encryptedDate) - via FlexFieldBean
 In requisitionBean, added following new (standard
template) accessible fields:
• departmentId (String) – via FlexFieldBean
• departmentName (String) – via FlexFieldBean
 updated description of Rolling Entities to denote
Employee Entity (in addition to candidate)

TALEO BUSINESS EDITION: WEB SERVICES API REFERENCE GUIDE PAGE 261
CONTACT
taleo.com – [email protected]
1.888.836.3669 – U.S.
+1.418.524.5665 – International
1.888.561.5665 – Customer Service

ABOUT TALEO

Leading organizations worldwide use Taleo on demand talent management solutions to assess, acquire, develop, and
align their workforce for improved business performance.

Taleo and all Taleo product and service names mentioned herein are trademarks or registered trademarks of Taleo in the
United States, France, The Netherlands, U.K., Canada, Australia, and several other countries.

All other product and company names mentioned herein may be the trademarks of their respective owners.
Copyright © 2011 Taleo Corporation. All rights reserved. No portion of this document may be reproduced in any form
without the prior written permission of Taleo Corporation.

Intrusion Detection Honeypots
From Everand
Intrusion Detection Honeypots
Chris Sanders
3/5 (2)
Welcomes You To ISO 9001: 2015 Awareness Training Programme
100% (2)
Welcomes You To ISO 9001: 2015 Awareness Training Programme
184 pages
How to Sell on Amazon and Product Research: Product Research Tips and Practical Guide on How to Find a Winning Product to Sell on Amazon Fba
From Everand
How to Sell on Amazon and Product Research: Product Research Tips and Practical Guide on How to Find a Winning Product to Sell on Amazon Fba
David L. Ross
No ratings yet
SF Calibration Impl en
No ratings yet
SF Calibration Impl en
114 pages
Taleo Business Edition: API Guide
No ratings yet
Taleo Business Edition: API Guide
264 pages
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
From Everand
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
Matthew C. Smith
No ratings yet
Content Creation Revolution with chatGPT
From Everand
Content Creation Revolution with chatGPT
Maria Cowen
No ratings yet
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet
Gray Hat Hacking the Ethical Hacker's
From Everand
Gray Hat Hacking the Ethical Hacker's
Çağatay Şanlı
5/5 (1)
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
From Everand
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
Jay Nans
No ratings yet
Osama the Gun
From Everand
Osama the Gun
Norman Spinrad
5/5 (1)
Human Nature Potential in Nurture
From Everand
Human Nature Potential in Nurture
David L. Hawk
No ratings yet
AI-Driven Digital Transformation: A Proven Blueprint for Responsible AI Scaling
From Everand
AI-Driven Digital Transformation: A Proven Blueprint for Responsible AI Scaling
Srikanth Victory
No ratings yet
BlockChain for Beginners
From Everand
BlockChain for Beginners
Matthew Smith
No ratings yet
10K Blueprint
From Everand
10K Blueprint
Cian O Farrell
5/5 (2)
TCWSFP12B UG ENus
No ratings yet
TCWSFP12B UG ENus
138 pages
Craftsman Creative: How Five-Figure Creators Can Build Six-Figure Businesses
From Everand
Craftsman Creative: How Five-Figure Creators Can Build Six-Figure Businesses
Daren Smith
No ratings yet
ChatGPT for Business: Strategies for Success
From Everand
ChatGPT for Business: Strategies for Success
Matthew C. Smith
1/5 (1)
Mastering Windows Automation with AHK 2.0
From Everand
Mastering Windows Automation with AHK 2.0
John Nunez
No ratings yet
Business English Writing: Effective Business Writing Tips and Will Help You Write Better and More Effectively at Work
From Everand
Business English Writing: Effective Business Writing Tips and Will Help You Write Better and More Effectively at Work
Mary G. Lewis
No ratings yet
The Stock Market from A to See - 2nd Edition
From Everand
The Stock Market from A to See - 2nd Edition
John Nunez
No ratings yet
Cybersecurity for Executives: A Guide to Protecting Your Business
From Everand
Cybersecurity for Executives: A Guide to Protecting Your Business
Matthew C. Smith
No ratings yet
How to Sell on Amazon Fba
From Everand
How to Sell on Amazon Fba
David L. Ross
No ratings yet
Improve Your Backgammon
From Everand
Improve Your Backgammon
Orion Fox
No ratings yet
The Future of Learning: Revolutionizing Education Through Generative AI: AI Books, #11
From Everand
The Future of Learning: Revolutionizing Education Through Generative AI: AI Books, #11
Mohammad
No ratings yet
Taleo Enterprise: Taleo Web Services User Guide
No ratings yet
Taleo Enterprise: Taleo Web Services User Guide
112 pages
Api Rest
No ratings yet
Api Rest
414 pages
Api Rest
100% (1)
Api Rest
346 pages
Api Rest
No ratings yet
Api Rest
354 pages
Api Rest
No ratings yet
Api Rest
405 pages
PP API Reference
100% (1)
PP API Reference
159 pages
REST API Developer Guide: Version 48.0, Spring '20
No ratings yet
REST API Developer Guide: Version 48.0, Spring '20
281 pages
IPG IntegrationGuide API NBD
No ratings yet
IPG IntegrationGuide API NBD
103 pages
Api Rest
100% (1)
Api Rest
280 pages
Api Rest Api
No ratings yet
Api Rest Api
415 pages
Api Rest
No ratings yet
Api Rest
416 pages
Api Rest
No ratings yet
Api Rest
421 pages
Api Rest
No ratings yet
Api Rest
363 pages
Api Rest
No ratings yet
Api Rest
281 pages
(Ebook) - Api Rest
No ratings yet
(Ebook) - Api Rest
269 pages
Api Rest
No ratings yet
Api Rest
322 pages
Salesforce Rest Api
No ratings yet
Salesforce Rest Api
284 pages
Api Rest
100% (1)
Api Rest
268 pages
Guidelines For Endpoint Config2 v2
No ratings yet
Guidelines For Endpoint Config2 v2
9 pages
PP API Reference
No ratings yet
PP API Reference
272 pages
Hci10 Web Services en
No ratings yet
Hci10 Web Services en
38 pages
Rest Api
100% (2)
Rest Api
22 pages
Api Rest
No ratings yet
Api Rest
220 pages
Aero Seal
No ratings yet
Aero Seal
14 pages
Group Life Assurance in Myanmar
No ratings yet
Group Life Assurance in Myanmar
2 pages
(Maria Brouwer) Governance and Innovation (Routled
No ratings yet
(Maria Brouwer) Governance and Innovation (Routled
260 pages
Ownership and Possession
No ratings yet
Ownership and Possession
11 pages
ADSL Application Form
No ratings yet
ADSL Application Form
6 pages
Dairy Industry Analysis
No ratings yet
Dairy Industry Analysis
48 pages
Candlesticks Report A Guide To Candlesticks
100% (2)
Candlesticks Report A Guide To Candlesticks
19 pages
Smartphone As A Tool For Different Applications
No ratings yet
Smartphone As A Tool For Different Applications
4 pages
Drewy Demurrage & Detention Report
No ratings yet
Drewy Demurrage & Detention Report
34 pages
P. Anil Kumar Synopsis
No ratings yet
P. Anil Kumar Synopsis
6 pages
Translation Certification: Form H-1
No ratings yet
Translation Certification: Form H-1
2 pages
Agree or Disagree
No ratings yet
Agree or Disagree
2 pages
627317044FINAL - Detailed Advt 02 - 2024
No ratings yet
627317044FINAL - Detailed Advt 02 - 2024
14 pages
Baroda Companies
100% (1)
Baroda Companies
25 pages
Geographical Investigations
No ratings yet
Geographical Investigations
10 pages
Certificate of Analysis: Product: ACCESS Prolactin Calibrators
No ratings yet
Certificate of Analysis: Product: ACCESS Prolactin Calibrators
1 page
Garments Label
No ratings yet
Garments Label
7 pages
Fast Track Quick Reference
No ratings yet
Fast Track Quick Reference
7 pages
Fisheries Code
No ratings yet
Fisheries Code
33 pages
IA Carpentry
No ratings yet
IA Carpentry
103 pages
Clarion IDE Users Guide
No ratings yet
Clarion IDE Users Guide
302 pages
Elgamatic 100
No ratings yet
Elgamatic 100
1 page
Workshop Proposal
No ratings yet
Workshop Proposal
20 pages
ART 101 Syllabus - Summer - 2025
No ratings yet
ART 101 Syllabus - Summer - 2025
5 pages
Microsoft Nokia Deal: A SWOT Analysis: Adit Jha
No ratings yet
Microsoft Nokia Deal: A SWOT Analysis: Adit Jha
6 pages
Certificate
No ratings yet
Certificate
1 page
2022 09 15 Web Development (Com 225) Practical Manual
No ratings yet
2022 09 15 Web Development (Com 225) Practical Manual
20 pages
BS en Iso 14692-3-2017
No ratings yet
BS en Iso 14692-3-2017
46 pages