StepStone Job Listing
Pricing
from $4.05 / 1,000 results
StepStone Job Listing
Scrape StepStone job listings by keyword, country, and location with structured job details, salary signals, company data, and source URLs.
Pricing
from $4.05 / 1,000 results
Rating
5.0
(1)
Developer
TrueFetch
Maintained by CommunityActor stats
2
Bookmarked
12
Total users
4
Monthly active users
21 hours ago
Last modified
Categories
Share
Affiliate disclosure: TrueFetch may earn a commission if you sign up through an Apify link on this page, at no extra cost to you.
Collect public StepStone vacancies from four European country sites and receive a consistent 41-field Dataset for regional recruiting, compensation research, and hiring-market analysis.
- Four country-specific StepStone markets: Germany, Austria, Belgium, and the Netherlands.
- Country-wide or city-focused searches without a hidden location default.
- 41 normalized fields for roles, pay, employers, applications, and available public contact signals.
- Public Store snapshot: 12 users and a 5.0 rating from one review on July 21, 2026; deployed Store content may represent an older release.
Run a one-result test · View API
With max_results: 1, one published FREE-tier result costs $0.01450: $0.01000 for Actor Start plus $0.00450 for the result.
What does StepStone Job Listing do?
StepStone Job Listing is a TrueFetch Apify Actor and StepStone jobs API for searching public vacancies on the German, Austrian, Belgian, and Dutch StepStone sites. Give it a keyword, select one supported country, and optionally name a city or region. The Actor opens the matching regional market, collects accessible listing details, and writes normalized records to the default Apify Dataset.
The output is intended for workflows that should not depend on four separate site layouts. One schema covers source links, job text, employment and work-mode signals, disclosed compensation, employer attributes, application destinations, and public company contact information when it can be found. Missing source data stays empty instead of being inferred.
This Actor is independent of StepStone and is not an official StepStone API. It does not log in, access applicant information, submit applications, or guarantee that every public vacancy will expose salary, work-mode, company, or contact details. Search supply and page availability can differ among the four regional sites.
How do I run StepStone Job Listing?
- Open StepStone Job Listing on Apify.
- Enter the required
keyword,country, andmax_resultsvalues. - Add a
locationonly when the search should be narrower than the selected country. - Start with one result, examine its source and populated fields, and then raise the cap.
Every example below follows one scenario: retrieve one Supply Chain Manager vacancy around Vienna, Austria, and convert usable salary figures to EUR.
{"keyword": "Supply Chain Manager","country": "Austria","max_results": 1,"location": "Vienna","currency": "EUR"}
max_results is a ceiling on jobs published by this run, not a promise that StepStone will expose that many matching and accessible vacancies. Omit location for a country-level request; the Actor does not silently replace the omission with a particular city.
What data does StepStone Job Listing return?
The default Dataset schema contains 41 nullable fields. A field is populated only when the source listing or subsequent public company enrichment supplies usable evidence.
| Field group | Fields |
|---|---|
| Processing | processor, processed_at |
| Source and application | platform, platform_url, official_url, easy_apply |
| Vacancy details | title, description, job_type, job_level, job_function, listing_type, skills, experience_range |
| Place and work mode | location, is_remote, work_from_home |
| Timing and demand | posted_date, valid_through, applicant_count, vacancy_count |
| Compensation | salary_minimum, salary_maximum, salary_currency, salary_period |
| Employer | company_name, company_type, company_founded, company_industry, company_url, company_website, company_logo, company_addresses, company_revenue, company_description, company_rating, employee_count, review_count |
| Public contacts | emails, phones, social_links |
This shortened illustrative item uses the Vienna scenario; actual values depend on the live listing:
{"platform": "StepStone","platform_url": "https://www.stepstone.at/stellenangebote--example","official_url": null,"title": "Supply Chain Manager","company_name": "Example Logistics GmbH","location": {"raw": "Wien","locality": "Vienna","country": "Austria","country_code": "AT"},"job_type": "Full-time","salary_currency": "EUR","processor": "https://apify.com/truefetch/stepstone-job-listing","processed_at": "2026-07-21T12:00:00.000Z"}
Consult the live Output schema for complete types and examples. Keep nullable fields nullable in downstream databases; an absent salary or external application URL is not a zero value.
What inputs can I configure?
The current local input schema exposes 5 inputs, of which 3 are required.
| Input | Required | Effect |
|---|---|---|
keyword | Yes | Job title, skill, employer, or phrase sent to StepStone search. |
country | Yes | Chooses Germany, Austria, Belgium, or the Netherlands and its regional domain. |
max_results | Yes | Maximum published jobs, from 1 to 10,000. |
location | No | City or region used to narrow the selected country; omit for country-wide search. |
currency | No | Target currency for conversion when usable numeric salary data exists. |
There are no public recency, remote-only, distance, salary-range, or employment-type inputs for this Actor. Do not add such keys to automation and assume they will filter StepStone. The currency value is a post-collection transformation request; it does not change which vacancies the source returns. Review the Input schema before generating requests programmatically.
What platforms and markets does StepStone Job Listing cover?
This is a single-platform Actor for StepStone with four explicit regional markets:
| Country input | Regional site | Typical source language |
|---|---|---|
| Germany | stepstone.de | German |
| Austria | stepstone.at | German |
| Belgium | stepstone.be | English and locally published listing content |
| Netherlands | stepstone.nl | Dutch |
The Actor selects the site from country; it does not search all four domains in one run. Local names and accents are normalized for the regional URL where needed. A supplied location is associated with the chosen market, while empty, country-level, or broad values result in a country-wide search path.
Coverage does not include the United Kingdom, Switzerland, Denmark, or other StepStone-branded markets in the current schema. Use separate runs to compare countries and retain processed_at because regional inventories and public page structures change over time.
Why use StepStone Job Listing?
| Capability | Workflow value |
|---|---|
| Regional domain selection | Send a search to the correct German, Austrian, Belgian, or Dutch site from one stable input contract. |
| Normalized European vacancy records | Store comparable fields even when source pages use different languages or layouts. |
| Country-wide and local modes | Build national snapshots or city-level watchlists without an imposed city default. |
| Salary conversion option | Standardize disclosed numeric pay for cross-market analysis while retaining source availability limits. |
| Source traceability | Keep the StepStone listing URL and a separate employer application URL when one is exposed. |
| Apify operation | Run through Console, schedules, webhooks, API clients, or an MCP-enabled assistant. |
The practical trade-off is source variability. Normalization makes records easier to consume, but it cannot make sparse public listings complete or turn a result cap into guaranteed inventory.
Who is StepStone Job Listing for?
| User | Example outcome |
|---|---|
| European recruiting teams | Monitor named roles by country or hiring city. |
| Labor-market researchers | Compare vacancy supply across selected DACH and Benelux markets. |
| Compensation analysts | Review disclosed salary bands and convert usable figures to a common currency. |
| Job-product developers | Add source-attributed StepStone records to a search or alert feature. |
| Employer-intelligence teams | Track public hiring activity and available company context over time. |
It is not a candidate database, resume scraper, application bot, or substitute for legal review. Apply appropriate retention, attribution, and regional data-handling policies to the results you store.
How can I use StepStone Job Listing through the API or MCP?
The stable Actor ID is truefetch/stepstone-job-listing. This synchronous request runs the same one-result Vienna scenario and returns Dataset items in the response:
curl -X POST \"https://api.apify.com/v2/acts/truefetch~stepstone-job-listing/run-sync-get-dataset-items?token=$APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"keyword": "Supply Chain Manager","country": "Austria","max_results": 1,"location": "Vienna","currency": "EUR"}'
For MCP, use Apify's Streamable HTTP endpoint and limit the exposed tools to this Actor:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=truefetch/stepstone-job-listing","headers": {"Authorization": "Bearer <APIFY_TOKEN>"}}}}
Then ask the connected client to run the same Vienna input. The API page also shows asynchronous endpoints, SDK examples, and OpenAPI details. Keep tokens in secrets or environment variables, never in committed files.
How much does StepStone Job Listing cost?
Pay-per-event billing applies: one Actor Start event for a run and one result event for each normalized job written to the default Dataset.
| Apify tier | Actor Start | Per result | Per 1,000 results |
|---|---|---|---|
| FREE | $0.01000 | $0.00450 | $4.50 |
| BRONZE | $0.01000 | $0.00435 | $4.35 |
| SILVER | $0.01000 | $0.00420 | $4.20 |
| GOLD / PLATINUM / DIAMOND | $0.01000 | $0.00405 | $4.05 |
At the FREE tier, the recommended one-result run costs $0.01450 when one item is published. Actor Start remains chargeable when a run produces no result. Use the Pricing tab to confirm current public amounts before scheduling volume.
How does StepStone Job Listing compare with alternatives?
| Decision | StepStone Job Listing | Multi-board Job Search | Manual regional browsing |
|---|---|---|---|
| Source scope | Four specified StepStone sites | Multiple compatible job boards | Whichever site a person opens |
| Data shape | One 41-field Dataset | Shared cross-source schema | Pages and copied notes |
| Repeatability | Saved input, API, MCP, and schedules | Similar automation with broader sources | Manual repetition |
| Strongest fit | StepStone-specific DACH/Benelux monitoring | Broader source discovery | Occasional individual review |
| Main constraint | Five-input search contract and variable public fields | Less source-specific focus | No dependable structured export |
Choose this Actor when StepStone attribution and its four supported European markets matter. Choose Job Search when one request should cover several job boards. Manual review remains appropriate for a small number of final candidate listings or application decisions.
What are the limits and troubleshooting steps?
| Symptom or limit | Likely reason | Safe next step |
|---|---|---|
Fewer jobs than max_results | The cap exceeds live, relevant, accessible inventory. | Broaden the keyword or omit the location. |
| No result for a city | The local spelling or source inventory may differ. | Try the regional spelling, then test the country without location. |
| The wrong regional language appears | Listing text comes from the selected country site and publisher. | Use country as the authoritative market selector. |
| Salary fields are empty | Many vacancies do not disclose numeric pay. | Treat salary columns as nullable and compare only populated records. |
| Converted salary is absent | Conversion needs usable source amount, currency, and exchange-rate data. | Inspect the original salary fields and source page. |
official_url is null | The page may not expose a separate external application destination. | Retain platform_url as the source record. |
| A repeated run changes | Listings close, update, move, or become inaccessible. | Store timestamps and compare runs as snapshots, not static truth. |
For a reproducible support case, use one country, a simple keyword, and max_results: 1. Share the Apify run URL through Issues, but never include your token.
Frequently asked questions
Is location required?
No. Omitting it requests the selected national StepStone market. Add a city or region only for a narrower search.
Can one run search all four countries?
No. country selects one regional domain per run. Create four explicit runs if your workflow needs a comparable four-market snapshot.
Does the Actor support remote-only or posting-age filters?
No public inputs currently provide those request filters. Remote and date values may appear in output when StepStone publishes them, but they cannot be required through this input schema.
Does currency filter the search?
No. It asks the Actor to convert usable numeric salaries after collection. It does not alter ranking, location, or vacancy availability.
Why are some of the 41 fields empty?
The schema unifies possible data across listings. StepStone pages do not consistently expose every salary, company, application, work-mode, and contact attribute.
Are public contact fields guaranteed?
No. Email addresses, phone numbers, and social links are emitted only when public company pages provide them and enrichment succeeds.
Can I schedule regional vacancy monitoring?
Yes. Validate one-result runs for each country first, schedule the inputs independently, and deduplicate using source URLs plus timestamps because postings may change or reappear.
Related TrueFetch Actors
- Indeed Job Listing — use it for an Indeed-specific search with broader country coverage and source filters.
- LinkedIn Job Listing — use it when LinkedIn recency, remote, employment-type, and radius filters are important.
- Job Search — use it for one normalized workflow across several compatible job boards.
Support and last updated
- Run StepStone Job Listing
- View API options
- Report an issue
- Join the TrueFetch Telegram group
- Contact support on Telegram
Last updated: July 21, 2026. Local schema, metadata, pricing, and read-only runtime evidence were verified independently from the older deployed Store content; public Store statistics above are dated observations.
Run one result first, verify that the chosen regional site and populated fields match your use case, and only then increase max_results.