--- title: "Oracle Recruiting Cloud API" description: "Oracle Recruiting Cloud API: the per-tenant HCM REST API, the public CandidateExperience sites where requisitions show, and one call for the same postings." canonical: https://jobspipe.dev/sources/oracle-recruiting-cloud --- # Oracle Recruiting Cloud API Oracle Recruiting Cloud is the recruiting module of Oracle Fusion Cloud HCM and the successor to Taleo; its HCM REST API is scoped to one customer's environment and returns that company's requisitions, while every customer runs a public candidate-experience site. JobsPipe does not collect Oracle Recruiting Cloud; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. > Oracle Recruiting Cloud has no public cross-employer jobs API, and JobsPipe does not collect Oracle Recruiting Cloud. This page explains what Oracle Recruiting Cloud exposes and how to reach the same employers through the boards JobsPipe does collect. **Canonical URL:** https://jobspipe.dev/sources/oracle-recruiting-cloud ## Coverage JobsPipe does not collect Oracle Recruiting Cloud. This page explains what Oracle Recruiting Cloud exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (LinkedIn, Indeed, Y Combinator, Naukri, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever, Paylocity). ## Why Oracle Recruiting Cloud jobs data is confusing Oracle Recruiting Cloud is the recruiting module of Oracle Fusion Cloud HCM, the successor to Taleo. The Oracle HCM REST API is scoped to one customer's Fusion environment and authenticated with that tenant's credentials; it returns that company's requisitions to that company. Every ORC customer runs a public candidate-experience site, usually under a Fusion pod domain like .fa..oraclecloud.com/hcmUI/CandidateExperience or a custom careers domain. The site is backed by the recruitingCEJobRequisitions resource, which serves that tenant's public postings without a login. There is no tenant directory. JobsPipe does not collect Oracle Recruiting Cloud. Employers that run Oracle Recruiting Cloud 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 ### Use the Oracle HCM REST API Reads one customer's environment with their credentials. Not a path across employers. ### Read individual candidate-experience sites Possible per tenant whose pod domain you know. Discovery is on you. ### What JobsPipe offers instead JobsPipe does not collect Oracle Recruiting Cloud. 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 ### How do I find an Oracle Recruiting Cloud careers site URL? Most customers run their candidate-experience site under a Fusion pod domain shaped like .fa..oraclecloud.com/hcmUI/CandidateExperience, so the URL carries both the tenant name and the data center. Others put it behind a custom careers domain. Oracle publishes no tenant directory, so you need each employer's pod domain before you can read its postings. ### What does the recruitingCEJobRequisitions endpoint return? It is the resource behind each customer's public candidate-experience site. It serves that tenant's public postings without a login, which makes it the closest thing to a public jobs API that Oracle Recruiting Cloud has. It works per tenant only: there is no cross-tenant endpoint, and you have to know the tenant's pod domain first. ### Is Oracle Recruiting Cloud the same as Taleo? No, it is Taleo's successor. Oracle Recruiting Cloud is the recruiting module of Oracle Fusion Cloud HCM, and its data sits behind the Oracle HCM REST API, which is scoped to one customer's Fusion environment and authenticated with that tenant's credentials. Public postings appear on each customer's candidate-experience site rather than through that API. ### How do I find an Oracle Recruiting Cloud employer's jobs on LinkedIn or Indeed? Employers that run Oracle Recruiting Cloud usually post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse or another collected ATS alongside it. JobsPipe collects those boards, so filter POST /v1/jobs/search by company_name_partial_match_or for the employer. sources[0].provider on each record names the board it came from. ## Does Oracle Recruiting Cloud have an API? Oracle Recruiting Cloud is the recruiting module of Oracle Fusion Cloud HCM, the successor to Taleo. The Oracle HCM REST API is scoped to one customer's Fusion environment and authenticated with that tenant's credentials; it returns that company's requisitions to that company. Every ORC customer runs a public candidate-experience site, usually under a Fusion pod domain like .fa..oraclecloud.com/hcmUI/CandidateExperience or a custom careers domain. The site is backed by the recruitingCEJobRequisitions resource, which serves that tenant's public postings without a login. There is no tenant directory. ## What JobsPipe returns for Oracle Recruiting Cloud Nothing under "source_or": ["oracle-recruiting-cloud"]: JobsPipe does not collect Oracle Recruiting Cloud. Employers that run Oracle Recruiting Cloud 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/oracle-recruiting-cloud. --- Building this integration yourself? The steps above work. The alternative is one API over this source and 30+ others, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -X POST https://api.jobspipe.dev/v1/sandbox/jobs/search \ -H "Content-Type: application/json" \ -d '{"job_title_or":["software engineer"],"limit":5}' ``` 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