--- title: "Taleo API" description: "Taleo API: Enterprise vs Business Edition, the per-tenant Taleo Connect and TBE REST APIs, the taleo.net career sites, and one call for the postings." canonical: https://jobspipe.dev/sources/taleo date_published: 2026-06-16 date_modified: 2026-09-26 author: Dvir Atias --- # Taleo API Taleo's APIs (Taleo Connect Client for Taleo Enterprise, the TBE REST API for Business Edition) are credentialed per tenant, and Oracle is migrating customers to Oracle Recruiting Cloud; postings are public on .taleo.net career sections and tbe.taleo.net. JobsPipe does not collect Taleo; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. > Taleo has no public cross-employer jobs API, and JobsPipe does not collect Taleo. This page explains what Taleo exposes and how to reach the same employers through the boards JobsPipe does collect. **Canonical URL:** https://jobspipe.dev/sources/taleo ## Coverage JobsPipe does not collect Taleo. This page explains what Taleo exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (Workday, Greenhouse, Lever, Ashby, LinkedIn, Indeed, SmartRecruiters, Workable, Personio, Recruitee, Teamtailor, EURES, Paylocity, Breezy HR, CV-Library, Y Combinator, Bayt, JobTech (Sweden), Resume-Library, Arbeitnow, Himalayas, Rise, Manatal, Pinpoint, JobScore, HireHive, The Muse, Remotive, Remote OK, Jobicy, Working Nomads, Landing.jobs). ## Why Taleo jobs data is confusing Oracle Taleo comes in two products that share a name: Taleo Enterprise, with career sites at .taleo.net under /careersection paths, and Taleo Business Edition at tbe.taleo.net. Their APIs (Taleo Connect Client and the TBE REST API) are credentialed per tenant, and Oracle is migrating customers to Oracle Recruiting Cloud, a third URL pattern. Taleo career sites are public HTML with server-rendered search pages. There is no public list endpoint across tenants and no cross-tenant feed, and which product a customer is on determines the page shape. JobsPipe does not collect Taleo. Employers that run Taleo usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. ## Workarounds ### Crawl Taleo Enterprise, Business Edition and ORC separately Three page shapes, per-tenant configs and no directory. Feasible for tenants you already know. ### Get Oracle API credentials per tenant Reads one customer's own data with their credentials. Not a path to postings across employers. ### What JobsPipe offers instead JobsPipe does not collect Taleo. Search the same employers by name across the boards JobsPipe does collect (LinkedIn, Indeed, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever and Paylocity); sources[0].provider on each record names the board it came from. ## Fields available on every record - `id` - `job_title` - `company` - `company_domain` - `url` - `date_posted` - `discovered_at` - `last_seen_at` - `verified_at` - `status` - `closed_at` - `closed_reason` - `ghost_score` - `seniority` - `cities` - `state_code` - `min_annual_salary_usd` - `max_annual_salary_usd` - `technology_slugs` - `keyword_slugs` - `esco_skills` - `sources` ## FAQ ### What is the difference between Taleo Enterprise and Taleo Business Edition? They are two Oracle products that share a name. Taleo Enterprise runs career sites at .taleo.net under /careersection paths and integrates through Taleo Connect Client, while Taleo Business Edition runs at tbe.taleo.net and has the TBE REST API. Both APIs are credentialed per tenant, and which product a customer is on determines the shape of its career pages. ### Is Taleo being replaced by Oracle Recruiting Cloud? Oracle is migrating Taleo customers to Oracle Recruiting Cloud, which adds a third URL pattern alongside taleo.net career sections and tbe.taleo.net. Anyone reading Taleo employers' postings directly therefore has to handle Taleo Enterprise, Business Edition and Oracle Recruiting Cloud separately, each with per-tenant configs and no directory of which employers are on which product. ### Do Taleo career sites have a JSON feed? No. Taleo career sites are public HTML with server-rendered search pages, and there is no public list endpoint across tenants and no cross-tenant feed. The Taleo Connect Client and TBE REST API read one customer's own data with that customer's credentials, so they are not a route to postings across employers. ### How do I find a Taleo employer's jobs on LinkedIn or Indeed? Search by the employer's name. Employers that run Taleo usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. Filter POST /v1/jobs/search by company_name_partial_match_or to reach them on the boards JobsPipe collects; sources[0].provider on each record names the board it came from. ## Does Taleo have an API? Oracle Taleo comes in two products that share a name: Taleo Enterprise, with career sites at .taleo.net under /careersection paths, and Taleo Business Edition at tbe.taleo.net. Their APIs (Taleo Connect Client and the TBE REST API) are credentialed per tenant, and Oracle is migrating customers to Oracle Recruiting Cloud, a third URL pattern. Taleo career sites are public HTML with server-rendered search pages. There is no public list endpoint across tenants and no cross-tenant feed, and which product a customer is on determines the page shape. ## What JobsPipe returns for Taleo Nothing under "source_or": ["taleo"]: JobsPipe does not collect Taleo. Employers that run Taleo usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. Each record comes back with sources[0].provider, status, ghost_score, discovered_at, last_seen_at, seniority, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range. ## Related - **Product:** https://jobspipe.dev/jobs-api - **All sources:** https://jobspipe.dev/sources - **Docs:** https://docs.jobspipe.dev - **Sign up (free tier):** https://jobspipe.dev/signup --- Generated from structured data. View the rendered page at https://jobspipe.dev/sources/taleo. ## Further reading - [Oracle Recruiting Cloud API](https://jobspipe.dev/sources/oracle-recruiting-cloud) - [Taleo API: pulling job postings from Oracle's legacy ATS](https://jobspipe.dev/blog/taleo-api-jobs) --- Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin