Stripe & Figma Jobs API (Greenhouse) + Departments avatar

Stripe & Figma Jobs API (Greenhouse) + Departments

Pricing

$0.20 / 1,000 job results

Go to Apify Store
Stripe & Figma Jobs API (Greenhouse) + Departments

Stripe & Figma Jobs API (Greenhouse) + Departments

$0.2/1K jobs | Get jobs from the Stripe and Figma boards on Greenhouse with full descriptions, locations, departments and posting dates. Two tracked company boards, not every Greenhouse employer. No login or API key.

Pricing

$0.20 / 1,000 job results

Rating

0.0

(0)

Developer

Job Atlas

Job Atlas

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 hours ago

Last modified

Categories

Share

Greenhouse Tracked Company Jobs Scraper (No Login)

$0.2/1K jobs | Get jobs from the Stripe and Figma boards on Greenhouse with full descriptions, locations, departments and posting dates. Two tracked company boards, not every Greenhouse employer. No login or API key. Independent, unofficial tool. Not affiliated with or endorsed by Greenhouse, Stripe or Figma.

Search Stripe and Figma Greenhouse Jobs With Full Descriptions

Our scraper collects jobs from the two Greenhouse boards we track, Stripe and Figma, and lets you filter by keyword, posting age and your own rules on normalized fields. Every row carries the complete original description in text and HTML, the department, the location text and the apply link. It is ideal for job alerts on these two employers, hiring research and feeding your own job database.

Coverage today: two boards, Stripe and Figma. Jobs at other companies that use Greenhouse are not collected, and the earlier input that fetched any board you named is retired. Postings are only available once their full description has been verified, so a run can return fewer jobs than the live careers pages list.

  • Need jobs from many employers instead of one tracked board? Our LinkedIn Jobs Scraper searches LinkedIn by role and location. The trade-off: its postings come from LinkedIn, not from each employer's own Greenhouse board.
  • Same output format for other applicant-tracking boards, each with its own tracked companies: Ashby (Ashby's own board), Lever (Dun & Bradstreet), SmartRecruiters (ServiceNow, Canva, Experian, Western Digital and Delivery Hero). Pick by employer.
  • Browse all Job Atlas job scrapers: https://apify.com/jobatlas

Key Benefits

  • No login or API key: nothing to set up and no account at risk. Your run reads stored postings and does not request the Greenhouse website.
  • Low pricing: $0.20 per 1,000 jobs, with no start fee. Apify platform usage is included in that price.
  • Complete descriptions only: a posting appears once its full description is verified, so every row carries the original text and HTML, not a snippet.
  • No repeats across runs: schedule the same search and receive only postings you have not received yet.
  • Optional AI enrichment and English translation: funded by us, off by default, no API key needed and no extra charge.

How It Works

  1. Provide your search. Every field is optional, and the prefilled form already returns real jobs.

    • (optional) Keyword (e.g., engineer, customer success). A case-insensitive phrase matched against the stored title, the employer and the complete description, so it also finds roles that only mention the word.
    • (optional) Posted within (e.g., 24h, 7d, any). Default is any. When Greenhouse gives no reliable original posting date, the reported date is the day the job was first stored; later refreshes do not make a posting look new.
    • (optional) Work arrangements (remote, hybrid, onsite). Empty means all. The Greenhouse postings we checked state no work arrangement (0 of 10 sample rows), and a remote-only filter returned no jobs in our check. Leave this filter empty here.
    • (optional) Advanced filters, a rule over normalized fields in the shared nomad-agent-job-filter-v1 format. For example, jobs with a minimum pay of at least 50,000:
    {
    "schemaVersion": "nomad-agent-job-filter-v1",
    "expression": {
    "field": "data.compensation.minimum",
    "operator": "gte",
    "value": 50000
    }
    }

    Place it under the filters field. Unknown values do not satisfy ordinary comparisons, so a rule only keeps jobs that state the field. Few Greenhouse postings carry pay (1 of 10 sample rows), so a pay filter removes most jobs on this board.

  2. Set maxItems (default 100, at most 200; the prefilled form uses 10). Zero means 200. Filters, repeat suppression and failed enrichment can return fewer jobs.

  3. Run the Actor. When it finishes, open the dataset for your jobs. The RUN-SUMMARY record in the key-value store shows data freshness, candidate and delivery counts, and the final status.

Run the same search again and you get only postings you have not received yet; set dedupe.enabled to false to see everything again. A non-empty dedupe.key deliberately shares delivery history across searches for the same Apify user, for example to keep one alert history per profile. If delivery cannot be confirmed, the run fails instead of claiming success.

If the stored data is unavailable or stale, the run fails instead of falling back to website scraping.

Greenhouse departments are the employer's own labels and can include internal codes, for example 9014 Metronome - R&D.

Data You'll Receive

  • Job details: title, complete description (text and HTML), department and posting date.
  • Location: the location text as the employer wrote it (locations[].raw, for example Seattle or Bengaluru).
  • Employer: Stripe or Figma.
  • Links: the posting and apply URL.
  • Pay: minimum, maximum, currency and period, on some jobs (1 of 10 in our sample).
  • Source details: custom.data carries the Greenhouse board, internal job ID, requisition ID, first-published and updated timestamps, offices and departments.
  • Stable ID and source key (identity.source, identity.externalId) for deduplication across runs.

Sample output data

Here is an example job from this Actor. Long descriptions are shortened with … and empty fields are left out for space (the long offices list in custom.data is also left out); the real output keeps them as null.

{
"schemaVersion": "nomad-agent-job-v1",
"identity": {
"url": "https://stripe.com/jobs/search?gh_jid=8257935",
"source": "greenhouse",
"externalId": "stripe_8257935"
},
"data": {
"title": "Staff Software Engineer, Alloy Integrations",
"company": {
"name": "Stripe",
"department": "9014 Metronome - R&D"
},
"locations": [
{
"raw": "Seattle"
}
],
"application": {
"url": "https://stripe.com/jobs/search?gh_jid=8257935",
"postedAt": "2026-10-15"
}
},
"llm": {
"status": "not_requested"
},
"raw": {
"description": "Who we are\nAbout Stripe\nStripe is a financial infrastructure platform for businesses. Millions of co…",
"descriptionHtml": "<h2>Who we are</h2>\n<h3>About Stripe</h3>\n<p><span style=\"font-weight: 400;\">Stripe is a financial i…"
},
"custom": {
"data": {
"board": "stripe",
"language": "en",
"nativeId": "8257935",
"updatedAt": "2026-10-15T13:11:37-04:00",
"departments": [
{
"id": 332493,
"name": "9014 Metronome - R&D",
"parentId": 88204
}
],
"internalJobId": 3573249,
"requisitionId": "See Opening ID",
"firstPublished": "2026-10-15T12:48:50-04:00"
},
"schemaId": "https://raw.githubusercontent.com/Exdenta/jobatlas/main/integrations/shared/greenhouse-v1.schema.json"
}
}

Greenhouse Jobs API

Results are stored in a dataset that you can export as CSV, JSON or Excel, or read on demand through the Apify API. To run it from code or on a schedule, send an input like this:

{
"schemaVersion": "nomad-agent-inventory-search-v1",
"keyword": "engineer",
"postedWithin": "any",
"maxItems": 10,
"dedupe": {
"enabled": true,
"key": ""
}
}

Every dataset item follows the nomad-agent-job-v1 format with six roots: schemaVersion, identity, data, llm, raw and custom (schema). A missing fact is null; a known empty list is []. Source-specific facts follow the public Greenhouse schema named in custom.schemaId.

Optional AI enrichment and English translation

Both are independent opt-ins and both are off by default. You do not supply any API key, and they add no charge on top of the per-job price.

{
"schemaVersion": "nomad-agent-inventory-search-v1",
"keyword": "engineer",
"maxItems": 10,
"aiEnrichment": {
"enabled": true,
"accuracy": "silver"
},
"translateToEnglish": true,
"dedupe": {
"enabled": true,
"key": ""
}
}
  • aiEnrichment.enabled fills supported unknown fields and records where each value came from in llm. It cannot overwrite facts the source states. Jobs whose requested enrichment fails are withheld. Without it, llm.status is not_requested. aiEnrichment.accuracy is silver or gold.
  • translateToEnglish converts selected display fields into English. raw.description and raw.descriptionHtml always keep the original text.
  • Only when you turn them on, description text goes to OpenRouter for extraction and selected display text goes to DeepL for translation, using our accounts. The routes deny provider data collection but do not guarantee zero retention or EU-only processing. Sanitized extracted facts and translations may be cached by us.
  • Filters work on normalized values before English display translation.

Moving from earlier releases

This release uses the input format nomad-agent-inventory-search-v1. Earlier source-specific inputs fail with migration guidance; replace them with keyword or filters. Original descriptions are always included. identity.externalId is the source's own posting ID as represented in this output and may be spelled differently from earlier releases, so the stable key is the pair identity.source plus identity.externalId. Update stored comparison keys when you migrate; your delivery history may allow a one-time repeat. The custom extension is new (earlier releases used nomad-greenhouse-source-v1 with a different shape); the other five roots keep the nomad-agent-job-v1 contract. The top-level accuracy field is a compatibility override for aiEnrichment.accuracy and never enables enrichment by itself.

Support and Feedback

We improve these scrapers from your feedback. If something breaks or you need a filter:

  • Open an issue on the Actor's Issues tab.
  • If this Actor saved you time, a short review on the Store helps other users find it.

Run evidence

Checked on 2026-10-16 with small probe runs on the latest build as it was before the pay-per-event price took effect, each capped at 10 jobs or fewer:

  • NiejZzFfDjNZazZmx (SUCCEEDED, build 1.0.4): keyword engineer, maxItems 10: 10 job(s).
  • LoRdTA3z9u4c9t8bR (SUCCEEDED, build 1.0.4): keyword engineer, work arrangements remote, maxItems 10: 0 job(s).

The prefilled form (keyword engineer, up to 10 jobs, posted within any, repeat suppression on) is proven by run NiejZzFfDjNZazZmx: 10 jobs, each with its complete description. Select latest and keep the build number your run reports if you need to trace a result. The price is $0.20 per 1,000 jobs (a per-job result charge) with no start fee. A successful status alone does not prove complete coverage of the source, so inspect the dataset and RUN-SUMMARY together.

Job Atlas

Explore the Job Atlas job-data and matching Actors:

Product guide | Source and client examples | Setup skill | Setup guide | Job Atlas job-data tools


Independent tool. We built and run this Actor ourselves. Greenhouse, Stripe and Figma do not operate, sponsor or endorse it, and their names are used only to say which sites the data comes from.