/jobvite/jobs

POST /api/jobvite/jobs

Price: 5 credits

Get one job posting from a company's Jobvite career board by board slug and job id (or a full posting URL): title, hiring organisation, the customer's own requisition number, category, one or more locations with postal address, employment type, posted date, the full HTML and plain-text description, and the apply URL.

How to use it

A job is addressed by the pair (company, job_id); the same id under another board is a 412, so never carry an id across boards. Two ids exist and only one of them addresses the posting: job_id is the 8-character code in the URL, while req_id is the customer's own requisition number shown to humans and is not an input. The board slug is not the display name either — 'pathways' renders as Clarvida — so take it from a URL rather than from the company's brand. employment_type, posted_at and locations come from a structured block some tenants do not emit at all, in which case the single free-text location is what the page shows.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company board slug from the career-page URL (jobs.jobvite.com/{company}) (examples: "innio", "nutanix", "pathways"; minLength: 1)
• job_id string required — Job identifier from the posting URL. Accepts a bare id or a full posting URL (examples: "o30zAfwW", "https://jobs.jobvite.com/nutanix/job/o30zAfwW"; minLength: 1)

Response

• @type string (default: "JobviteJob")
• id string required
• company string required
• req_id string nullable
• company_name string nullable
• company_eid string nullable
• category string nullable
• category_id string nullable
• location string nullable
• location_id string nullable
• locations array (default: [])
  • @type string (default: "JobviteLocation")
  • locality string nullable
  • region string nullable
  • country string nullable
• employment_type string nullable
• description string nullable
• description_plain string nullable
• posted_at integer nullable
• url string nullable
• apply_url string nullable

Errors

• 422 — 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 — Company board not found, or the job id does not belong to that board 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.