Skip to content

Monster Scraper API: Job, Salary and Posting Data in One Call

Monster job pages are heavily bot-detected and paginated, so a naive scraper spends more time fighting blocks than reading listings.

OUTPUT FORMATSHTMLJSONMarkdown

A managed scraping API takes that layer off your hands: you supply a Monster URL, the service renders the page, rotates proxies and returns the content. The sections below explain what you get back, how the request controls change the result, and what each control costs in credits so you can size a plan before writing code.

What a Monster request returns

Each Monster job page can yield a consistent set of fields: job title, company, salary range, location, employment type, required skills, posting date and the application URL. You choose the output shape — raw HTML, structured JSON, or LLM-ready Markdown. Raw HTML is useful when you want to run your own parser; structured JSON is the fastest path to a database; Markdown is convenient when the next step is a language model summarising hiring trends or classifying job descriptions. The same page can also produce a full-page screenshot if you need a visual record alongside the data.

Three jobs people use Monster data for

Most Monster scraping falls into one of three patterns. First, listing extraction: pull titles, descriptions, locations, salaries and posting dates to build a current view of hiring demand. Second, trend analysis: read requirements across many listings to surface in-demand skills, emerging roles and industry shifts. Third, employer monitoring: follow a specific company's postings to see workforce growth, recruitment strategy and market movement. The same request shape serves all three; the difference is how you filter and aggregate the results afterwards.

Request controls and what they change

The default request returns the page without JavaScript execution. Four parameters change that behaviour and, in three cases, the credit cost. Use the table below as a decision aid: pick the smallest set of controls your target actually needs, because each premium control multiplies the per-request credit charge.

How credits are consumed

A base request starts at one credit. JavaScript rendering raises a successful request to five credits. Premium proxies cost ten credits with JavaScript rendering disabled, or twenty-five credits with it enabled. Credits are valid for one month and do not roll over, so a plan sized for a single month's workload is the right comparison point. Concurrency — the number of requests in flight at once — is a separate limit set per plan and is not the same as a per-target rate limit.

Worked example: one Monster job page to one record

Suppose you send a single Monster job URL with render_js=true and no premium proxy. The service returns the post-render HTML. From that page you can map the following fields into a record: title, company, salary range, location, employment type, skills required, posting date and application URL. If you instead request structured JSON, the same fields arrive already separated. If you request Markdown, the same content arrives as prose suitable for an LLM prompt. The credit cost of the request is the same in all three cases — five credits for a JavaScript-rendered request — because the cost is driven by the rendering and proxy controls, not by the output format.

Two different throttles, two different fixes

It helps to separate two failure modes that look similar. A concurrency throttle happens when you send more simultaneous requests than your plan allows; the fix is to queue work or move to a higher plan. A target-side throttle happens when Monster itself slows or blocks aggressive patterns; the fix is to space requests out, vary sessions, or enable stealth_proxy. Treating a target-side block as a plan limit leads to unnecessary upgrades; treating a plan limit as a target block leads to wasted retries.

Getting from zero to a first request

Account setup is the first step: registering provides an API key and a starting credit balance for testing. The size of that starting balance is a commercial detail to confirm with the provider before you rely on it for a large test run. From there, install the client for your stack — Python, Node, Go, PHP or Ruby — or skip the SDK entirely and send a GET request with the target URL and your key. The dashboard includes a request builder that lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL, which is useful for validating a request before wiring it into a pipeline. Code samples exist for Python, Node.js, Ruby, PHP, Go and cURL, and a request builder covers the no-code path.

Choosing a plan size

Plan size is driven by two numbers: monthly credits and concurrent requests. A JavaScript-rendered request costs five credits, so a plan with a given monthly credit allowance supports roughly one-fifth of that number in rendered requests per month before premium proxies are involved. For example, a plan with 1,000,000 credits would cover about 200,000 rendered requests at five credits each; premium proxies at ten or twenty-five credits per request reduce that count accordingly. Concurrency matters when you need to run many requests at once rather than spread them over the month. The plan table below lists the exact credit and concurrency figures for each tier so you can match them to your expected volume.

Data handling and compliance

Data handling obligations depend on what your workflow collects and where it operates. If your workflow pulls personal data from Monster listings — recruiter contact details, applicant information — you are responsible for the legal basis and retention rules that apply in your jurisdiction. Before building, confirm with the provider what data the service stores, for how long, and under which processing terms.

Request controls and their credit impact
ControlWhat it doesCredit effect
render_jsRuns the page in a headless browser and returns post-render HTML5 credits per successful request
stealth_proxyRoutes through premium proxies to reduce blocking10 credits without JS rendering; 25 credits with JS rendering
country_codeRoutes through a residential IP in the chosen countryNo additional credit charge stated
ai_extract_rulesNatural-language extraction rules for structured outputNo additional credit charge stated
ScreenshotCaptures a full-page screenshotNo additional credit charge stated

Credit figures are the platform's published per-request charges at the time of capture; confirm current pricing before committing to a plan.

Frequently asked questions

How do I start scraping Monster?

Create an account, copy your API key, and send a GET request with the Monster URL you want. The service renders the page, rotates proxies and returns the data. The starting credit balance available for testing is a commercial detail to confirm with the provider before you rely on it for a large test run.

Will I get blocked when scraping Monster?

Blocking risk depends on the target and the request pattern. If Monster responds aggressively to a particular pattern, enable stealth_proxy on the request to raise the protection level. Confirm with the provider which proxy infrastructure is used before relying on it for a high-volume workflow.

Can I scrape Monster without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. You can also drive the API from an n8n workflow if you prefer a visual automation tool.

How do I handle JavaScript when scraping Monster?

Set render_js=true on the request. The page is loaded in a headless browser, the JavaScript executes server-side, and you receive the post-render HTML.

Can I scrape Monster from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when Monster shows different listings or content depending on the visitor's location.

What's the rate limit for scraping Monster?

Limits are expressed as concurrency per plan rather than a per-target rate limit. If Monster itself throttles aggressive patterns, space requests out or use multiple sessions.