POST /api/pracuj/jobs/similar
Price: 5 credits
Get Pracuj.pl similar / recommended job offers for a job offer id
Get job offers similar or recommended for a given Pracuj.pl job offer. Each result carries the offer id, title and url, the hiring employer (id, name, profile url and logo), the workplace locations and a whole-Poland flag, the displayed salary text, a short job description snippet and an AI-generated candidate-fit summary, position levels, contract types, work schedules and work modes, attribute flags (e.g. immediate employment, Ukrainian-friendly), one-click-apply and super-offer flags, the recommendation rank and relevance score, and the last-published and expiry dates. Returns an empty list when the offer has no recommendations.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)job string required — Pracuj.pl job offer id, or a job offer URL containing it (examples: "1004924039", "https://www.pracuj.pl/praca/senior-golang-developer-warszawa,oferta,1004924039"; minLength: 1)count integer required — Max number of similar offers to return (min: 1)@type string (default: "PracujSimilarJob")id integer requiredgroup_id string nullableurl string requiredcompany_id integer nullablecompany_name string nullablecompany_url string nullablecompany_image string nullableworkplaces array (default: [])is_whole_poland boolean nullablesalary_text string nullabledescription string nullableai_summary string nullableposition_levels array (default: [])contract_types array (default: [])work_schedules array (default: [])work_modes array (default: [])primary_attributes array (default: [])is_super_offer boolean nullableis_franchise boolean nullableis_one_click_apply boolean nullableis_optional_cv boolean nullableis_jobicon_company boolean nullableis_highlighted boolean nullablescore number nullableposition integer nullablelast_published_at string nullableexpires_at string nullablebanner 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 — The entity was not found, or a precondition failed 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.