POST /api/breezyhr/jobs
Price: 10 credits
Get one job posting from a company's BreezyHR career board by board handle and posting id (or a full posting URL): title, the full HTML and plain-text description, the board's publication date and the posting's original posted date, employment type, department, free-text salary and structured salary range, workplace type, applicant location requirement, the primary and additional locations, and the company block with its website.
A posting is addressed by the pair (company, posting_id) — an id from another company's board is a 412, so never carry an id across boards. posting_id also accepts the id-slug form and the full posting URL, and the company is then taken from it. published_at and posted_at are different dates and must not be merged: posted_at is when the posting was first created and can be a year older than published_at, which is when the board last published it. salary is whatever free text the board typed, while salary_range is structured and only a few postings carry it. workplace_type reads remote on the postings BreezyHR flags as remote and is absent on the rest, which does not mean the job is on site — the board says nothing.
access-token string requiredtimeout 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}.breezy.hr) (examples: "recruiting", "ablefy", "breezy"; minLength: 1)posting_id string required — Job posting identifier. Accepts a bare posting id, the id-slug form, or a full posting URL (examples: "9f0d48bae2ef", "9f0d48bae2ef-senior-data-engineer", "https://recruiting.breezy.hr/p/9f0d48bae2ef"; minLength: 1)@type string (default: "BreezyhrJob")id string requiredcompany string requiredalias string nullablejob_title string nullableurl string nullablepublished_at integer nullableposted_at integer nullableemployment_type string nullableemployment_type_id string nullabledepartment string nullablesalary string nullablesalary_range object nullable@type string (default: "BreezyhrSalaryRange")currency string nullablemin number nullablemax number nullableunit string nullabledescription string nullabledescription_plain string nullablesummary string nullableworkplace_type string nullableapplicant_location_requirement string nullablelocation object nullable@type string (default: "BreezyhrLocation")id string nullablename string nullablecity string nullablestate string nullablestate_id string nullablecountry string nullablecountry_id string nullableis_remote boolean nullableis_primary boolean nullableis_other_selected boolean nullableremote_type string nullableremote_label string nullablestreet_address object nullable@type string (default: "BreezyhrStreetAddress")formatted string nullablecustom string nullableis_other boolean nullablelatitude number nullablelongitude number nullablecomponents array (default: [])@type string (default: "BreezyhrAddressComponent")long_name string nullableshort_name string nullabletypes array (default: [])locations array (default: [])@type string (default: "BreezyhrLocation")id string nullablename string nullablecity string nullablestate string nullablestate_id string nullablecountry string nullablecountry_id string nullableis_remote boolean nullableis_primary boolean nullableis_other_selected boolean nullableremote_type string nullableremote_label string nullablestreet_address object nullable@type string (default: "BreezyhrStreetAddress")formatted string nullablecustom string nullableis_other boolean nullablelatitude number nullablelongitude number nullablecomponents array (default: [])company_info object nullable@type string (default: "BreezyhrCompany")name string nullablealias string nullableimage string nullablehas_multiple_locations boolean nullablecompany_website 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 — Company board not found, or the posting 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.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.