/pracuj/jobs/search

POST /api/pracuj/jobs/search

Price: 5 credits

Search Pracuj.pl job listings by keyword and filters

How to use it

Search Pracuj.pl job listings by keyword with rich filters — narrow by location and radius, job category, contract type, seniority level, working-time arrangement, work mode (on-site/hybrid/remote/mobile), posting recency, Polish voivodeship, minimum salary and its pay period, and toggles for whole-Poland remote, jobs for Ukrainians, immediate start, and disclosed salary. Each result carries the job id, title, hiring company (id, name, logo, profile url), a description snippet, an AI summary, locations with coordinates, position levels, contract types, work schedules and modes, and publication and expiry dates.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• text string required — Search query — job title, skill, or company name (minLength: 1)
• count integer required — Max number of jobs to return (min: 1)
• location string nullable — City or place name
• radius integer nullable — Search radius around the location in km (min: 0)
• category string nullable — Exact job category name as listed on Pracuj.pl, in the result language (Polish) (examples: "IT - Rozwój oprogramowania", "Sprzedaż", "Marketing")
• contract_type string nullable — Type of employment contract (one of: "employment", "specific_work", "mandate", "b2b", "replacement", "agency", "temporary", "internship")
• position_level string nullable — Seniority / position level (one of: "trainee", "assistant", "junior", "specialist", "senior", "expert", "team_manager", "manager", "director", "president", "blue_collar")
• work_schedule string nullable — Working time arrangement (one of: "full_time", "part_time", "temporary")
• work_mode string nullable — On-site, hybrid, remote or mobile work (one of: "office", "hybrid", "remote", "mobile")
• date_posted string nullable — Restrict to recently posted jobs (one of: "last_24h", "last_3_days", "last_7_days", "last_14_days", "last_30_days")
• region string nullable — Polish voivodeship (or abroad) (one of: "whole_poland", "lower_silesian", "kuyavian_pomeranian", "lodz", "lublin", "lubusz", "lesser_poland", "masovian", "opole", "subcarpathian", "podlaskie", "pomeranian", "silesian", "holy_cross", "warmian_masurian", "greater_poland", "west_pomeranian", "abroad")
• salary_min integer nullable — Minimum salary in PLN (min: 0)
• salary_period string nullable — Pay period the minimum salary applies to (monthly by default) (one of: "monthly", "hourly")
• whole_poland boolean nullable — Only fully-remote jobs available across all of Poland
• for_ukrainians boolean nullable — Only jobs aimed at candidates from Ukraine
• immediate_start boolean nullable — Only jobs with an immediate start
• with_salary boolean nullable — Only jobs that disclose a salary

Response

• @type string (default: "PracujSearchItem")
• id integer required
• group_id string nullable
• url string nullable
• company_id integer nullable
• company_name string nullable
• company_url string nullable
• company_image string nullable
• description string nullable
• ai_summary string nullable
• salary_text string nullable
• offers array (default: [])
  • @type string (default: "PracujSearchOffer")
  • id integer required
  • url string nullable
  • workplace string nullable
  • latitude number nullable
  • longitude number nullable
  • is_whole_poland boolean nullable
• position_levels array (default: [])
• contract_types array (default: [])
• work_schedules array (default: [])
• work_modes array (default: [])
• primary_attributes array (default: [])
• is_super_offer boolean nullable
• is_franchise boolean nullable
• is_one_click_apply boolean nullable
• is_remote_allowed boolean nullable
• is_optional_cv boolean nullable
• is_jobicon_company boolean nullable
• last_published_at string nullable
• expires_at 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 — 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.

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.