Skip to content

Martindale Attorney Listings Scraper API

Martindale listing pages are JavaScript-driven and guarded by bot detection.

OUTPUT FORMATSHTMLJSONMarkdown

This API takes a Martindale URL, renders the page through a headless browser, rotates residential proxies, and returns either rendered HTML or parsed JSON. Your client stays a thin HTTP call — no proxy pool, no browser fleet, no anti-bot layer to maintain.

What the API handles for you

Three jobs run on every request: JavaScript rendering so listing content actually appears, proxy rotation so requests are not tied to one IP, and bot-detection handling so the response is a page rather than a challenge screen. You supply the target URL and your API key; the service supplies the browser and network layer.

Three workflows this fits

Most Martindale collection programs fall into one of three shapes. Pick the one that matches your downstream use before you choose request options.

  • Attorney tracking. Collect listings by practice area and state, including names, firms, peer-review ratings and contact verification. Common downstream uses are legal-marketing intent signals and competitor tracking.
  • Firm profiles. Collect a firm's partner roster, practice areas, office locations and peer-review ratings.
  • Location mapping. Roll up attorney office addresses by state and city. Teams use this for legal-services lead targeting and to compare competitor footprints.

All three return the same core field set; the difference is which pages you queue and how you key the results.

Fields you can expect back

Attorney name, firm, practice areas, state, peer-review rating, contact details and verified office locations are the documented field set. The JSON path returns business listings, ratings, contact info, categories and locations, so you do not parse HTML yourself.

If a field you need is not in that list, it is still reachable through extract_rules (CSS selectors mapped to your own field names) or ai_extract_rules (a natural-language spec). Anything that renders on the public page can be targeted; anything behind a login is out of scope.

Request options and what each one unlocks

The base call is a GET with your API key and a martindale.com URL. Add options only when the page needs them — each one changes the credit cost.

  • render_js — executes page JavaScript. Needed for listing content that appears after load. Costs 5 credits per successful request.
  • stealth_proxy — routes through stealth infrastructure for pages that challenge ordinary requests. Costs 75 credits per request.
  • premium_proxy — premium proxy pool; 10 credits without JS rendering, 25 with it.
  • country_code — geotargets the request; the platform advertises 200+ countries and territories (40+ on classic proxies).
  • extract_rules — CSS (or XPath) selectors mapped to field names; returns parsed JSON.
  • ai_extract_rules — natural-language extraction spec; also returns parsed JSON.
  • Screenshots — capture a full-page image alongside the data.

Start with the cheapest option that returns the fields you need, then escalate only on failure.

Estimating monthly credits

Credits are consumed per successful request and the multiplier depends on the options you enable. A worked example using the documented rates:

  • 10,000 plain requests = 10,000 credits.
  • 10,000 requests with render_js = 50,000 credits.
  • 10,000 requests with premium_proxy + JS = 250,000 credits.
  • 10,000 requests with stealth_proxy = 750,000 credits.

Compare that against the plan tiers below before committing. If your Martindale pages render without JS, you avoid the 5-credit multiplier entirely; if they need stealth, budget roughly 15× the plain-request cost.

Telling failures apart

Three different problems look similar in a pipeline and need different fixes:

  1. Blocked request. You get a challenge page or non-200 instead of listing content. Fix: add stealth_proxy, or check that render_js is on.
  2. Rendered but empty. The page loads but the fields you want are missing. Fix: the selector or AI spec is wrong, not the network. Inspect the rendered HTML and adjust extract_rules.
  3. Parsed but wrong shape. JSON comes back but keys do not match your schema. Fix: rename fields in extract_rules, or tighten the ai_extract_rules description.

Log the raw HTML alongside the parsed output so you can tell case 1 from case 2 after the fact.

Plan tiers

Standard plans cover most teams; enterprise tiers add concurrency and volume. All prices exclude VAT. Credits are valid for one month and do not roll over; requests start at 1 credit each. The full plan matrix — credits, concurrency, rendering, proxies, geotargeting, screenshots, support and team management per tier — is delivered in the protected pricing module and should be read row by row rather than summarized.

Setup path

  1. Create an account — you get an API key and 1,000 free credits, no card required.
  2. Install an SDK (Python, Node.js, Go, PHP, Ruby, Java) or use plain cURL.
  3. Send a GET with your key and a Martindale URL.
  4. Add render_js, stealth_proxy, country_code, extract_rules or ai_extract_rules only as the page requires.

Test in the dashboard request builder first, then paste the generated snippet into your codebase. Working samples exist for each supported language.

Martindale scraper plan comparison
PlanPrice / moAPI creditsConcurrent requestsJS renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$1975,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$991,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Prices exclude VAT. Credits are valid for one month and do not roll over. Requests start at 1 credit each. Plan names, prices and limits are the operator's published figures and should be re-checked against the current pricing page before purchase.

Frequently asked questions

Do I need an account to scrape Martindale?

No external Martindale account is required. You sign up for an API key (1,000 free credits, no card), send the URL, and the service handles rendering and proxies.

Is scraping Martindale legal?

Public-facing pages can usually be collected, but review the target site's terms of service before deploying and avoid post-login content. This is general guidance, not legal advice for your jurisdiction or use case.

What data can I extract from Martindale?

Whatever appears on the public page. To get structured JSON back, map CSS selectors through extract_rules, or describe the fields you want in plain language with ai_extract_rules. The documented field set covers attorney name, firm, practice areas, state, peer-review rating, contact details and office locations.

How do I get structured JSON from Martindale?

Two routes: give extract_rules a set of CSS selectors keyed to your field names, or give ai_extract_rules a plain-language description of the fields. Either way the response arrives already parsed as JSON.

Which programming languages can I use to scrape Martindale?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.

How much does it cost to scrape Martindale?

1,000 free credits on signup, no card required. Paid plans start at $19/month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, 75 for stealth_proxy.