/jazzhr/jobs

POST /api/jazzhr/jobs

Price: 5 credits

Get one job posting from a company's JazzHR career board by board handle and job id (or a full posting URL): title, hiring organisation, location and postal address, department, employment type, experience level, the full HTML and plain-text description, structured salary range, posted and valid-through dates.

How to use it

A job is addressed by the pair (company, job_id) — the same id under a different board is a 412, so never carry an id across boards. Either field accepts the full posting URL in job_id, and the company is then taken from it. Boards are tenant-themed: department, employment_type and experience_level come from a layout some tenants replace, and salary, posted_at, valid_through_at and address come from a structured block roughly two thirds of postings carry, so their absence means the board did not publish them rather than the job lacking them.

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", "easeinc"; minLength: 1)
• job_id string required — Job identifier. Accepts a bare id or a full applytojob.com posting URL (examples: "0ryIFxS5e0", "https://ilsos.applytojob.com/apply/0ryIFxS5e0/Accountant-II"; minLength: 1)

Response

• @type string (default: "JazzhrJob")
• id string required
• company string required
• company_name string nullable
• location string nullable
• address object nullable
  • @type string (default: "JazzhrAddress")
  • locality string nullable
  • region string nullable
  • postal_code string nullable
• location_type string nullable
• applicant_regions array (default: [])
• department string nullable
• employment_type string nullable
• experience_level string nullable
• description string nullable
• description_plain string nullable
• salary object nullable
  • @type string (default: "JazzhrSalary")
  • currency string nullable
  • min number nullable
  • max number nullable
  • unit string nullable
• posted_at integer nullable
• valid_through_at integer 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, the tenant's JazzHR account is deactivated, or the job is closed or unknown on 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.