Source · Taleo

Taleo Jobs API.

Every public Taleo Enterprise + Taleo Business Edition + Oracle Recruiting Cloud posting, one endpoint - normalized.

Public Taleo Enterprise + TBE + Oracle Recruiting Cloud

24h refresh

12 months retention

Why people are confused about the Taleo API

Oracle Taleo exists in two flavors that share a name but almost nothing else. Taleo Enterprise (TEE) is the Fortune 500 product - career sites like <tenant>.taleo.net with a complex URL structure (/careersection/2/jobsearch.ftl?lang=en&type=...). Taleo Business Edition (TBE) is the mid-market product - career sites like tbe.taleo.net/MANAGER1/<tenant>/jobboard. Their APIs, auth models, and HTML are all different.

Oracle is gradually sunset-migrating Taleo customers to Oracle Recruiting Cloud (ORC), which lives under <tenant>.oraclecloud.com. ORC is a third URL pattern to track. For aggregator use, you have to crawl all three product surfaces simultaneously and merge the results. JobsPipe maintains crawlers for TEE, TBE, and ORC and serves a unified feed regardless of which Oracle product each customer is on.

Option 1

Crawl TEE, TBE, and ORC separately

Three URL patterns, three HTML schemas, three sets of bot-detection idiosyncrasies. Doable but high-maintenance.

Option 2

Get Oracle API credentials per tenant

Requires Oracle Customer Connect onboarding through each tenant and only gives you that tenant's data. Not a path to aggregation.

Option 3

Use JobsPipe

Every Oracle-hosted career site across TEE, TBE, and ORC, one endpoint, normalized JSON.

Taleo Enterprise vs Taleo Business Edition

Taleo Enterprise (TEE) is Oracle's enterprise ATS, deployed at hundreds of Fortune 500s with deep customization, complex requisition workflows, and per-customer career-section URLs at <tenant>.taleo.net/careersection/... Taleo Business Edition (TBE) is the mid-market product, hosted at tbe.taleo.net/MANAGER1/<tenant>/jobboard and significantly simpler in both data model and URL structure. They share branding but their APIs, HTML, and crawler logic are entirely separate. Most search results for 'Taleo API' refer to TEE; if you're consuming a TBE tenant, half the documentation is irrelevant. JobsPipe abstracts the distinction.

Taleo API documentation

Taleo Enterprise APIs are documented inside Oracle Customer Connect (formerly Taleo Customer Connect) and are gated behind an Oracle customer login. There are several authenticated surfaces (Taleo Connect Client / TCC, Taleo Connect Service / TCS, Recruiting Web Services), each requiring per-tenant Oracle credentials. None of them are useful for aggregator use without per-customer onboarding. For consuming postings across many Taleo-using companies, the public career site is the practical answer, and JobsPipe normalizes it. Oracle Recruiting Cloud APIs are documented on the Oracle Cloud Help Center and follow Oracle's standard REST + OAuth pattern.

Sample request

curl "https://api.jobspipe.dev/v1/jobs?source=taleo" \
     -H "Authorization: Bearer $JOBSPIPE_KEY" \
     -H "Accept: application/json"

Sample response

{
  "id": "tl_NjgyMTM0NzU3",
  "source": "taleo",
  "tenant": "honeywell",
  "title": "Principal Systems Engineer, Avionics",
  "company": "Honeywell",
  "location": {
    "city": "Phoenix",
    "region": "AZ",
    "country": "US",
    "remote": false
  },
  "salary": {
    "min": 142000,
    "max": 178000,
    "currency": "USD",
    "period": "year",
    "source": "explicit"
  },
  "employment_type": "full_time",
  "posted_at": "2026-05-08T15:12:00Z",
  "expires_at": null,
  "apply_url": "https://honeywell.taleo.net/careersection/...",
  "description": "Honeywell Aerospace is hiring a Principal Systems Engineer to lead avionics-platform engineering for our next-generation flight-management systems ..."
}

Every Taleo job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.

Fields in every Taleo job record

idsourcetenanttitlecompanylocationsalaryemployment_typeremoteposted_atexpires_atapply_urldescription

Related on the blog

Guide

ATS API: one integration for 30+ applicant tracking systems

Read

Comparison

The 5 best jobs APIs in 2026 - comparison, pricing, and coverage

Read

Guide

How to scrape Workday job postings legally (and why you shouldn't)

Read

FAQ

Does JobsPipe cover Taleo Enterprise, Taleo Business Edition, and Oracle Recruiting Cloud?+

Yes - all three. We detect which Oracle product each tenant runs (Taleo Enterprise, TBE, or ORC) and adapt the crawler. Postings come back in the same normalized JSON shape.

Do I need Oracle API credentials to use JobsPipe?+

No. JobsPipe reads only public career sites. We do not call any authenticated Oracle Taleo or Oracle Recruiting Cloud API and never have access to applicant data.

How fresh is Taleo data?+

Public Taleo career sites are re-crawled at least every 24 hours. Large Fortune 500 tenants on TEE are refreshed every 6 hours.

Do I need to handle the Oracle Recruiting Cloud migration myself?+

No. When a tenant migrates from Taleo to Oracle Recruiting Cloud, JobsPipe detects the new career-site host and keeps serving postings from the same /v1/jobs?source=taleo&tenant=<slug> query with no consumer-side changes.

Try Taleo data free - 5,000 requests/month, no credit card.

Get a free API key