Comeet Jobs Scraper avatar

Comeet Jobs Scraper

Pricing

from $2.99 / 1,000 comeet career roles

Go to Apify Store
Comeet Jobs Scraper

Comeet Jobs Scraper

Extract public Comeet job listings with company metadata, locations, job URLs, update timestamps, and cleaned description sections.

Pricing

from $2.99 / 1,000 comeet career roles

Rating

0.0

(0)

Developer

Jobs API

Jobs API

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a month ago

Last modified

Categories

Features

Limited permissions

Share

Comeet public job scraper

This Actor extracts source-backed public job data from Comeet-hosted career pages locally or on Apify Cloud. It reads the public company page, uses Comeet’s normal public positions endpoint, and enriches positions from the public detail endpoint. The page-provided access value is used only in memory for those requests; it is never logged, written to the dataset, or stored in the run summary.

Modes

  • search: fetch one or more public company career pages and enrich their current positions.
  • single: fetch one public position URL supplied in jobUrl or jobUrls.
  • multiple: fetch several public position URLs supplied in jobUrls, grouping requests by company page.

Example search input:

{
"mode": "search",
"startUrls": [{ "url": "https://www.comeet.com/jobs/reeco/0A.00D" }],
"maxItems": 25,
"fetchDetails": true,
"timeoutMs": 30000
}

Example direct input:

{
"mode": "multiple",
"jobUrls": [
"https://www.comeet.com/jobs/reeco/0A.00D/integrations-team-lead/06.F6B"
]
}

Each job record includes stable IDs, title/company/location data, employment and experience, remote details, full description and requirements text/HTML/sections, public questionnaires when exposed, employer metadata, public image metadata, application-related flags, selected public payloads, response hashes/statuses, and field-quality metadata. Empty/null values are omitted. Request diagnostics and receipts are stored under DIAGNOSTICS, never mixed into the jobs dataset.

The OUTPUT key-value record separates Apify's process status (SUCCEEDED or FAILED) from resultStatus (COMPLETE, LIMITED, SKIPPED, DEFERRED, NO_DATA, or FAILED). NO_DATA is used only when every requested company board's positions endpoint returned an explicit empty array with a successful HTTP receipt; each no_data_evidence entry includes the company URL, response URL, HTTP status, and response SHA-256. Empty or unrecognized responses without that evidence are DEFERRED. Direct-position mode cannot claim NO_DATA from an empty input. Explicit source denials (HTTP 401, 403, 429, or 451) and visible source-authored challenges stop further requests, discard staged job rows, and produce SUCCEEDED/SKIPPED. Generic transport or service unavailability is not treated as proof of a site block: with no stored jobs it produces DEFERRED, while stored jobs are preserved as LIMITED. Fatal non-block failures with no stored jobs produce FAILED/FAILED and invoke the Actor failure lifecycle. Only structurally valid, source-backed comeet_job records (including summary-only records) whose identity, content, job URL, and receipt match the requested source position are written to Dataset; diagnostics remain in key-value storage.

Run locally with apify run --input-file INPUT.json. Public detail requests are made one at a time using the runtime's ordinary request identity. If the site returns an explicit denial or human-verification challenge, the run stops without emitting job records; do not retry or route around that barrier. The Actor does not use login, proxy rotation, fingerprint overrides, or access-control bypass.