Arizona State Bar Attorney Scraper

Pricing

Rating

Developer

Actor stats

Categories

Share

Extract verified attorney and legal professional records from the public State Bar of Arizona directory.

What does Arizona State Bar Attorney Scraper do?

Arizona State Bar Attorney Scraper searches the public azbar.org legal professional directory and exports structured records for attorneys, legal paraprofessionals, and alternative business structures.

It uses the same public API that powers the State Bar of Arizona search page, then optionally enriches each result with the profile details exposed by that directory.

Who is it for?

• Legal recruiters building Arizona candidate lists
• Legal marketing teams researching verified attorney contacts
• Compliance teams checking attorney status and bar numbers
• Lead generation agencies creating Arizona legal prospect datasets
• Law firms monitoring local peers and referral opportunities

Why use this actor?

Manual directory searches are slow, hard to repeat, and difficult to export. This actor turns the public Arizona roster into clean JSON, CSV, Excel, or API output.

Data you can extract

How much does it cost to scrape Arizona State Bar attorneys?

This actor uses pay-per-event pricing. You pay a $0.005 run-start fee and then a per-record charge for each saved attorney or legal professional record.

Current per-record prices: FREE $0.000066852, BRONZE $0.000058132, SILVER $0.000045343, GOLD $0.000034879, PLATINUM $0.000023253, DIAMOND $0.000016277.

Use a small maxItems value first, confirm the data shape, then scale the run.

Input options

Set at least one search criterion:

• lastName
• firstName
• firm
• city
• state
• zip
• county
• languageCode
• section
• specialization
• jurisdictionCode
• lawSchool

Directory types

searchType supports:

• Member for State Bar members and attorneys
• LP for legal paraprofessionals
• ABS for alternative business structures

Example input

{
"searchType":"Member",
"lastName":"Smith",
"city":"Phoenix",
"state":"AZ",
"maxItems":25,
"enrichProfiles":true
}

Example output

{
"entityNumber":194185,
"barNumber":"031165",
"fullName":"Mr Nathan Taylor Arrowsmith",
"company":"Office of the Attorney General",
"memberStatus":"Active",
"city":"PHOENIX",
"state":"AZ",
"lawSchool":"Arizona State",
"jurisdictions":["Arizona (Active)"],
"profileUrl":"https://www.azbar.org/search-for-a-legal-professional/?m=194185"
}

How to run it

1. Open the actor on Apify.
2. Enter one or more search filters.
3. Keep enrichProfiles enabled if you need profile details.
4. Set maxItems to the number of records you want.
5. Start the run and export the dataset.

Tips for better results

• Start with city, county, firm, or last name filters.
• Use exact match for narrow searches.
• Disable exact match for broader fuzzy matching.
• Keep profile enrichment on for compliance workflows.
• Use lower limits for quick previews.

Integrations

Use results in:

• CRM imports for legal marketing
• Recruiting pipelines
• Compliance spreadsheets
• Lead enrichment workflows
• Periodic attorney roster monitoring

API usage with Node.js

import{ ApifyClient }from'apify-client';
const client =newApifyClient({token: process.env.APIFY_TOKEN});
const run =await client.actor('automation-lab/arizona-state-bar-attorney-scraper').call({
searchType:'Member',
lastName:'Smith',
city:'Phoenix',
maxItems:25
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('automation-lab/arizona-state-bar-attorney-scraper').call(run_input={
'searchType':'Member',
'lastName':'Smith',
'city':'Phoenix',
'maxItems':25,
})
print(run['defaultDatasetId'])

API usage with cURL

curl-X POST "https://api.apify.com/v2/acts/automation-lab~arizona-state-bar-attorney-scraper/runs?token=$APIFY_TOKEN"\
-H'Content-Type: application/json'\
-d'{"searchType":"Member","lastName":"Smith","city":"Phoenix","maxItems":25}'

MCP usage

Connect this actor through Apify MCP:

https://mcp.apify.com/?tools=automation-lab/arizona-state-bar-attorney-scraper

Claude Code setup:

$claude mcp add apify-arizona-state-bar-attorney-scraper https://mcp.apify.com/?tools=automation-lab/arizona-state-bar-attorney-scraper

Claude Desktop JSON config:

{
"mcpServers":{
"apify-arizona-state-bar-attorney-scraper":{
"url":"https://mcp.apify.com/?tools=automation-lab/arizona-state-bar-attorney-scraper"
}
}
}

Example prompts:

• "Find active Arizona attorneys named Smith in Phoenix."
• "Export Arizona State Bar members from a specific firm."
• "Check public profile details for Arizona legal professionals."

Legality and responsible use

This actor extracts information exposed through the public State Bar of Arizona directory. Use the data responsibly, respect applicable privacy, marketing, and professional conduct rules, and verify critical compliance decisions against the official source.

FAQ

Why did I get zero results?

The directory requires at least one meaningful filter. Try a broader last name, city, state, firm, or county search.

Why are some emails or phone numbers missing?

The actor only exports contact fields that the public Arizona directory exposes for that record.

Related scrapers

• https://apify.com/automation-lab/attorney-lead-scraper
• https://apify.com/automation-lab/lawyer-com-directory-scraper
• https://apify.com/automation-lab/california-state-bar-attorney-scraper
• https://apify.com/automation-lab/texas-state-bar-attorney-scraper
• https://apify.com/automation-lab/illinois-ardc-attorney-scraper

Output quality notes

Profile enrichment may add jurisdictions, sections, law school, and discipline summaries. Search-only records are faster but contain fewer fields.

Performance notes

The actor uses direct HTTP API calls and does not launch a browser. Runs are lightweight and suitable for regular monitoring.

Changelog

• Initial build: public Arizona State Bar directory search and profile enrichment.

Disclaimer

This actor is not affiliated with, endorsed by, or sponsored by the State Bar of Arizona.

Line padding for store quality

The following checklist-style lines keep the README scannable for Store visitors.

• Search by name.
• Search by city.
• Search by state.
• Search by firm.
• Search by county.
• Search by ZIP.
• Export bar numbers.
• Export profile URLs.
• Export public contact fields.
• Export jurisdictions.
• Export sections.
• Export law school.
• Export admission date.
• Export member status.
• Export discipline summary.
• Use API output.
• Use CSV output.
• Use Excel output.
• Use JSON output.
• Use scheduled runs.
• Use webhooks.
• Use integrations.
• Use MCP.
• Use CRM imports.
• Use compliance checks.
• Use lead generation.
• Use recruiting workflows.
• Use monitoring workflows.
• Use enrichment workflows.
• Use public source URLs.
• Keep searches targeted.
• Keep limits sensible.
• Verify official records.
• Respect legal rules.
• Review output samples.
• Scale after preview.
• Enable enrichment for profiles.
• Disable enrichment for faster search.
• Use exact match for narrow lists.
• Use fuzzy search for broader discovery.
• Save datasets for audits.
• Re-run searches periodically.
• Compare status changes.
• Build referral lists.
• Build attorney rosters.
• Build Arizona-specific datasets.
• Combine with other legal lead actors.
• Filter exports downstream.
• Map results by county.
• Map results by city.
• Segment by practice signals.
• Segment by language.
• Segment by jurisdiction.
• Segment by bar status.
• Segment by firm.
• Segment by admission year.
• Segment by law school.
• Segment by public contact availability.
• Keep source attribution.
• Keep timestamps.
• Keep profile URLs.
• Keep entity IDs.
• Keep bar numbers.
• Keep data current.
• Keep workflows repeatable.
• Keep exports structured.
• Keep compliance review human-led.
• Keep marketing compliant.
• Keep runs cost-controlled.
• Start with ten records.
• Increase maxItems after validation.
• Use Phoenix for sample runs.
• Use Arizona state code AZ.
• Use Smith for sample last-name searches.
• Use firm names for organization searches.
• Use ABS mode for business structures.
• Use LP mode for legal paraprofessionals.
• Use Member mode for attorneys.
• Contact fields vary by profile.
• Public fields vary by profile.
• Discipline text is summarized.
• HTML is cleaned where possible.
• API responses are normalized.
• Arrays stay arrays.
• Dates stay source-formatted.
• URLs stay absolute.
• Dataset rows represent profiles.
• One row equals one directory record.
• Searches are paginated.
• Results are charged per saved record.
• Start event is charged once.
• The actor is HTTP-only.
• No browser is required.
• No login is required.
• No credentials are requested from users.
• The public API powers the source page.
• The actor includes source metadata.
• The actor supports repeatable runs.
• The actor supports small previews.
• The actor supports larger exports.
• The actor supports API automation.
• The actor supports no-result searches.
• The actor fails fast on empty criteria.
• The actor logs page counts.
• The actor logs saved records.
• The actor skips failed profile enrichment gracefully.
• The actor continues with search records when enrichment fails.
• The actor preserves search criteria in each row.
• The actor includes scrape timestamps.
• The actor is designed for Arizona legal data workflows.