Justia Lawyer Scraper — Attorney Leads

Extract attorney profiles from the Justia Lawyer Directory with practice areas, contact details, bar admissions, education, ratings, and reviews. Filter by practice area and geographic location, or supply direct Justia listing/profile URLs.

Use Cases

• Legal lead generation — build lists of licensed attorneys by practice area and city/county for sales outreach
• Attorney prospecting — find lawyers with verified phone, email, and website for CRM enrichment
• Legal-tech data enrichment — feed attorney directories, comparison tools, and matching platforms
• Market research — analyze attorney distribution by practice area, geography, rating, and law school
• Recruitment — source attorneys by specialization for law firm hiring or expert-network platforms

Input

The actor supports three input modes (combine as needed):

Field	Type	Default	Description
startUrls	array	[]	Direct Justia lawyer listing or profile URLs (must contain justia.com/lawyers)
practiceArea	enum	family-law	Practice-area slug (e.g., criminal-law, personal-injury, bankruptcy)
location	string	california/los-angeles	Geographic slug in state/city or state/county format
maxResults	integer	50	Maximum lawyer records to extract (1–10,000)
scrapeProfileDetails	boolean	true	Visit each lawyer's profile page to enrich with bar admissions, law school, and additional contact info
customProxyUrl	string	""	Optional premium residential proxy URL (recommended for high-volume runs)

URL formats accepted in startUrls

• Practice area: https://www.justia.com/lawyers/family-law
• Location: https://www.justia.com/lawyers/california/los-angeles
• Combined: https://www.justia.com/lawyers/family-law/california/los-angeles
• County: https://www.justia.com/lawyers/california/los-angeles-county
• Individual profile: any URL matching justia.com/lawyers/<lawyer-slug>

Example inputs

{
    "practiceArea": "family-law",
    "location": "california/los-angeles",
    "maxResults": 100,
    "scrapeProfileDetails": true
}

{
    "startUrls": [{ "url": "https://www.justia.com/lawyers/criminal-law/illinois/chicago" }],
    "maxResults": 200
}

{
    "practiceArea": "personal-injury",
    "location": "texas/houston",
    "maxResults": 50,
    "scrapeProfileDetails": false,
    "customProxyUrl": "http://user:pass@proxy.decodo.com:8000"
}

Output

Each dataset item is a lawyer record with the following fields:

Field	Type	Example
lawyer_name	string | null	"Jane A. Roe"
firm_name	string | null	"Roe & Partners LLP"
practice_areas	string[] | null	["Family Law","Divorce"]
city	string | null	"Los Angeles"
state	string | null	"CA"
phone	string | null	"(213) 555-0100"
email	string | null	"jane@roelaw.com"
website	string | null	"https://roelaw.com"
address	string | null	"500 Market St, Los Angeles, CA 90013"
rating	number | null	4.8
reviews_count	number | null	23
bar_admissions	string[] | null	["State Bar of California"]
law_school	string | null	"UCLA School of Law"
profile_url	string | null	"https://www.justia.com/lawyers/jane-roe-12345"
scraped_at	string (ISO 8601)	"2026-07-05T12:00:00.000Z"
source_url	string	"https://www.justia.com/lawyers/family-law/california/los-angeles"

Pricing

This actor uses Pay-Per-Event billing:

Event	Price	Trigger
Actor Start	$0.00005	Once per run
Lawyer Record	$0.025	Per attorney profile successfully extracted

Example: 100 lawyer records = $2.50 + $0.00005 start = ~$2.50.

Usage-based billing (compute + proxy passthrough) is also enabled for heavy users.

API & Integration

Run the actor via API:

curl -X POST "https://api.apify.com/v2/acts/muhammadafzal~justia-lawyer-directory-scraper/runs?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"practiceArea":"family-law","location":"california/los-angeles","maxResults":50}'

Export results:

$curl "https://api.apify.com/v2/datasets/DATASET_ID/items?token=YOUR_API_TOKEN&format=json"

Integrate with Zapier, Make, n8n, Airbyte, LangChain, or any tool that consumes Apify datasets.

Reliability & Anti-Blocking

• Playwright browser with anti-detection launch args (real TLS/UA fingerprint)
• Session pool (20 sessions, max 8 uses each) for IP rotation
• Consent cookie pre-injection to bypass GDPR popups
• Randomized delays (1–3s) and viewport sizes per request
• 3-layer extraction: JSON-LD structured data → DOM parsing with multi-selector fallback → profile-page enrichment
• Datacenter proxy by default; falls back to your custom residential proxy via customProxyUrl for blocked endpoints
• Pagination auto-follow (a[rel="next"], ?page=N)

Notes

• Justia's directory contains hundreds of thousands of attorney profiles across all US states. Large extraction jobs (10,000+ records) should set scrapeProfileDetails: false for speed, then re-enrich a subset.
• Practice-area slugs follow Justia's URL convention (kebab-case). Common slugs are pre-listed in the input schema dropdown; custom slugs can be typed manually.
• The actor is MCP-ready: AI agents (Claude, GPT, Cursor) can call it with a single practiceArea + location pair and receive structured JSON.

Legal & Compliance

This actor scrapes publicly available attorney profile data from the Justia Lawyer Directory. Ensure your use complies with Justia's Terms of Service and applicable data-protection laws (GDPR, CCPA) when handling contact information. Output is intended for B2B lead generation and research purposes.

What is Justia Lawyer Scraper?

Justia Lawyer Scraper turns the target data into structured, reusable results on Apify. Use it when you need repeatable collection for sales teams, agencies, recruiters, market researchers, and data-enrichment workflows without maintaining a custom scraper or one-off integration. Run it manually, schedule recurring jobs, call it through the Apify API, or connect it to an AI agent through the Apify MCP server.

The Actor stores results in an Apify dataset, where they can be previewed and exported as JSON, CSV, Excel, XML, or RSS. Availability and completeness depend on the source, supplied inputs, public visibility, authentication requirements, and upstream rate limits.

Use cases for Justia Lawyer Scraper

• Build structured datasets for research, reporting, enrichment, or monitoring.
• Automate repetitive collection with schedules, webhooks, and API calls.
• Feed clean records into spreadsheets, databases, CRMs, BI tools, AI agents, or RAG pipelines.
• Track changes over time by running the same validated input on a schedule.
• Replace fragile manual copy-and-paste work with a reproducible Apify workflow.

How to use Justia Lawyer Scraper

1. Open the Actor input page and choose a focused, valid target.
2. Set a conservative result limit for the first run.
3. Start the Actor and inspect the dataset for coverage and field availability.
4. Export the results or connect the dataset to your downstream system.
5. Scale gradually and use scheduling, pagination, or proxies when supported.

Important input options

• startUrls — Use this field when the user provides specific Justia lawyer listing or profile URLs. Each URL must contain 'justia.com/lawyers'. Accepted formats include practice-area pages (justia.com/law
• practiceArea — Use this field when the user describes a legal practice area in words. Justia uses kebab-case slugs (lowercase, hyphen-separated). Common values: personal-injury, medical-malpractice, crimin
• location — Use this field when the user describes a geographic area. Format is lowercase state/city or state/county slug using hyphens for spaces. Examples: 'california/los-angeles', 'california/los-an
• maxResults — Maximum number of lawyer records to extract before stopping. Caps both listing pages and profile enrichments. Defaults to 50. Increase for bulk extraction jobs; decrease for quick tests. Exa
• scrapeProfileDetails — When true (default), the actor visits each lawyer's profile page to enrich the record with bar admissions, law school, and any contact info not present on the listing page. When false, only
• customProxyUrl — Optional premium residential proxy URL (e.g., http://user:pass@provider.decodo.com:8000). Justia blocks datacenter IPs aggressively on some endpoints; providing a premium residential proxy (

API and automation example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/justia-lawyer-directory-scraper').call({
  // Add the same input fields you use in the Apify Console.
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Related Apify Actors

Use these dedicated tools when a neighboring data source or workflow is a better match:

• Instagram Followers & Following Scraper — With Cookies
• Facebook Ads Library Scraper — Meta Ad Intelligence Tool
• Leads Finder Pro - B2B Leads with Emails [Apollo Alternative]
• Yellow Pages US Scraper — Business Leads & Reviews
• Yellow Pages Australia Scraper — Business Leads & Reviews
• OpenTable Restaurants, Ratings & Reviews Scraper
• Etsy Scraper Pro — Products, Prices, Reviews & Shop Data
• Email Validator — Syntax, MX & Risk Checks
• Shopify Store Scraper - Products, Reviews & Emails
• 🔧 USA Plumbers Scraper — Leads with Phone, Address & Website

Frequently asked questions

How many results can I scrape with Justia Lawyer Scraper?

The practical total depends on the source, input limits, pagination, available records, run timeout, and upstream restrictions. Start with a small run, verify the output, and increase the limit gradually.

Can I integrate Justia Lawyer Scraper with other apps?

Yes. Use Apify integrations, webhooks, schedules, dataset exports, Make, Zapier, Google Sheets, cloud storage, or your own application.

Can I use Justia Lawyer Scraper with the Apify API?

Yes. Start runs with the Apify REST API or an official Apify client, then retrieve records from the run's default dataset. Keep your API token in a secret or environment variable.

Can I use Justia Lawyer Scraper through an MCP Server?

Yes. The Apify MCP server can expose the Actor to compatible AI clients and agents. Review the input and expected cost before allowing an autonomous workflow to run it at scale.

Do I need proxies?

It depends on the source and volume. Use the default configuration first. For larger or geographically sensitive jobs, select an appropriate proxy configuration only when the Actor supports it.

Is it legal to scrape this data?

Scraping rules vary by source, jurisdiction, data type, and intended use. Collect only data you are authorized to access, respect applicable terms and privacy laws, and avoid restricted or personal data misuse. This documentation is not legal advice.

Your feedback

If a field is missing, a source layout has changed, or you need a supported use case documented, open an issue on the Actor page with a reproducible input and run ID.