Virginia DPOR Professional License Scraper

Search the official Virginia Department of Professional and Occupational Regulation (DPOR) License Lookup and return structured professional and occupational license records.

Extracted fields

licenseNumber, name, dbaNames, address, licenseType, board, rank, expirationDate, sourceUrl, sourceSearchUrl, scrapedAt, and warnings.

Input

Use searchQueries for text such as a name, business, address, or license type. Use licenseNumbers for exact lookups. The Actor deduplicates license numbers and stops at maxResults (default 25, maximum 1000).

{
  "searchQueries": ["architect"],
  "licenseNumbers": [],
  "maxResults": 25,
  "includeDetails": true,
  "requestDelayMs": 750
}

Output and pricing

Each dataset item is one license record. Pay per event is $0.003 per delivered record, plus the configured $0.00005 actor-start event. For example, 25 records cost about $0.07505 before any applicable platform usage charges. No result event is charged for empty, rejected, or blocked searches.

Reliability and limitations

The Actor uses the public DPOR License Lookup site and preserves an HTTP session for its form-backed search and detail pages. DPOR may limit broad searches to 200 visible records. If DPOR returns a CAPTCHA, access-denied page, rate limit, or other challenge, the Actor reports a blocked outcome and never fabricates records. This is a read-only scraper; it does not access authenticated online services or request license certifications.

DPOR states that online lookup data may be delayed or incomplete and is not the agency's physical public-record collection. Use the official source link in each record for verification and comply with DPOR terms, applicable law, and privacy requirements.

Source

Official source: https://dporweb.dpor.virginia.gov/LicenseLookup/

Use cases

• Supply structured public data to AI, RAG, enrichment, or evaluation workflows.
• Schedule repeatable collection and export results to downstream workflows.
• Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
• Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
• Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

Run Virginia DPOR Professional License Scraper with the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/virginia-dpor-professional-license-scraper').call({
  "searchQueries": [
    "architect"
  ],
  "licenseNumbers": [],
  "maxResults": 25,
  "includeDetails": true,
  "requestDelayMs": 750
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

Support

When reporting a problem, include the Actor run ID, a redacted input, the expected result, and a small public example URL when applicable. Do not post API tokens, cookies, credentials, or personal data in an issue.

Frequently asked questions

Can I schedule Virginia DPOR Professional License Scraper?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

Can an AI agent call this Actor?

Yes. Add muhammadafzal/virginia-dpor-professional-license-scraper through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.

Recommended workflow

1. Define the smallest useful scope. Choose a representative public URL, query, identifier, or filter and keep the first result limit low.
2. Run and inspect. Check the run log, dataset item count, field coverage, source URLs, and live event or usage charges.
3. Validate downstream assumptions. Confirm nullable fields, deduplication keys, timestamps, and any locale-specific formats before importing records into another system.
4. Scale gradually. Increase limits or scheduling frequency only after the small run behaves as expected. Use Apify's maximum-cost and timeout controls to bound large jobs.
5. Monitor changes. Keep a small known-good input as a canary. If the source layout or API changes, compare the new dataset with a previously validated run and report the run ID when requesting support.

For recurring workflows, store the exact Actor input with your pipeline configuration. This makes runs reproducible and helps distinguish a source-data change from an input change.