.png)
Oracle Taleo Enterprise Integration Guide
Connect Oracle Taleo Enterprise with enterprise applications through documented REST APIs, SOAP web services, scheduled file exchange, and orchestrated Martini workflows.
Oracle Taleo Enterprise integration options at a glance
Oracle Taleo Enterprise supports resource-oriented REST APIs for selected modules and operations, along with a substantial SOAP web-services footprint for documented business processes. Authentication varies by interface: REST may use OAuth 2.0 bearer tokens, while SOAP and Taleo integration utilities use service-specific credentials and security configuration. Taleo Connect Client and related Oracle processes support scheduled imports and exports for high-volume or file-based exchange. Martini can consume Taleo REST and SOAP endpoints, validate and transform CSV or XML files, schedule polling workflows, coordinate approved file transfers, expose controlled APIs, and apply retries, deduplication, and business rules without relying on direct database access.
| Integration point | Supported by Oracle Taleo Enterprise? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Limited | Oracle documents Taleo REST APIs for selected resource-oriented operations, such as retrieving or updating recruiting data. Availability varies by module, release, enabled services, and tenant configuration. | Martini can consume documented REST endpoints, manage bearer-token authentication, paginate or incrementally retrieve data where supported, map responses, and orchestrate updates to other systems. |
| SOAP APIs | Yes | Taleo provides SOAP web services for supported business operations, including processes that may not be available through the configured REST resources. | Martini can consume WSDL-defined services, construct namespace-aware XML requests, handle SOAP headers and service credentials, map responses, and distinguish SOAP faults from transient transport failures. |
| Webhooks / outbound callbacks | Not confirmed | A general-purpose webhook framework for all Candidate, Requisition, Submission, Offer, and Onboarding events was not confirmed. A documented callback may exist for selected customer configurations. | Martini can receive a documented Taleo callback when the relevant module explicitly provides one; otherwise it can use scheduled polling or file exchange rather than assuming event coverage. |
| Bulk, asynchronous, and batch exchange | Limited | High-volume exchange is commonly handled through Taleo Connect Client and scheduled Oracle integration processes. REST or SOAP bulk support is endpoint-specific. | Martini can orchestrate scheduled extraction and import workflows, process pages or files in controlled batches, maintain watermarks, and route partial failures for review. |
| File import and export | Limited | Taleo Connect Client and related processes can support scheduled imports and exports using configured data maps and files. Formats, schedules, and mappings depend on the implementation. | Martini can validate, transform, produce, consume, and deliver documented CSV, XML, or other exchange files through an approved file-transfer architecture. |
| File and attachment APIs | Limited | Candidate resumes, offer documents, and onboarding documents may have different API, permission, and size rules from core Taleo objects. Public attachment coverage must be verified per tenant. | Martini can process documented file or attachment endpoints and apply content-type, size, privacy, and retention controls; unsupported attachment operations should use an approved exchange process. |
| Authentication | Yes | REST may use OAuth 2.0-style bearer tokens, while SOAP and integration utilities use service-specific credentials, headers, certificates, or security configuration depending on the service. | Martini can store credentials and endpoint configuration securely, separate environments, apply authorization headers or SOAP security settings, and limit workflows to least-privilege Taleo roles. |
| Database access | No | Direct access to Oracle-managed Taleo production data is not a standard public integration method. | Martini should use documented Taleo APIs, web services, files, or approved integration utilities instead of connecting directly to the managed Taleo database. |
How Oracle Taleo Enterprise exposes data and business events
Oracle Taleo Enterprise REST APIs
Oracle documents REST APIs for selected Taleo resources and operations. Coverage is dependent on the module, Oracle release, enabled services, tenant configuration, and permissions, so each required object and write operation must be verified before implementation.
Martini implementation pattern
Martini implementation pattern: Martini authenticates with the configured bearer-token model, retrieves or updates the supported resource, handles pagination or incremental filters where available, maps the response into a canonical model, and sends the result to downstream systems. A durable watermark and stable Taleo identifiers support restartable synchronization.
Implementation sequence
Oracle Taleo Enterprise SOAP APIs
Taleo has a substantial SOAP web-services footprint for documented operations, including processes that may not be represented by the available REST resources. Service endpoints, WSDLs, headers, credentials, and write operations vary by service and release.
Martini implementation pattern
Martini implementation pattern: Martini consumes the documented WSDL-based service, constructs namespace-aware XML requests, applies the required SOAP security configuration, parses responses, and handles SOAP faults separately from network or server errors. Reusable workflows can standardize correlation, mapping, and retry behavior across services.
Implementation sequence
Taleo Connect Client file exchange
Taleo Connect Client and related Oracle processes can support scheduled imports and exports using configured data maps and files. This is distinct from a public REST or SOAP API, and exact formats and schedules depend on the customer’s Taleo implementation.
Martini implementation pattern
Martini implementation pattern: Martini runs on a schedule, obtains or produces files through an approved exchange location, validates structure and required fields, transforms CSV or XML content, and records file-level and row-level outcomes. The workflow can coordinate with the Taleo process without connecting to the managed database.
Implementation sequence
Scheduled Taleo synchronization
Because universal webhook coverage was not confirmed, scheduled polling and scheduled file exchange are important options for changed Candidates, Requisitions, Submissions, Offers, and Onboarding processes. The schedule and source must reflect the tenant’s documented capabilities.
Martini implementation pattern
Martini implementation pattern: Martini uses a scheduler-triggered workflow to retrieve changed data through a supported API or consume an export, retains a durable last-successful-run watermark, and processes records in controlled batches. It can use a documented Taleo notification only where the customer’s module explicitly supports one.
Implementation sequence
Common Oracle Taleo Enterprise integration patterns
Pattern 1: Synchronize candidates and submissions
When to use this pattern
Use this pattern when Taleo recruiting data must be shared with an HR, CRM, identity, or analytics platform and universal event delivery is unavailable. A scheduled API or export flow can retrieve changed Candidates, Requisitions, and Candidate submissions while controlling volume and duplicate processing.
Integration direction
Example Mapping
| Oracle Taleo Enterprise Field | Canonical Field | Target Field |
|---|---|---|
| Candidate.id | candidate.externalId | person.externalId |
| Candidate.firstName | person.givenName | person.givenName |
| Candidate.lastName | person.familyName | person.familyName |
| Candidate submission.status | application.status | jobApplication.status |
Martini implementation pattern
A scheduler-triggered Martini workflow retrieves incremental data or consumes a Taleo export, processes pages or rows, normalizes time zones and statuses, and upserts the target using stable identifiers. Business rules exclude unauthorized fields, detect invalid Candidate-to-Requisition relationships, and route permanent errors separately from retryable API failures.
Martini capabilities used
- workflows
- API consumption
- scheduled triggers
- data mapping
- business rules
- error handling
- retry and checkpoint management
Pattern 2: Publish requisitions and synchronize status
When to use this pattern
Use this pattern when an upstream HR system approves job requisitions and Taleo is the recruiting execution platform, or when requisition status must be returned to the originating system. The exact create and update operations must be confirmed for the customer’s Taleo configuration.
Integration direction
Example Mapping
| Oracle Taleo Enterprise Field | Canonical Field | Target Field |
|---|---|---|
| jobRequisition.externalId | requisition.sourceId | Requisition.referenceNumber |
| jobRequisition.title | requisition.title | Requisition.title |
| jobRequisition.status | requisition.lifecycleStatus | Requisition.status |
| jobRequisition.organization | requisition.organizationCode | Requisition.organization |
Martini implementation pattern
Martini receives an approved requisition through an API or file, validates required fields and allowed status transitions, and invokes the documented Taleo REST or SOAP operation. A reverse workflow retrieves status changes, maps Taleo lifecycle values to the source model, and uses correlation keys to avoid creating duplicate requisitions. Failed validations are held for correction while transient service failures are retried.
Martini capabilities used
- API exposure
- workflows
- SOAP and REST consumption
- data mapping
- validation
- business rules
- correlation and retries
Pattern 3: Exchange recruiting data through files
When to use this pattern
Use this pattern for high-volume or scheduled exchange when the required data is available through Taleo Connect Client or an approved Oracle import/export process, but individual API calls are inefficient or unavailable. It also suits targets that require CSV or XML files.
Integration direction
Example Mapping
| Oracle Taleo Enterprise Field | Canonical Field | Target Field |
|---|---|---|
| Candidate.id | candidate.externalId | candidateId |
| Requisition.referenceNumber | job.reference | jobRequisitionId |
| Candidate submission.status | application.status | applicationStatus |
| Offer.acceptanceStatus | offer.accepted | offerAccepted |
Martini implementation pattern
Martini schedules the exchange, retrieves a Taleo export or generates an import file, validates encoding and required columns, transforms rows, and delivers the result to the approved destination. It records the file checksum and row-level outcomes, prevents reprocessing of the same file, and routes rejected rows to an operational report.
Martini capabilities used
- scheduled workflows
- file processing
- CSV and XML handling
- data mapping
- validation
- deduplication
- error reporting
Pattern 4: Handoff accepted candidates to onboarding
When to use this pattern
Use this pattern when an accepted Offer or recruiting milestone should initiate onboarding, payroll, identity, or service-management actions. Since universal Taleo callbacks are not confirmed, the trigger can be a scheduled status poll, a documented notification, or a file export.
Integration direction
Example Mapping
| Oracle Taleo Enterprise Field | Canonical Field | Target Field |
|---|---|---|
| Candidate.id | person.externalId | ServiceNow subject person |
| Offer.acceptanceStatus | hire.offerStatus | ServiceNow onboarding status |
| Requisition.organization | hire.organizationCode | ServiceNow assignment group |
| Onboarding process.stage | onboarding.stage | ServiceNow task state |
Martini implementation pattern
Martini retrieves eligible Offers and Onboarding processes, applies rules for approval, consent, organization, and duplicate handoffs, then creates or updates downstream tasks. It stores the target identifier and source milestone, retries transient calls, and prevents duplicate task creation when a workflow restarts.
Martini capabilities used
- scheduled or event-triggered workflows
- API consumption
- data mapping
- business rules
- idempotency
- error handling
- monitoring
Applications commonly integrated with Oracle Taleo Enterprise
Oracle Taleo Enterprise is commonly connected to HR, payroll, identity, service management, document-signing, and enterprise relationship platforms. The exact scope depends on the customer’s Taleo module, Oracle release, enabled services, permissions, and the capabilities of the adjacent application.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Oracle HCM Cloud | Synchronize recruiting outcomes, workers, positions, organizations, and new-hire information across the Oracle HR landscape. | Oracle Taleo Enterprise → Martini → Oracle HCM Cloud | Martini can retrieve or receive approved recruiting and onboarding data from Taleo, map identifiers and organizational fields, apply lifecycle rules, and update Oracle HCM Cloud through its supported interface. The workflow can retain correlation IDs and route validation failures for review. |
| Workday | Exchange requisitions, candidate outcomes, new-hire data, organizations, and worker information when Taleo remains the recruiting platform and Workday is the HR system of record. | Oracle Taleo Enterprise → Martini → Workday | A scheduled Martini workflow can poll Taleo or consume an approved export, normalize candidate and hiring statuses, and call Workday APIs or process files. Reverse synchronization can publish approved requisition or organization data to Taleo where the tenant supports the required operation. |
| SAP SuccessFactors | Synchronize job requisitions, candidate and hiring data, employee identities, and onboarding information across recruiting and core HR processes. | Oracle Taleo Enterprise → Martini → SAP SuccessFactors | Martini can orchestrate incremental Taleo retrieval, map submission and offer states to SuccessFactors values, validate required fields, and submit the result through supported APIs or files. Retryable transport failures are separated from permanent mapping and validation errors. |
| ServiceNow | Create onboarding tasks, approvals, or service requests when a candidate reaches a hiring milestone, and return task status where required. | Oracle Taleo Enterprise → Martini → ServiceNow | Martini can poll Taleo for approved offer or onboarding milestones, create ServiceNow records through its API, store cross-system identifiers, and synchronize completion or exception status back to an approved Taleo process. |
| Salesforce | Share recruiting, staffing, partner, or candidate-related information where Salesforce participates in relationship or workforce processes. | Oracle Taleo Enterprise → Martini → Salesforce | A Martini workflow can retrieve selected Taleo Candidates, Requisitions, or Submissions, apply privacy and eligibility rules, transform them into Salesforce objects, and upsert using stable correlation keys. Sensitive fields can be excluded or redacted by policy. |
| Microsoft Entra ID | Coordinate identity provisioning for new hires after a candidate reaches an approved onboarding stage and the HR process authorizes account creation. | Oracle Taleo Enterprise → Martini → Microsoft Entra ID | Martini can consume an approved Taleo or HR-system onboarding result, validate identity attributes, and invoke the authorized Entra provisioning process. The workflow should keep identity creation subject to security review and avoid treating Taleo alone as the authoritative identity source. |
| DocuSign | Exchange offer or employment-document status when electronic signature is part of the recruiting process. | Oracle Taleo Enterprise → Martini → DocuSign | Martini can retrieve eligible Offers or document status through the documented Taleo process, call DocuSign APIs, correlate envelope identifiers, and update downstream status or exception records. Document permissions and retention requirements are evaluated before transferring content. |
| Oracle Payroll | Transfer accepted offers or new-hire information into payroll and downstream workforce processes. | Oracle Taleo Enterprise → Martini → Oracle Payroll | Martini can orchestrate a controlled handoff after offer acceptance, map Candidate, Submission, Offer, and onboarding fields to the payroll intake model, validate required employment data, and retry transient delivery failures while isolating rejected records. |
How to build a Oracle Taleo Enterprise integration in Martini
Objective
Configure the Taleo tenant endpoint and the authentication model required by the selected API or file process. Keep OAuth client secrets, service credentials, certificates, and environment-specific values outside workflow mappings.
Instructions in Martini
- Identify the Taleo module, release, endpoint, and required operation
- Configure REST OAuth bearer-token settings or SOAP service credentials
- Store secrets in Martini secure configuration
- Use separate development, test, and production credentials
- Confirm least-privilege Taleo roles and data access
Objective
Select the trigger that matches Taleo capabilities and the required freshness. Because universal webhook coverage is not confirmed, scheduled polling or file exchange is often the dependable default.
Instructions in Martini
- Use a documented Taleo callback only when explicitly available
- Configure a scheduler for incremental API polling where appropriate
- Choose a scheduled file exchange for high-volume or batch processes
- Define the synchronization window and watermark strategy
Objective
Obtain Candidates, Requisitions, Candidate submissions, Offers, Users, or Onboarding processes through the supported REST, SOAP, or file mechanism and preserve source identifiers for correlation.
Instructions in Martini
- Call the verified REST resource or SOAP operation
- Process API pagination and continuation rules
- Retrieve the approved export or receive the documented file
- Capture source timestamps, identifiers, and file metadata
- Separate authentication, authorization, validation, and transport failures
Objective
Use a Martini workflow to coordinate retrieval, transformation, business decisions, target delivery, checkpointing, and exception handling as one restartable integration process.
Instructions in Martini
- Use reusable workflow steps for common Taleo operations
- Branch by object type, status, or processing outcome
- Keep the checkpoint update after successful target delivery
- Use controlled concurrency for service limits
- Send permanent failures to an operational review path
Objective
Convert Taleo payloads or files into a canonical model and then into the target application’s fields, including explicit lifecycle, organization, location, and recruiter mappings.
Instructions in Martini
- Map stable Taleo identifiers to cross-system correlation keys
- Normalize dates, time zones, codes, and enumerated statuses
- Transform CSV or XML structures when using file exchange
- Exclude or redact sensitive fields that are not required
- Validate required relationships between Candidates, Requisitions, and submissions
Objective
Enforce eligibility, approval, privacy, deduplication, and lifecycle rules before writing to a target system or initiating onboarding activity.
Instructions in Martini
- Allow only approved Offer or onboarding milestones to trigger downstream actions
- Check whether a target object already exists before creating it
- Reject invalid Candidate-to-Requisition relationships
- Apply organization and data-access rules
- Keep status mappings explicit for each Taleo module
Common Oracle Taleo Enterprise data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Candidates | Synchronize applicant identity, contact, profile, and recruiting information. | Oracle HCM Cloud, Workday, SAP SuccessFactors, Salesforce, analytics platforms | Martini retrieves or receives Candidates through the available REST, SOAP, or export process, normalizes identifiers and sensitive fields, applies incremental rules, and upserts the target representation. |
| Requisitions | Publish job openings, requirements, organizational context, and requisition lifecycle status. | Oracle HCM Cloud, Workday, SAP SuccessFactors, job distribution processes | Martini maps approved requisition data, validates required fields and status values, submits supported REST or SOAP operations or generates import files, and records correlation identifiers. |
| Candidate submissions | Represent a Candidate’s application or submission against a Requisition and its recruiting status. | Oracle HCM Cloud, Workday, SAP SuccessFactors, reporting platforms | Martini correlates Candidate and Requisition identifiers, maps submission stages explicitly, deduplicates by stable Taleo identifiers, and isolates invalid status or relationship data. |
| Offers | Transmit offer details, acceptance state, and offer-related information for downstream hiring processes. | Oracle HCM Cloud, Oracle Payroll, DocuSign, ServiceNow | Martini applies eligibility and approval rules, transforms offer values, transfers only permitted fields or documents, and retries transient delivery failures without duplicating downstream actions. |
| Users | Represent recruiters, hiring managers, administrators, and other Taleo users involved in ownership and authorization. | Identity platforms, HR systems, reporting platforms | Martini can synchronize permitted user and organizational attributes where an approved API or export exposes them, while respecting role, organization, and personal-data restrictions. |
| Onboarding processes | Coordinate onboarding activities and process records initiated for a candidate or new hire. | Oracle HCM Cloud, Oracle Payroll, ServiceNow, Microsoft Entra ID | Martini polls or consumes an approved onboarding status source, applies milestone rules, creates downstream tasks or workforce records, and stores cross-system status and error details. |
Authentication and security considerations
Authentication varies by Taleo interface
REST APIs may use OAuth 2.0-style bearer tokens with tenant-specific endpoints, while SOAP services and Taleo integration utilities use service-specific credentials, headers, certificates, or security configuration. REST credentials should not be assumed to work for SOAP.
Least-privilege access
Use dedicated integration accounts with only the roles, permissions, and organizational data access required for the workflows. Separate development, testing, and production credentials.
Protect recruiting data
Candidate, offer, onboarding, and document data may contain personal or sensitive information. Use secure transport, secret storage, restricted logging, retention controls, and appropriate redaction.
Operational considerations for Oracle Taleo Enterprise integrations
Availability and versioning
Validate every required object and operation against the Taleo module, release, tenant configuration, and enabled services. Oracle releases and configuration changes can affect REST resources, WSDLs, fields, enumerations, and required values.
Throughput and synchronization
Check current Oracle service limits and tenant policies. Use pagination, incremental filters, controlled concurrency, backoff, and durable watermarks. For high-volume exchange, evaluate Taleo Connect Client and scheduled files instead of one request per record.
Idempotency and partial failure
Use stable Taleo identifiers and source correlation keys. For files, retain names, checksums, timestamps, import status, accepted rows, rejected rows, and error details. Retry transient failures but do not repeatedly submit permanent validation errors.
Documents and schema changes
Attachment and document operations may have different permissions, limits, and API coverage from core objects. Confirm content type, file size, retention, and privacy rules separately, and test representative payloads after Oracle changes.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than one endpoint
Martini coordinates Taleo REST calls, SOAP operations, scheduled files, target APIs, validation, business rules, and checkpoints in maintainable workflows rather than embedding logic in isolated scripts.
Make transformations reusable
Reusable mappings and workflow logic can normalize Candidate, Requisition, Submission, Offer, and Onboarding data across HR, payroll, identity, service, and analytics systems.
Improve operational control
Martini provides a structured place to manage secrets, retries, deduplication, partial file failures, error routing, monitoring, and environment-specific configuration as Taleo APIs and tenant settings evolve.
Expose controlled interfaces
Where downstream systems need a stable contract, Martini can expose an API façade that hides Taleo-specific REST, SOAP, polling, and file-exchange details while applying authorization and business rules.
Frequently asked questions
Oracle Taleo Enterprise can be integrated through documented REST APIs, SOAP web services, Taleo Connect Client and scheduled file imports or exports, and selected tenant-specific notification processes where explicitly available. The appropriate method depends on the module, release, resource, permissions, and volume. Direct access to the managed Taleo database is not a standard public integration approach.
Yes. Martini can integrate with Oracle Taleo Enterprise by consuming its documented REST APIs and SOAP web services, orchestrating approved file-based exchanges, scheduling synchronization workflows, mapping Taleo objects to target systems, and applying validation, business rules, retries, and checkpointing. A native Martini connector is not documented in the supplied research.
No. A dedicated Oracle Taleo Enterprise connector is not required. Martini can use Taleo’s confirmed native integration mechanisms, including REST APIs, SOAP web services, authentication methods, scheduled exports and imports, and approved file-exchange processes.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Oracle Taleo Enterprise. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from Oracle, infrastructure providers, file-transfer services, or other third-party systems depending on subscriptions, usage, and deployment model.
Use REST when the required resource and operation are available in the tenant and the OAuth-based authentication model is suitable. Use SOAP when the operation is exposed through Taleo web services or an existing WSDL-based process depends on it. Use Taleo Connect Client or scheduled file exchange for high-volume, batch, or file-oriented processes. The choice should be made per object and operation.
A universal webhook framework for all Candidate, Requisition, Submission, Offer, and Onboarding events was not confirmed. A documented callback or notification may be available for selected configurations, but integrations should otherwise use scheduled API polling or file exchange rather than assume complete event coverage.
Martini can use incremental API filters or documented exports, process pages or files in controlled batches, and retain a durable last-successful-run watermark. Stable Taleo identifiers and source-system correlation keys support idempotent upserts. Candidate, submission, offer, requisition, and onboarding statuses should be mapped explicitly because values can vary by module and configuration.
Martini maps REST JSON, SOAP XML, and documented file formats into canonical and target models, with validation and business rules for statuses, relationships, privacy, and required fields. Workflows can distinguish authentication failures, authorization errors, validation failures, rate limiting, timeouts, SOAP faults, and server errors, retry transient failures with controlled backoff, and route permanent or rejected records for operational review.
Related Martini documentation
APIs
Workflows
Integrate Oracle Taleo Enterprise with Martini
Use Martini to connect Oracle Taleo Enterprise REST APIs, SOAP web services, and approved file exchanges to the systems that support recruiting, onboarding, payroll, identity, and workforce operations.