/taleo/jobs/search

POST /api/taleo/jobs/search

Price: 10 credits

List the open job postings of one company's Taleo career section by tenant label, optionally narrowed by a free-text keyword and by the place, job field, organization, job type, schedule, level, employment status and posting age the board itself lists. Each row carries the internal job id, the requisition number that identifies the posting publicly, the title, the locations, the career section's own remaining display columns and the posting URL.

How to use it

Lists one board: Taleo publishes no cross-company directory, so tenant must come from a career-site URL, and career_section pins the search to one of a tenant's several sections and makes url usable. The row is thin — beyond title and locations a section's own display columns arrive as an unnamed ordered list, so call taleo/jobs with contest_no for the description and those fields. The eight facet filters are vocabularies each board defines for itself, so a 422 names what this board does list and means 'wrong spelling', not 'no results'. count is capped at 1000, and a larger board is served as its first 1000 rows in the board's own unnamed order. A board can report a few percent more open postings than it serves, so a slightly short result is complete.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tenant string required — Tenant label from the career-site URL ({tenant}.taleo.net) (examples: "aarcorp", "nato", "adb"; minLength: 1)
• count integer required — Max number of job postings to return (min: 1; max: 1000)
• career_section string nullable — Career-section segment of the career-site URL (/careersection/{career_section}/) (examples: "1", "ex", "external"; minLength: 1)
• query string nullable — Free-text keyword search over the postings (examples: "warehouse", "nurse"; minLength: 1)
• location string nullable — A place the board lists, spelled exactly as the board spells it (examples: "Florida", "Belgium", "SUGAR LAND"; minLength: 1)
• category string nullable — A job field the board lists, spelled exactly as the board spells it (examples: "Operations", "Warehouse", "Nursing & Care Management"; minLength: 1)
• organization string nullable — An organizational unit the board lists, spelled exactly as the board spells it (examples: "TECHNICAL EDUCATION CENTER"; minLength: 1)
• job_type string nullable — A job type the board lists, spelled exactly as the board spells it (examples: "Standard", "Temporary Work"; minLength: 1)
• schedule string nullable — A work schedule the board lists, spelled exactly as the board spells it (examples: "Full-time", "Part-time"; minLength: 1)
• level string nullable — A job level the board lists, spelled exactly as the board spells it (examples: "Experienced", "Entry Level"; minLength: 1)
• employee_status string nullable — An employment status the board lists, spelled exactly as the board spells it (examples: "Regular", "Temporary"; minLength: 1)
• posted_within string nullable — A posting-age window the board lists, spelled exactly as the board spells it (examples: "Today", "Last 7 Days", "Last 28 Days"; minLength: 1)

Response

• @type string (default: "TaleoJobSummary")
• id string required
• tenant string required
• contest_no string nullable
• locations array (default: [])
• columns array (default: [])
• hot_job boolean nullable
• url string nullable

Errors

• 422 — A location, category, organization, job_type, schedule, level, employee_status or posted_within value this board does not list Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Tenant has no reachable public career section Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.