Greenhouse Job Board Snapshot
Pricing
$10.00 / 1,000 job board snapshots
Greenhouse Job Board Snapshot
Get a deterministic snapshot of a public Greenhouse job board: normalized job listings, total count, explicit truncation and SHA-256 hash. No browser, proxies or private data. One board per run.
Pricing
$10.00 / 1,000 job board snapshots
Rating
0.0
(0)
Developer
Federico bosi
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Security
Limited permissionsShare
Get a deterministic snapshot of a public Greenhouse job board. One dataset record contains normalized listings sorted by ID and a SHA-256 hash of the returned snapshot.
Input
{"board":"greenhouse","maxJobs":100}
Use the public board token, not a URL or API key. maxJobs is 1–500, default 100. No browser or proxy is required.
Output
One record: schemaVersion, board, sourceUrl, totalJobs, returnedJobs, truncated, jobs, contentHash. Each job includes id, title, location, url, updatedAt and requisitionId. Missing optional values are null. The hash covers returned data, not omitted jobs; check truncated before treating it as a complete board.
Example input: {"board":"greenhouse","maxJobs":1}. Illustrative output (example values; real contentHash is a SHA-256 hex digest):
{"schemaVersion":"1.0","board":"greenhouse","sourceUrl":"https://boards-api.greenhouse.io/v1/boards/greenhouse/jobs?content=false","totalJobs":2,"returnedJobs":1,"truncated":true,"jobs":[{"id":123,"title":"Example role","location":null,"url":null,"updatedAt":null,"requisitionId":null}],"contentHash":"<sha256-of-normalized-returned-snapshot>"}
Pricing
Active price: $0.01 per successful board-snapshot event, including up to 500 returned jobs. One successful board produces one dataset record and one charge, not one charge per job. A valid empty board is successful. Invalid input and upstream errors produce no charged result. The Apify maximum-charge limit applies.
Limits
One public Greenhouse Job Board GET request, 12-second upstream timeout, 2 MB response limit. No applications, candidate records or private Harvest API. No retries or browser scraping. Upstream changes can cause explicit errors.