StepStone Scraper for Job, Salary and Skills Data
StepStone job pages are rendered, paginated and defended against automated traffic.
A managed scraping API removes that operational burden: you send a StepStone URL, the service renders it in a real headless browser, rotates residential proxies, and returns rendered HTML or structured JSON for you to parse. This page explains what fields you can collect, which request inputs control rendering, proxies and geo-targeting, how credits are consumed, and which plan tier fits a given workload.
What you can collect from public StepStone job pages
A single StepStone job page exposes a predictable set of fields. The API returns the rendered page, and you can either parse it yourself or ask the service to return structured JSON.
- Job title
- Employer name
- Location
- Salary range (where the listing discloses one)
- Posting date
- Full job description
- Required skills
- Application URL
These fields support three common workflows: building a talent-intelligence feed of open roles, aggregating disclosed salary ranges by role, location and seniority, and tracking how quickly employers fill or repost roles. The salary signal is only as good as what employers choose to publish — many German listings omit a range, so treat aggregates as partial coverage rather than a market average.
How a StepStone request works
The workflow is four steps.
- Create an account. You receive an API key and a starting credit balance to test with.
- Install a client SDK or use raw HTTP. Python, Node.js, Go, PHP, Ruby and Java clients are documented, plus cURL examples.
- Send a GET request with your API key and a StepStone URL on stepstone.de. The service renders JavaScript, rotates residential proxies, and returns rendered HTML.
- Add advanced parameters only when the page needs them: render_js for JavaScript execution, stealth_proxy for aggressive anti-bot responses, country_code for geo-targeted routing, and ai_extract_rules for natural-language extraction into structured JSON.
If you prefer not to write code, the dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in any of the supported languages.
Field and control map
Use this map to decide which request input produces which output, and which inputs are optional.
| Goal | Request input | What you get back |
|---|---|---|
| Fetch a job page | target StepStone URL + API key | Rendered HTML of the page |
| Execute page JavaScript | render_js=true | Post-render HTML with dynamic content present |
| Reduce blocking risk | stealth_proxy enabled | Request routed through stealth proxy handling |
| Route through a specific country | country_code | Request sent via a residential IP in that country |
| Extract structured fields without selectors | ai_extract_rules | Structured JSON matching your natural-language spec |
| Extract specific elements | extract_rules with CSS or XPath | Structured JSON of matched elements |
| Capture a visual record | screenshot option | Full-page screenshot |
| Get LLM-ready text | Markdown output | Clean Markdown of the page |
A practical ordering: start with the plain URL and render_js=true. Add stealth_proxy only if you see challenge pages. Add country_code only when content differs by geography. Add ai_extract_rules or extract_rules when you want JSON rather than HTML.
Worked example: one job URL to structured JSON
Suppose you have a single public StepStone job listing URL and you want title, employer, location, salary range, posting date, description and required skills as JSON.
- Paste the URL into the dashboard request builder.
- Enable render_js so the page executes its JavaScript before capture.
- Add an ai_extract_rules specification naming the fields you want.
- Copy the generated snippet into your codebase and run it.
- Inspect the returned JSON. If a field is missing, check whether the listing actually discloses it — salary range in particular is often absent.
For a batch, loop over a list of job URLs with the same parameters. Keep the field specification in one place so all records share a schema.
Blocking versus rendering gaps
Two failure modes look similar but need different fixes.
- Blocking: you receive a challenge page, a CAPTCHA, or an empty response with an anti-bot signature. Fix: enable stealth_proxy, which routes the request through stealth proxy handling.
- Rendering gap: the HTML arrives but the job fields are absent because the page had not finished executing JavaScript. Fix: confirm render_js=true and, if the page loads content after user interaction, use a JavaScript scenario to click, scroll or wait.
Geo-variance is a third case: the page renders but shows different content than expected. Fix: set country_code to the country whose content you need.
Credits, concurrency and plan tiers
Credits are consumed per request, and the cost depends on which features you enable. The base rate is one credit per request. Enabling JavaScript rendering costs five credits per successful request. Enabling premium proxies costs ten credits without JS rendering or twenty-five with it. Credits are valid for one month and do not roll over. Concurrency is the number of requests you can send at the same time.
The plan table below lists every tier with its monthly price, credit allowance, concurrency limit and feature inclusions. Prices are exclusive of VAT. Use the table to match a workload to a tier: estimate your monthly request volume, multiply by the per-request credit cost for the features you need, and choose the smallest tier whose credit allowance covers that total with headroom for retries.
Plan comparison
The following table reproduces the published plan tiers with their prices, credit allowances, concurrency limits and feature inclusions. All prices are exclusive of VAT.
Compliance and data handling
The service does not collect or store personal data from scraped sites unless the user explicitly requests it. When you scrape StepStone, you are responsible for complying with StepStone's terms of service and applicable data-protection law. Salary and employer data are business information; personal data in job descriptions or application contacts should be handled under your own GDPR or CCPA obligations.
When a managed API is the right choice
Use a managed API when:
- You need to collect StepStone job pages at scale and do not want to operate a headless-browser fleet.
- You want proxy rotation and anti-bot handling without maintaining your own proxy pool.
- You want structured JSON without writing and maintaining CSS or XPath selectors.
- You want geo-targeted requests without provisioning country-specific infrastructure.
Consider a self-hosted approach when your volume is very small, your target pages are static, or you need full control over the browser environment for reasons the API does not cover.
| Plan | Price | API credits | Concurrent requests | JavaScript rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
All prices are exclusive of VAT. Credits are valid for one month and do not roll over. Requests start at 1 credit each; JavaScript rendering costs 5 credits per successful request; premium proxies cost 10 or 25 credits depending on whether JS rendering is enabled.
Frequently asked questions
What data can I extract from StepStone?
Any content that appears on the rendered public page is available. You have two extraction routes: extract_rules, where you supply CSS selectors to target specific elements, or ai_extract_rules, where you describe the fields you want in natural language and the service resolves them. Either route returns structured JSON.
How do I get started scraping StepStone?
Sign up, grab your API key, and send a GET request with the target URL. We render the page, rotate proxies, and return the data. 1,000 free credits to test.
Will I get blocked when scraping StepStone?
Requests are routed through rotating residential proxies and executed in a genuine headless browser, so they carry the profile of ordinary visitor traffic rather than a bot. If a particular target tightens its defenses, switch on stealth_proxy for that request to add the stronger handling path.
Can I scrape StepStone without writing code?
Yes. Our dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.
How do I handle JavaScript when scraping StepStone?
Set render_js=true on the request. The page is then loaded in a real headless browser and its JavaScript runs on the server side, so the HTML you receive already reflects the post-render state of the page.
Can I scrape StepStone from a specific country?
Yes. Setting country_code on the request sends it out through a residential IP located in that country. This matters when the page you receive changes depending on where the visitor appears to be.