Jobgether Remote Jobs Scraper

This Actor parses publicly embedded JobPosting JSON-LD or state from a Jobgether jobs page. Its input supports a Jobgether HTTPS URL, optional local keywords, a result limit, and a bounded request timeout. It uses ordinary direct HTTP access with one attempt and does not expose proxy, user-agent, cookie, or alternate-route controls.

The Actor metadata and previous local documentation record HTTP 403 from the ordinary public request path. The batch therefore treats the Actor as SKIPPED and does not request Jobgether again. A 401, 403, 429, 451, or visible source-authored denial/challenge is terminal: no job rows are emitted; OUTPUT_SUMMARY, DIAGNOSTICS, and SOURCE_RECEIPTS preserve the observed result when a blocked response is received. HTTP 407 and generic transport failures are DEFERRED, not source blocks.

Run status

OUTPUT_SUMMARY.status is the actual Apify process outcome (SUCCEEDED or FAILED); resultStatus describes the data outcome (COMPLETE, LIMITED, SKIPPED, DEFERRED, NO_DATA, or FAILED). If a later dataset write or runtime failure occurs after one or more complete job records were stored, those records are preserved and the run is SUCCEEDED with resultStatus: LIMITED and limitedResults: true. Finalization failures downgrade stored rows to SUCCEEDED/LIMITED, persist a KVS diagnostic, and retry Actor exit once; a zero-row finalization failure becomes FAILED/FAILED through Actor.fail(). A fatal failure before any normal row is stored is FAILED/FAILED and uses Actor.fail(). Confirmed source blocks are handled as SUCCEEDED/SKIPPED; diagnostics stay in key-value storage and are never pushed as dataset items.

The Chrome comparison showed a public listing with title, employer, geographic eligibility labels, employment type, and category. A public detail page also showed the role overview, language, hard and other skills, qualifications, responsibilities, interview stages, description sections, and company details. The current parser does not yet prove a greater-than-20-fact normal record, and no enriched dataset is claimed while the ordinary request path is blocked.

Offline checks

From this directory, npm test, npm run check, and apify validate-schema validate parser/access handling and Actor schemas without contacting Jobgether. Do not run this Actor against a route after a confirmed source block. For local dataset validation, pass a fresh actor-relative storage directory created by an authorized ordinary run to npm run validate -- <storage-dir>; never use --purge or reuse an existing store.

No Apify Cloud push or run is part of this Actor's local status.