TaleoConnector

Company code of the company

Url endpoint that will provide the URL for following messages

Connect

Are we connected

The endpoint receives a message to create an account, and sends a correlated message of account ID. Accounts are the companies and organizations involved with your business such as employers, customers, search firms, agencies, etc.

Create an attachment for a specific candidate, and sends a correlated message of attachment ID. 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).

Create a background check. 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.

Create a candidate

Create a Contact

Create a contact log

Create a department

Create a contact record that somebody sent an email to the user (INBOUND EMAIL).

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.

Create an employee

Create an attachment for a specific ID associated with a specific entity (i.e. Candidate, Employee, Account, etc.).

Create an event

Create an interview instance for a specific candidate.

Link an entity (by ID) to another entity (by ID) in Taleo Business Edition.

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

Create a Location.

Create an offer for a specific candidate.

Create a reference for a specific candidate

Create a Region

Create a requisition

Create a requisition template. Templates are the available jobs preloaded in Taleo for users to post easily with consistency. They are stored in the job library.

Create a task.

Create a User. Users are all the people with access to your Taleo Business Edition system including hiring managers, recruiters, interviewers, staffing agencies, etc. For more details check Taleo Business Guide User’s role:

• 'A' = Administrator
• 'M' = Hiring Manager
• 'R' = Recruiter
• 'E’ = Employee
• 'G' = Agency
• ‘-‘ = no access

Create a user with permission attributes

Delete an Account.

Delete an attachment

Delete a background check instance.

Delete a candidate

Delete a contact

Delete a contact log

Delete a department

Delete an employee

Delete an employee by employee number

Delete an event instance

Delete an interview instance.

Delete a Location.

Delete an offer instance

Delete a reference instance.

Delete a Region

Delete a requisition instance

Delete a specific rolling entity instance based on ID

Delete a task instance

Delete a user

Disconnect

Get an account details

Get an account history.

Get a users association within a given requisition.

Get an attachment by attachment ID

Get attachment data by ID

Get attachment(s) by candidate id.

Get a specific background check by ID

Get all background checks for a specific Candidate ID

Get the offer letter binary attachment associated with a candidate (based on offer ID).

Get the primary resume binary attachment associated with a candidate.

Get a status of a requisition for a particular candidate

Get a candidate general information by ID

Get candidate detailed information by ID.By default all flags are true

Get a Candidate transaction history

Get the rolling entity specific to a candidate’s work history form details

Get all candidates by Requisition ID

Get a contact details

Get a Contact transaction history

Get a contact log details by contact log ID

Get contact log(s) associated with any Taleo Business Edition entity that supports storing of contact logs

Get a Department details

Get a Department details

Get all Departments. This functions similar to getLookUp Request.

Get employee general information by ID

Get employee general information by Number

Get the all the application modules the company code has turned on.

Get attachment(s) associated with any Taleo Business Edition entity that supports attachment upload.

Get event(s) associated with any Taleo Business Edition entity that supports storing/creation of calendar events.

Get event details by event ID

Get interview details by interview ID

Get interview(s) associated with any Taleo Business Edition candidate

Get a Location details

Get a Location details

Get all Locations.

Retrieve the token results of a login session ID.

Lookup picklist values for a given field. Metadata and picklist fields are any field (standard or custom) that associate drop-down list of values for data consistency. 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.

Retrieve all field values within an entity. Returns all fields within the entity including:

• displayName (application field name)
• integrationName (API / external field name)
• isCustom (whether the field is a standard or custom field in TBE)
• isReadOnly (whether the field is writable or read-only)
• isRequired (whether the field is application-required for data entry)
• type (the type of field defined)

Get offer details by offer ID.

Get offer(s) associated with any Taleo Business Edition candidate.

Get all public events within a start date and end date

Get reference details by reference ID.

Get reference(s) associated with any Taleo Business Edition candidate

Get a Region details

Get a Region details.

Get all Regions. This functions similar to getLookUp Request.

Get requisition details by requisition ID

Get a Requisition transaction history. 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.

Get requisition(s) associated with any Taleo Business Edition candidate

Get a specific rolling entity for a candidate or employee. There is no ‘ALL’ function; a call is configured for the pulling of each rolling entity type:

• WORK_HISTORY
• RESIDENCE_HISTORY
• EDUCATION
• REFERENCES
• CERTIFICATES_LICENCES

Get the system props of a company code using valid session variable. System-level properties return as string-string map:

• 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

Get task(s) associated with any Taleo Business Edition entity that supports storing/creation of task events

Get task details by task ID

Get all tasks associated with a user

Get URL of a company code, or customer instance. This call is always performed using URL: https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter

Get an User details

Get a Users system history within Taleo Business Edition. 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.

Are we connected

Login a Partner.

Receives a message resume binary attachment, and sends back a passed output of resume data (using third-party provider ResumeMirror)

Creates a new candidate with contact information parsed with the original resume appended to the candidate record, and sends back: Candidate ID (either newly created or existing if duplicate) Duplicate Value where 0 equals none existing and 1 equals duplicate exists

Post a specific requisition to a supported posting location. For more details check Taleo Business Guide

Remove an association of a user to a requisition.

Remove an existing candidate assignment from a requisition (both based on ID variables)

Remove Linkage between two entities in Taleo Business Edition.

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

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.

Query all candidates based on defined key (field name) and value (data looking for).

Query all contacts based on defined key (field name) and value (data looking for)

Query all employees based on defined key (field name) and value (data looking for)

Query all requisitions based on defined key (fieldname) and value (data looking for).

Query all Users based on defined key (field name) and value (data looking for).

Set a user’s association to a requisition

Append an offer letter attachment by offer ID

Append a resume attachment to a candidate ID.

Submit a candidate to a requisition(s)

Unpost a specific requisition to a posting location

Update an existing account. Update requests replace all data fields in the accountBean (i.e. data is not appended or upserted).

Update an existing attachment. Note: Update requests replaces the attachment file (i.e. data is not appended or upserted)

Update an existing BackgroundCheck instance. Update requests replace all data fields in the backgroundCheckBean (i.e. data is not appended or upserted).

Update an existing candidate. Update requests replace all data fields in the candidateBean (i.e. data is not appended or upserted)

Update an existing contact. Update requests replace all data fields in the contactBean (i.e. data is not appended or upserted).

Update an existing contact log. Update requests replace all data fields in the contactLogBean (i.e. data is not appended or upserted).

Update an existing employee. Note: Update requests replace all data fields in the employeeBean (i.e. data is not appended)

Update an existing calendar event. Update requests replace all data fields in the calendarEventBean (i.e. data is not appended or upserted).

Update an existing interview instance. Update requests replace all data fields in the interviewBean (i.e. data is not appended or upserted)

Update an existing offer instance Update requests replace all data fields in the offerBean (i.e. data is not appended or upserted).

Update an existing reference instance. Update requests replace all data fields in the referenceBean (i.e. data is not appended or upserted).

Update an existing requisition instance. Update requests replace all data fields in the requisitionBean (i.e. data is not appended or upserted) 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.

Update an existing task event. Update requests replace all data fields in the taskBean (i.e. data is not appended or upserted).

Update an existing user. 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). 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.

Upsert, or append a candidate to a requisition

Update or create a department instance. 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

Upsert an existing employee record (create new and/or update existing). Upsert is the universal create and update command for Taleo Business Edition API. When using upsertEmployee as create command, use all the field except for employeeID, When using upsertEmployee as update command, use all fields or fields will be defined NULL (same as updateEmployee).

Update or create a Location instance.

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.

Update or create a Region instance. 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

Update an existing rolling entity instance. 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.