POST /api/taleo/jobs
Price: 5 credits
Get one job posting from a company's Taleo career section by tenant, career section and requisition number (or a full posting URL): the internal job id, the title, the full posting description, the labels the career section displays and the values it fills them with, and the posting URL.
Identity is (tenant, career_section, contest_no): the same requisition number on another tenant resolves to nothing rather than to the wrong job. Passing a full posting URL fills all three in by itself. A posting that has closed returns 412, so a 412 means 'closed or wrong tenant', not a bad request. Beyond title and description, a career section names its own fields: detail_labels are the labels it displays and detail_values are the values it fills them with, both in page order, but their lengths differ, so read them as two ordered lists and do not zip them into pairs. Any clock time inside them is rendered in America/New_York, whatever the posting's own country.
access-token string requiredtimeout 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)career_section string required — Career-section segment of the career-site URL (/careersection/{career_section}/) (examples: "1", "ex", "external"; minLength: 1)contest_no string required — Requisition number of the posting. Accepts the bare number or a full posting URL (examples: "18800", "https://aarcorp.taleo.net/careersection/1/jobdetail.ftl?job=18800"; minLength: 1)@type string (default: "TaleoJob")id string requiredtenant string requiredcareer_section string requiredcontest_no string nullabledescription string nullabledescription_text string nullabledescription_sections array (default: [])detail_labels array (default: [])detail_values array (default: [])url string nullable422 — The request body did not validate 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 — Career section not found, or it has no open posting with this requisition number 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.