# Jobgether Remote Jobs Scraper (`jobsapi/jobgether-remote-jobs-search-scraper`) Actor Extract public Jobgether remote jobs with company, location, dates, employment type, descriptions, requirements, skills, and source links. - **URL**: https://apify.com/jobsapi/jobgether-remote-jobs-search-scraper.md - **Developed by:** [Jobs API](https://apify.com/jobsapi) (community) - **Security:** Limited permissions - **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.99 / 1,000 jobgether remote job records This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## 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 -- `; never use `--purge` or reuse an existing store. No Apify Cloud push or run is part of this Actor's local status. # Actor input Schema ## `searchUrl` (type: `string`): Public Jobgether jobs or search URL. ## `keywords` (type: `array`): Optional local keyword filters matched against title, company, locations, and description. ## `maxItems` (type: `integer`): Maximum unique job records to return. ## `timeoutMs` (type: `integer`): Maximum time allowed for the public Jobgether request. ## Actor input object example ```json { "searchUrl": "https://jobgether.com/remote-jobs", "keywords": [], "maxItems": 20, "timeoutMs": 30000 } ``` # Actor output Schema ## `dataset` (type: `string`): No description ## `runSummary` (type: `string`): No description ## `diagnostics` (type: `string`): No description ## `sourceReceipts` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("jobsapi/jobgether-remote-jobs-search-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("jobsapi/jobgether-remote-jobs-search-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call jobsapi/jobgether-remote-jobs-search-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobsapi/jobgether-remote-jobs-search-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/Dgjc8vlR4T58fFw1S/builds/zqtXwwHSCYv93VZOT/openapi.json