Breezy HR Jobs Scraper

What does Breezy HR Jobs Scraper do?

Extract real public jobs from company career boards hosted by Breezy HR. This Actor does not substitute another provider, generate sample jobs, or turn page navigation into records. No paid vendor API key is required. The default is a verified public source, with an output limit of 10 actual listings. Results change as employers publish or remove vacancies.

How does extraction work?

The Actor reads the company board’s public /json feed, filters available source location, department, country, remote flags and posting dates, then retrieves full JobPosting JSON-LD from matching public /p/ detail pages. Descriptions are required and source URLs/IDs must agree. Detail requests use bounded concurrency, capped at four. Search queries are matched against actual title, description, employer and department text, not metadata key names. A query appearing only in a full description is supported; an earlier title mismatch does not discard that listing.

What data can be extracted?

Field	Type	Meaning
jobId, jobUrl	string	Actual source identity and canonical public listing URL
title	string	Source-provided job/project title
companyName	string	Published employer or project company
location	string	Available source location labels, not the requested search location
description, descriptionHtml	string	Full public description and original markup when available
jobType, salary	string	Native contract labels and available compensation data
skills	array	Explicit source skill labels when available
remote	boolean	Source remote availability; hybrid can count as remote availability
datePosted	string	Source publication date
rawData	object	Rich original public fields and matching list/detail records

The existing 21-field normalized contract is retained. Unknown, null, blank and empty-container values are omitted; genuine zero and false values remain. No currency, employer, rate, date or location is guessed. Description markup is untrusted source content; sanitize it before rendering in your own application. A listing URL is not evidence that an application was submitted.

These simplified records were observed in a real local run on 2026-10-23. They are documentation, not fallback rows inserted into future runs; listings can change. The actual dataset also contained full descriptions and rich source fields.

[
  {
    "title": "AI Business Consultant Intern",
    "companyName": "Univers",
    "jobUrl": "https://univers.breezy.hr/p/6299ce691d5b01-ai-business-consultant-intern"
  },
  {
    "title": "AI Engineer",
    "companyName": "Univers",
    "jobUrl": "https://univers.breezy.hr/p/5e3cd0dda3ac01-ai-engineer"
  }
]

How to run the Actor

1. Open the Input tab and keep the default source or provide an official public board/search URL.
2. Set maxItems, normally 10, and optional searchQuery, keyword or location values.
3. Run and inspect the actual dataset together with RUN_SUMMARY and SOURCE_METADATA.
4. Download JSON, HTML, CSV or Excel, or use the API tab for integrations.

Input, source URLs and filtering

maxItems defaults to 10, with a range of 1–1000. searchQuery takes priority over the legacy keyword shortcut. startUrl overrides startUrls; otherwise the configured public default is used. Multiple sources share an output cap. Native board location, department, country and recognized remote URL filters take priority over corresponding shortcuts. Location/country checks use actual source values. remoteOnly means at least one explicit source location permits remote work, including hybrid; it does not assert fully remote work. publishedAfter accepts an ISO date. Feed ordering is retained; the Actor does not claim a date sort that it has not implemented. Public /p/ job URLs are also supported.

Only public HTTPS routes and GET requests are supported here. Leave requestBody empty. Account, application-submission, consent and private-contact actions are not performed. The example company is a real configurable default, not a claim that it represents every employer using Breezy HR.

Diagnostics and verification

RUN_SUMMARY records actual output counts and status. SOURCE_METADATA contains source/detail request evidence, durations, bytes, status and explicitly configured proxy usage without credentials. ERROR_DIAGNOSTIC stays outside the dataset. Zero usable results fail the run, and inaccessible details are not replaced with navigation titles or synthetic descriptions. Sparse filters may legitimately produce fewer records. Not every possible native filter combination or production deployment has been verified by a local default test.

Test locally using apify run. Local storage is not automatically uploaded to Apify Console. Deployment requires authorized apify push access and a separate production run with the same input. Never remove maintenance based only on a local test or a successful empty crawler.

Costs, limitations and support

Public source reads do not need a paid vendor key, but Apify execution, storage and optional proxies can incur costs. Proxy fallback must be explicitly configured; no CAPTCHA, login requirement or source access control is bypassed. Consult current Store/platform pricing instead of relying on a fixed per-run estimate. Use public data responsibly under source terms and applicable law; avoid unnecessary personal-data collection. This Actor is not affiliated with Breezy HR or the employers listed. Use the Issues tab with a sanitized input, source URL and run ID for support. Do not include credentials.