/pracuj/jobs

POST /api/pracuj/jobs

Price: 10 credits

Get Pracuj.pl job offer details by id

How to use it

Get full details of a Pracuj.pl job offer by its id. Returns the job title, full description and structured description sections (responsibilities, requirements, about the project, technologies), an AI-generated summary, the hiring employer (id and name), salary ranges per contract type (amount from/to, currency, pay period, gross/net kind), workplaces with locality, region and country, the job category taxonomy, position levels, work schedules, contract types and work modes, attribute flags (e.g. immediate employment, Ukrainian-friendly, many vacancies), required technologies and specializations, the application url with one-click-apply flag, employer logo and banner, and publication, last-published and expiry dates.

Parameters

• access-token string required

Request body

• timeout 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)

Response

• @type string (default: "PracujJob")
• id integer required
• url string required
• language string nullable
• employer_id integer nullable
• employer_name string nullable
• description string nullable
• ai_summary string nullable
• sections array (default: [])
  • @type string (default: "PracujJobSection")
  • type string required
  • items array (default: [])
• salaries array (default: [])
  • @type string (default: "PracujJobSalary")
  • contract_type string nullable
  • salary_from number nullable
  • salary_to number nullable
  • currency string nullable
  • time_unit string nullable
  • salary_kind string nullable
• workplaces array (default: [])
  • @type string (default: "PracujJobWorkplace")
  • locality string nullable
  • region string nullable
  • country string nullable
  • display_address string nullable
  • is_abroad boolean nullable
• categories array (default: [])
  • @type string (default: "PracujJobCategory")
  • id integer required
  • name string nullable
  • parent_id integer nullable
  • parent_name string nullable
• leading_category object nullable
  • @type string (default: "PracujJobCategory")
  • id integer required
  • name string nullable
  • parent_id integer nullable
  • parent_name string nullable
• position_levels array (default: [])
• work_schedules array (default: [])
• contract_types array (default: [])
• work_modes array (default: [])
• primary_attributes array (default: [])
• entirely_remote_work boolean nullable
• technologies array (default: [])
• specializations array (default: [])
• payment_models array (default: [])
• apply_url string nullable
• reference_number string nullable
• one_click_apply boolean nullable
• remote_recruitment boolean nullable
• is_directly_from_employer boolean nullable
• is_super_offer boolean nullable
• is_active boolean nullable
• is_archive boolean nullable
• is_withdrawn boolean nullable
• published_at string nullable
• last_published_at string nullable
• expires_at string nullable
• image string nullable
• banner 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 — Job offer not found 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.