/jazzhr/jobs/search

POST /api/jazzhr/jobs/search

Price: 20 credits

List the open job postings of one company's JazzHR career board by board handle. Each row carries the job id, title, location, department when the board publishes one, and the posting URL.

How to use it

Lists one company's board — JazzHR has no cross-company search, so the board handle must already be known. The board carries no filters at all: there is no keyword, location or department parameter, and count only trims the rows returned. Rows are a summary; call jazzhr/jobs with the id for the description, salary and dates. A handle answers in one of three ways: an empty list means a live board with nothing open right now, while a handle that names no board and a board whose tenant closed its JazzHR account are both a 412, so an empty list is evidence the employer is still on the platform and a 412 is not evidence the handle was misspelled.

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 handle from the career-page URL ({company}.applytojob.com) (examples: "ilsos", "farinspections", "thejointchiropractic"; minLength: 1)
• count integer required — Max number of job postings to return (min: 1; max: 3000)

Response

• @type string (default: "JazzhrJobSummary")
• id string required
• company string required
• location string nullable
• department string nullable
• 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 tenant's JazzHR account is deactivated 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.