Contractor License Verifier
Pricing
Pay per usage
Contractor License Verifier
Under maintenanceVerify contractor licenses across CA, TX, FL, AZ, NV, CO, and WA. Writes normalized status, class, business, qualifier, bond, workers comp, complaint, suspension, source, and recommendation results to the default dataset.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
jts
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
What this Actor does
Verify contractor licenses across CA, TX, FL, AZ, NV, CO, and WA. Writes normalized status, class, business, qualifier, bond, workers comp, complaint, suspension, source, and recommendation results to the default dataset.
Input example
{"state": "CA","licenseNumber": "1045782","name": "Example Builders","status": "any"}
Input fields
Provide one or more license lookups. Each lookup is { state, licenseNumber } or { state, name, licenseClass?, status? }.
licenses(array, user input): Up to 100 lookup objects.state(string, user input): Optional single lookup state: CA, TX, FL, AZ, NV, CO, or WA.licenseNumber(string, user input): Optional single lookup license number.name(string, user input): Optional single lookup name.status(string, user input): Use active to return only active licenses, or any to return every matched status.apiBaseUrl(string, optional override): Override of the upstream API base URL. Defaults to runtime.baseUrl from service.json.
Output dataset
One dataset item per lookup result or inline error.
input: Original lookup input.ok: Whether the lookup succeeded.state: State searched.licenseNumber: Matched license number.status: Normalized license status.recommendation: allow, review, or block.riskScore: 0-100 review score.result: Full API response envelope.
Developer notes
Set CONTRACTOR_LICENSE_VERIFIER_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API.
Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json.
For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.
Run locally
$apify run
Deploy
$apify push