/pracuj/companies/search

POST /api/pracuj/companies/search

Price: 1 credit

Browse the Pracuj.pl employer catalog by business category, location and remote-work

How to use it

Browse the Pracuj.pl employer catalog filtered by business category (and optionally a city and a remote-work toggle). This is a category-driven directory browse, NOT a search by company name — Pracuj does not expose a name lookup for employers. Each result carries the employer's profile id, numeric company id (usable with the company profile endpoint), name, logo, profile alias and url, the cities where it operates, the number of recommendations, its current open-offer count, whether it offers benefits and remote work, an optional promo video, and the profile's default language.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — Company business category to browse (one of: "office_administration", "research_development", "banking", "health_safety_environment", "construction", "call_center", "consulting", "energy", "education_training", "finance_economics", "franchise_own_business", "hospitality_tourism", "human_resources", "internet_ecommerce", "engineering", "it_administration", "it_software_development", "quality_control", "supply_chain", "marketing", "media_arts_entertainment", "real_estate", "customer_service", "physical_work", "legal", "production", "public_relations", "advertising_design", "public_sector", "sales", "transport_logistics", "insurance", "purchasing", "health_beauty_recreation", "other")
• count integer required — Max number of companies to return (min: 1)
• location string nullable — City or place name to restrict the catalog to
• is_remote boolean nullable — Only companies that offer remote work

Response

• @type string (default: "PracujCompanySearchItem")
• public_id string required
• company_id integer nullable
• name string required
• url string nullable
• alias string nullable
• image string nullable
• locations array (default: [])
• rating_count integer nullable
• offer_count integer nullable
• has_benefits boolean (default: false)
• is_remote boolean (default: false)
• video_url string nullable
• default_language 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.