Licensee Search Florida Scraper

Search the official Florida Department of Financial Services (DFS) public licensee service and export adjuster records as structured JSON. This licensee search Florida Actor supports name, Florida license number, NPN, email, firm, location, status, resident-status, and appointment-based filters.

Each enriched result can include public licensee identity, business and mailing contact data, National Producer Number, continuing-education status, valid and invalid licenses, active and inactive company appointments, and a regulator source link.

What does this Actor do?

The Actor automates the public workflow at licenseesearch.fldfs.com.

It can:

• search the official Florida DFS public service;
• limit results to individual adjusters, adjusting firms, or both categories;
• search by person name, firm, email, Florida license number, or NPN;
• filter by business city, state, or Florida DFS county code;
• select valid, invalid, or both license-status groups;
• find licensees reported without a qualifying appointment;
• filter by the official continuing-education hours-not-met flag;
• paginate beyond the first 20 search results;
• enrich each search row with the official detail record;
• save normalized results to the default Apify dataset.

The Actor does not infer license status from third-party data. It preserves the status, license, appointment, and continuing-education values shown by Florida DFS at retrieval time.

Who is it for?

Insurance compliance teams can verify adjuster licensing and appointments during onboarding or periodic reviews.

Carriers and adjusting firms can prepare review lists by city, resident status, or missing qualifying appointment.

Credentialing teams can look up a specific Florida license number or NPN and retain the official record URL.

Data engineers can schedule recurring runs and send normalized results to a warehouse, spreadsheet, webhook, or comparison pipeline.

Investigators and due-diligence analysts can inspect public identity, contact, license, and appointment context without manually opening each detail page.

Why use this Actor?

The public Florida DFS interface is designed for interactive searches. The Actor turns that interface into a repeatable dataset while keeping requests bounded and session-aware.

Key benefits include:

• official regulator source data;
• adjuster-specific category filtering;
• automatic search pagination;
• optional detail-page enrichment;
• stable field names for downstream workflows;
• direct links back to every source record;
• configurable result limits for low-cost checks or larger reviews.

No proxy is enabled or billed by this Actor. It uses the public SSR search with a coherent cookie and CSRF session.

What Florida DFS data is extracted?

Field	Meaning
licenseeId	Stable identifier used by the Florida DFS detail URL
licenseNumber	Florida license number
name	Public individual or adjusting-firm name
businessAddress	Public business street address
mailingAddress	Public mailing address from the detail page
city, state, postalCode	Parsed business location
county	County shown by Florida DFS
email, phone	Public contact values shown by Florida DFS
npn	National Producer Number
ceDueDate	Continuing-education due date as displayed
continuingEducationStatus	Continuing-education status
ceHoursRequired, ceHoursCompleted	CE hour counts when available
validLicenses	Valid license types, issue dates, and qualifying-appointment flags
invalidLicenses	Invalid license types, issue dates, and statuses
activeAppointments	Active company appointment rows
inactiveAppointments	Inactive company appointment rows
hasQualifyingAppointment	Whether a valid license has a qualifying appointment
sourceUrl	Official Florida DFS detail-record URL
retrievedAt	ISO timestamp for the retrieval

Fields can be null or empty when Florida DFS does not publish that value for a record. Search-only runs (fetchDetails: false) intentionally leave detail-only fields empty.

Getting started

1. Open the Actor input page in Apify Console.
2. Enter at least one person, firm, license, NPN, email, city, state, or county filter, or enable an appointment/CE eligibility filter.
3. Keep licenseCategory set to adjuster, or select adjusting firms/both.
4. Choose the desired license status.
5. Leave detail enrichment enabled for licenses, appointments, NPN, CE, and contact fields.
6. Set a bounded maxItems value.
7. Click Start.
8. Open the Dataset tab to inspect, download, or integrate the results.

A safe first run is:

{
  "lastName": "Smith",
  "licenseCategory": "adjuster",
  "licenseStatus": "both",
  "fetchDetails": true,
  "maxItems": 10
}

Input parameters

Input	Type	Default	Description
firstName	string	—	Individual first name, at least 3 characters
lastName	string	Smith prefill	Individual last name, at least 3 characters
middleName	string	—	Individual middle name, at least 3 characters
firmName	string	—	Adjusting-firm name contains filter
email	string	—	Public email contains filter
licenseNumber	string	—	Exact Florida license number, up to 7 characters
npn	string	—	Exact NPN, up to 9 digits
city	string	—	Business city, at least 3 characters
state	string	—	Two-letter business state code
countyCode	string	—	Two-digit county code used by Florida DFS
residentStatus	enum	—	resident or nonResident
licenseStatus	enum	both	valid, invalid, or both
licenseCategory	enum	adjuster	adjuster, adjustingFirm, or both
onlyNoQualifyingAppointment	boolean	false	Use the official missing-appointment search filter
onlyCeHoursNotMet	boolean	false	Official DFS hours-not-met filter; not an overdue/noncompliance finding
fetchDetails	boolean	true	Fetch NPN, contact, CE, licenses, and appointments
maxItems	integer	10	Save 1–10,000 unique licensees

Florida DFS requires at least three characters for its person-name, firm-name, email, and city text filters. The Actor validates those constraints before making source requests.

Search examples

Verify one Florida adjuster license

{
  "licenseNumber": "W108368",
  "licenseCategory": "adjuster",
  "licenseStatus": "both",
  "fetchDetails": true,
  "maxItems": 1
}

Search adjusting firms

{
  "firmName": "Claims",
  "licenseCategory": "adjustingFirm",
  "licenseStatus": "valid",
  "fetchDetails": true,
  "maxItems": 25
}

Build an appointment review list

{
  "city": "Miami",
  "state": "FL",
  "licenseCategory": "adjuster",
  "licenseStatus": "valid",
  "onlyNoQualifyingAppointment": true,
  "fetchDetails": true,
  "maxItems": 100
}

Review CE hours not met

{
  "onlyCeHoursNotMet": true,
  "fetchDetails": true,
  "maxItems": 10
}

The optional onlyCeHoursNotMet flag maps directly to Florida DFS CEHrsNotMetFilter. It combines with other filters, or can be the sole search criterion. Omitting it or setting it to false preserves existing searches. CE hours not met may include records still In Progress before their due date: it is not proof of overdue status, a missed deadline, or legal noncompliance. The official filter can also return records whose detail page omits CE statistics; these fields remain null rather than being invented or locally re-filtered. Use the detail fields and official record for review, not an inferred compliance score.

Florida DFS county codes

Keep countyCode a two-character string, including leading zeros; these are DFS codes, not FIPS or alphabetical county numbers. For Miami-Dade (displayed as Dade by DFS), use "01"; Broward is "10", Hillsborough "03". The text input preserves existing API compatibility rather than restricting values to an enum. Unknown two-digit codes remain source-interpreted. Official dropdown mapping observed 2026-10-03:

County	Code	County	Code
Alachua	11	Baker	52
Bay	23	Bradford	45
Brevard	19	Broward	10
Calhoun	58	Charlotte	53
Citrus	47	Clay	48
Collier	64	Columbia	29
Dade (Miami-Dade)	01	Desoto	34
Dixie	54	Duval	02
Escambia	09	Flagler	61
Franklin	59	Gadsden	21
Gilchrist	55	Glades	60
Gulf	66	Hamilton	56
Hardee	30	Hendry	49
Hernando	40	Highlands	27
Hillsborough	03	Holmes	51
Indian River	32	Jackson	25
Jefferson	46	Lafayette	62
Lake	12	Lee	18
Leon	13	Levy	39
Liberty	67	Madison	35
Manatee	15	Marion	14
Martin	42	Monroe	38
Nassau	41	Okaloosa	43
Okeechobee	57	Orange	07
Osceola	26	Out of state	00
Palm Beach	06	Pasco	28
Pinellas	04	Polk	05
Putnam	22	Santa Rosa	33
Sarasota	16	Seminole	17
St. Johns	20	St. Lucie	24
Sumter	44	Suwannee	31
Taylor	37	Union	63
Volusia	08	Wakulla	65
Walton	36	Washington	50

Output example

A current enriched result has this shape (public contact values are replaced here):

{
  "licenseeId": "1265542",
  "licenseNumber": "W108368",
  "name": "SMITH ALLMAN, SHEA N",
  "businessAddress": "2153 WHITENERS FARM RD LINCOLNTON, NC 28092",
  "mailingAddress": "2153 WHITENERS FARM RD LINCOLNTON, NC 28092",
  "city": "LINCOLNTON",
  "state": "NC",
  "postalCode": "28092",
  "county": null,
  "email": "public-contact@example.org",
  "phone": "(000) 000-0000",
  "npn": "16618181",
  "ceDueDate": "10/31/2026",
  "continuingEducationStatus": "Compliant",
  "ceHoursRequired": 0,
  "ceHoursCompleted": 0,
  "validLicenses": [
    {
      "type": "NON-RES ADJUSTER - ALL LINES (0720)",
      "issueDate": "8/17/2012",
      "status": "VALID",
      "qualifyingAppointment": true
    }
  ],
  "invalidLicenses": [],
  "activeAppointments": [],
  "inactiveAppointments": [],
  "hasQualifyingAppointment": true,
  "sourceUrl": "https://licenseesearch.fldfs.com/Licensee/1265542",
  "retrievedAt": "2026-08-17T06:00:00.000Z"
}

The default dataset supports JSON, JSONL, CSV, Excel, XML, and RSS exports through Apify.

How much does it cost to verify Florida adjuster licenses?

This Actor uses pay-per-event pricing:

• one start event is charged when a run begins;
• one item event is charged for each unique licensee saved;
• detail enrichment is included in the item event and is not charged separately;
• empty, duplicate, or failed records are not charged as items.

The one-time start fee is $0.005. Current item prices are:

Tier	Price per saved licensee
FREE	$0.00874
BRONZE	$0.0076
SILVER	$0.005928
GOLD	$0.00456
PLATINUM	$0.00304
DIAMOND	$0.002128

At BRONZE, a run saving 1 record costs $0.0126, 10 records cost $0.081, and 100 records cost $0.765. Detail enrichment is included. Runtime and public-source availability can affect the final number of records, so set maxItems to the number your workflow actually needs.

Scheduling compliance checks

Use an Apify schedule to run the same filtered search daily, weekly, or monthly. Store each run's dataset ID, then compare stable keys such as licenseeId and licenseNumber.

Useful change signals include:

• a valid license moving to the invalid list;
• hasQualifyingAppointment changing;
• an active appointment appearing or disappearing;
• a CE status or due date changing;
• a public business location changing.

The Actor returns current public source state. It does not maintain historical snapshots or send change alerts by itself; Apify schedules, webhooks, and your downstream system provide that workflow.

Export and integration patterns

Spreadsheet review: export the dataset as CSV or Excel for a one-time credential review.

Data warehouse: call the dataset API after each scheduled run and upsert by licenseeId.

Onboarding automation: run an exact license-number or NPN lookup from an internal workflow and retain sourceUrl as evidence.

Appointment monitoring: filter for no qualifying appointment, then compare subsequent datasets.

Webhook pipeline: attach an Apify run-succeeded webhook and send the dataset URL to Make, Zapier, n8n, or your own service.

Use the Actor through the API

Replace APIFY_TOKEN with your token.

cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~florida-adjuster-license-search/runs?token=APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"licenseNumber":"W108368","maxItems":1}'

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/florida-adjuster-license-search').call({
  lastName: 'Smith',
  licenseCategory: 'adjuster',
  fetchDetails: true,
  maxItems: 10,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/florida-adjuster-license-search').call(
    run_input={
        'city': 'Miami',
        'state': 'FL',
        'onlyNoQualifyingAppointment': True,
        'maxItems': 25,
    }
)
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

Use with Apify MCP

Add the Actor to Claude Code:

claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/florida-adjuster-license-search"

Claude Desktop, Cursor, and VS Code setup

Use this equivalent JSON configuration in Claude Desktop, Cursor, or VS Code:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/florida-adjuster-license-search"
    }
  }
}

Example prompts:

• “Verify Florida adjuster license W108368 and summarize its current licenses and appointments.”
• “Find up to 50 valid adjusters in Miami that have no qualifying appointment and return a review table.”
• “Search Florida DFS for adjusters named Smith and save the official source URLs.”

Performance and cost tips

• Use an exact license number or NPN when verifying one person.
• Keep maxItems close to the number you need.
• Set fetchDetails: false only when search-row identity, address, and email are sufficient.
• Detail enrichment runs with bounded concurrency to avoid overwhelming the public service.
• Search pages contain 20 records; the Actor requests additional pages only as needed.
• Avoid broad state-only searches with a large limit unless your workflow requires them.

Limits and source behavior

Florida DFS controls the public service and can change HTML, session rules, filters, or availability without notice.

The Actor:

• does not bypass authentication or CAPTCHA;
• does not use private credentials;
• does not guarantee that every public record contains email, phone, county, NPN, CE, or appointment values;
• does not claim that a public record is a legal certification;
• does not include enforcement orders from separate Florida systems;
• does not provide historical changes unless you schedule and retain multiple runs;
• stops with a failed run when the source returns an unrecognized error page, missing/malformed results, inconsistent totals, or pagination with no new IDs instead of silently returning empty or truncated success;
• retries transient network/408/429/5xx failures at most four attempts; deterministic HTTP errors fail immediately;
• merges session cookie updates and allows one fresh-session restart for recognized expired-session responses. Other challenges/errors fail visibly; no browser or proxy fallback is enabled.

For a naturally empty valid search, the run succeeds with zero item charges.

Data handling and support

This Actor uses no AI/model provider. Florida DFS is the public data source; no paid data API or proxy is enabled. Apify hosts the run, dataset and logs under its standard terms; charges are only the documented start and saved-item events. Cookies/CSRF state are held in memory for the run, not shared between runs. Public professional identity and contact data are intentionally included in your dataset, not printed as response dumps in logs. Dataset/log retention follows your Apify account settings; delete run storage through Apify when no longer needed. The Actor does not maintain its own cross-run history or cache. Contact the Actor's Issues tab for support; do not put secrets in issue text.

Diagnostic privacy

Failed operations send sanitized diagnostic input, exceptions, and Actor/build/run IDs to our private GlitchTip service for repair. Secret fields and URL queries are removed; reports are retained for 30 days. Normal retries, valid empty results, and successful recoveries are not reported as terminal errors.

Responsible use and legality

The Actor accesses public professional-license information. Public availability does not remove your obligations.

Use the data for lawful credential verification, compliance, due diligence, and analysis. Follow applicable privacy, employment, insurance, consumer-reporting, records-retention, and contractual rules. Do not use public contact information for harassment, unlawful discrimination, or unsolicited messaging that violates applicable law.

Confirm consequential decisions with Florida DFS or the appropriate regulator. sourceUrl is included so reviewers can inspect the current official record.

Troubleshooting

The Actor says a text filter is too short.

Florida DFS requires at least three characters for name, firm, email, and city text filters. Use a longer value or an exact license/NPN filter.

The run returns no records.

Check the selected category and status. A license may be in the adjusting-firm category rather than individual adjuster, or may only appear when status is both.

Detail fields are empty.

Confirm fetchDetails is true. Some records genuinely omit public contact, CE, or appointment values.

The run fails with a Florida DFS response error.

Inspect the run log and retry later if the public service is temporarily unavailable. Do not repeatedly launch identical runs during a source outage.

The result limit is reached.

Increase maxItems within the 10,000-item input maximum or narrow the filters for a more targeted compliance list.

Related Automation Lab Actors

• Texas Insurance License Lookup — official Texas insurance agent, adjuster, agency, appointment, and relationship datasets.
• Florida DBPR License Verification Scraper — Florida DBPR professional-license records outside the DFS insurance workflow.

Choose this Actor specifically for Florida DFS insurance adjusters and adjusting firms.

FAQ

Is this the official Florida DFS website?

No. This is an independent Apify Actor that retrieves public records from the official source and links every result back to it.

Can it search agents or other insurance categories?

This product intentionally supports the DFS Adjuster and Adjusting Firm categories. It does not claim broad coverage of every license category.

Does it include active and inactive appointments?

Yes, when fetchDetails is enabled and Florida DFS publishes appointment rows for the licensee.

Does it verify continuing education?

It returns the public CE status, due date, and hour counts shown on the detail record. Treat those values as source data, not independent certification.

Can it monitor changes automatically?

Schedule recurring Actor runs and compare retained datasets. The Actor retrieves current records but does not itself maintain history or send alerts.

Does it need a proxy?

No proxy is enabled by default. The current implementation uses direct public HTTP requests with a coherent DFS session.

Are detail pages charged separately?

No. A saved enriched licensee is covered by one item event; there is no separate detail event.