[NewSearch millions of jobs from your AI agent with MCP→](/blog/jobspipe-mcp-server)

[All posts](/blog)

Guide·Jul 16, 2026·5 min read

# Taleo API: pulling job postings from Oracle's legacy ATS

Taleo's own API is customer-scoped, and its public postings live across three different career-site URL patterns and HTML schemas with their own bot detection. Why Taleo is high-maintenance to read, and how to pull every Taleo career site through one jobs API.

![Dvir Atias](/authors/dvir-atias.jpg)

Dvir Atias

Founder, JobsPipe

Taleo is one of the oldest enterprise applicant tracking systems, now part of Oracle, and still runs hiring for a long tail of large employers. So **Taleo API** gets searched by developers who need those postings - and runs into the usual enterprise wall.

## The Taleo API surfaces

-   **The Taleo REST/SOAP API** - the customer-scoped integration surface for requisitions, candidates, and offers, authenticated per Taleo instance. It is provisioned for the employer’s own integrations, not for third parties reading public jobs.
-   **The career sites** - where public postings actually live. The catch, unique to Taleo’s age: employers run across three different URL patterns and HTML schemas, each with its own bot-detection quirks.

## Why Taleo is high-maintenance

There is no public, cross-tenant Taleo endpoint and no list of Taleo customers. Reading postings means parsing three career-site variants, handling bot detection, and keeping the tenant list current as enterprises migrate off Taleo onto Oracle Recruiting Cloud - a standing maintenance cost, not a one-time scrape.

## Every Taleo career site through one jobs API

JobsPipe absorbs that maintenance and serves Taleo postings through one normalized [jobs API](/jobs-api), the same schema as 30+ other sources:

```
curl https://api.jobspipe.dev/v1/jobs/search \
  -H "Authorization: Bearer jp_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "source_or": ["taleo"], "job_title_or": ["project manager"], "posted_at_max_age_days": 30 }'
```

Scope to one employer with `company_name_partial_match_or`. More on our [Taleo source page](/sources/taleo), and how it compares in [the best jobs APIs of 2026](/blog/best-jobs-api-2026).

Taleo postings without the three-schema scraper - one jobs API, free tier included.

## Frequently asked questions

### Does Oracle Taleo have a public jobs API?

No. Taleo's REST/SOAP API is customer-scoped for the employer's own integrations. Public postings live on career sites, and Taleo employers run across three different URL patterns and HTML schemas, each with its own bot detection.

### How do I pull job postings from Taleo?

Reading Taleo means parsing three career-site variants and keeping the tenant list current. JobsPipe absorbs that maintenance and serves Taleo postings through one normalized jobs API in the same schema as 30+ other sources.

[

← Previous

Which ATS APIs are actually public? The 2026 job-data reference

](/blog/public-vs-gated-ats-apis)[

Next →

Jobvite API: what you can pull, and the feed most customers never enable

](/blog/jobvite-api-jobs)

---
Canonical URL: https://jobspipe.dev/blog/taleo-api-jobs
Title: Taleo API: pulling job postings from Oracle's legacy ATS
Description: Taleo's own API is customer-scoped, and its public postings live across three different career-site URL patterns and HTML schemas with their own bot detection. Why Taleo is high-maintenance to read, and how to pull every Taleo career site through one jobs API.