Connecticut Nursing License Lookup Scraper

Search the official Connecticut eLicense data by holder name, credential type, status, city, or license number. The Actor exports verification-ready nursing credential records from Connecticut Open Data, including identity, credential code, status and reason, dates, location, responsible department, and source provenance.

The source is updated daily and contains active and inactive records. No Connecticut eLicense account, browser, or proxy configuration is required.

What does this Actor do?

Connecticut Nursing License Lookup Scraper turns repeatable public-license checks into structured dataset rows.

It can:

• look up a Connecticut nurse by partial holder name;
• verify a full credential code or numeric credential number;
• filter RN, LPN, APRN, nurse-midwife, temporary, and nursing-home-administrator credentials;
• select any of the ten published raw nursing statuses;
• filter expiration dates by inclusive calendar-day windows;
• reconcile every submitted search using an uncharged completion summary;
• narrow a credential category by city;
• run up to 25 searches in one task;
• deduplicate credentials found by overlapping searches;
• stop at a user-controlled maximum result count.

Every result includes links to the official eLicense verification page and Connecticut's source dataset.

Who is it for?

Healthcare employers

Check public credential status and expiration dates during onboarding or periodic workforce reviews.

Staffing and recruiting teams

Export nursing credentials into a spreadsheet, ATS enrichment step, or internal verification queue.

Compliance teams

Schedule the same input and compare datasets across runs to identify public status or expiration changes.

Data and integration teams

Use typed JSON instead of manually copying records from an interactive lookup page.

This Actor provides public source data. It does not make hiring, credentialing, disciplinary, or legal decisions for you.

Supported nursing credentials

The Actor deliberately limits source results to professional nursing categories:

• Registered Nurse
• Registered Nurse - Temporary
• Licensed Practical Nurse
• Licensed Practical Nurse - Temporary
• Advanced Practice Registered Nurse
• Licensed Nurse Midwife
• Nursing Home Administrator

This whitelist prevents similarly named but unrelated nursery permits, facilities, and service-agency records from entering the output.

What data is extracted?

Field	Meaning
holderName	Public credential holder name
fullCredentialCode	Complete Connecticut credential code
credentialNumber	Number without the type prefix
credentialDescription	Nursing credential category
department	Always Connecticut Department of Public Health
status	Current public status
statusReason	Public reason associated with the status
isActive	Source active flag, not permission to practice; inspect statusReason
issueDate	Original issue date when available
effectiveDate	Current effective date
expirationDate	Current expiration date
address, city, state, zip	Public source location fields
recordRefreshedOn	Date Connecticut refreshed the record
verificationUrl	Official interactive verification page
sourceDatasetUrl	Official daily source dataset
query	Filters that produced the record
scrapedAt	Actor extraction timestamp

Source fields can be absent. Nullable output fields are returned as null rather than invented values.

How to run your first lookup

1. Open the Actor in Apify Console.
2. Add one or more objects to License searches.
3. Enter a name, license number, credential type, status, or city.
4. Set Maximum results.
5. Click Start.
6. Open the Dataset tab to inspect, download, or integrate the records.

A search object combines its filters with AND logic. Separate objects are independent searches and their results are merged and deduplicated.

Input parameters

queries

An array of 1–25 search objects. Each object must contain at least one filter.

Filter	Behavior
name	Case-insensitive holder-name fragment, 2–100 characters
licenseNumber	Exact credential number (digits-only leading zeros ignored, string-safe) or exact full code; original submitted value retained
credentialType	One supported nursing credential category
status	Exact raw status: ACTIVE, INACTIVE, PENDING, ACTIVE IN RENEWAL, ACTIVE MILITARY, APPROVED, DENIED, EXPIRED APPLICATION, LICENSEE NOT RENEWING, RETIRED
city	Case-insensitive city fragment, 2–100 characters
expirationDateFrom	Optional inclusive lower bound, real YYYY-MM-DD date
expirationDateTo	Optional inclusive upper bound, real YYYY-MM-DD date

ACTIVE does not include ACTIVE IN RENEWAL. The source can mark suspended or retired credentials active: isActive=true is never a legal eligibility verdict. Read statusReason and verify with the authority.

Digits-only numbers such as 061935 match the stored numeric number 61935; 10.061935 remains an exact full-code lookup. Numeric numbers can match multiple nursing categories; use credentialType to disambiguate. Nonnumeric codes retain existing exact matching.

Expiration bounds combine with all other filters using AND. Either bound alone is valid. Missing expiry is excluded when a bound is supplied. Dates use the source's floating calendar days, not your local timezone; the upper bound is implemented as less than the next day's midnight. Source date strings are preserved. Invalid dates and reversed ranges are rejected (supported range: 0001-01-01 through 9999-12-30).

maxItems

Maximum unique credentials saved across all searches, after deduplication. The range is 1–10,000 and the default is 100. Later queries may be skipped once this global cap or the charge budget is reached; consult SUMMARY, rather than interpreting skipped searches as no match.

Example:

{
  "queries": [
    {
      "name": "Smith",
      "credentialType": "Registered Nurse",
      "status": "ACTIVE"
    }
  ],
  "maxItems": 10
}

Batch workforce verification example

Use exact full credential codes to verify several nursing roles in one run:

{
  "queries": [
    { "licenseNumber": "10.061935" },
    { "licenseNumber": "11.036142" },
    { "licenseNumber": "12.004821" }
  ],
  "maxItems": 3
}

Each saved credential retains its first matching query. Repeated queries do not create or charge duplicate rows. For complete reconciliation, read SUMMARY from the run's key-value store or the Output tab.

Expiration-window example

{
  "queries": [{ "credentialType": "Registered Nurse", "status": "ACTIVE IN RENEWAL", "expirationDateFrom": "2027-08-01", "expirationDateTo": "2027-08-31" }],
  "maxItems": 100
}

Per-search completion summary

The uncharged SUMMARY JSON object has schemaVersion: 1, run status, maxItems, and totals uniqueSaved, observedSourceRows, deduplicated. Its queries array contains one entry for each submitted search: zero-based index, original filters, attempted, the same observed/saved/deduplicated counts, outcome, and completeness.

• no-match, matched, matched-but-duplicate: source pagination exhausted; completeness: exhausted.
• cap-reached, budget-reached: not proven exhausted; completeness: unknown. A full page at the cap does not prove complete extraction.
• unattempted-cap, unattempted-budget, unattempted-failure: no lookup was performed; completeness: not-attempted.
• failed: failed lookup; completeness: unknown. Earlier confirmed output remains accounted for. storageWriteUncertain: true identifies an interrupted storage/charge operation; confirmed counts exclude that uncertain batch, so inspect the dataset and charge logs.

observedSourceRows counts inspected pages, not total source matches. No extra counting requests are made. Progress is saved after each query and best-effort on failure. Dataset rows remain credentials only; summaries and empty/duplicate searches have no item charge.

Output example

A current output row has this shape:

{
  "credentialId": "1000123",
  "holderName": "Jordan A SAMPLE",
  "holderType": "INDIVIDUAL",
  "fullCredentialCode": "10.012345",
  "credentialTypeCode": "10",
  "credentialNumber": "12345",
  "credentialDescription": "Registered Nurse",
  "department": "Connecticut Department of Public Health",
  "status": "ACTIVE",
  "statusReason": "CURRENT",
  "isActive": true,
  "issueDate": "2024-01-15T00:00:00.000",
  "effectiveDate": "2026-01-01T00:00:00.000",
  "expirationDate": "2027-01-31T00:00:00.000",
  "city": "Hartford",
  "state": "CT",
  "recordRefreshedOn": "2026-08-20T00:00:00.000",
  "verificationUrl": "https://www.elicense.ct.gov/Lookup/LicenseLookup.aspx",
  "sourceDatasetUrl": "https://data.ct.gov/Business/State-Licenses-and-Credentials/ngch-56tr",
  "query": { "credentialType": "Registered Nurse", "status": "ACTIVE" },
  "scrapedAt": "2026-08-25T20:00:00.000Z"
}

The example identity and code are anonymized. Actual datasets contain public source values.

How much does it cost to verify Connecticut nursing licenses?

Pay-per-event pricing includes a $0.00005 start fee and one item charge for each saved credential.

Tier	Price per saved credential
FREE	$0.003864
BRONZE	$0.00336
SILVER	$0.0026208
GOLD	$0.002016
PLATINUM	$0.001344
DIAMOND	$0.0009408

At the BRONZE rate, 10 saved credentials cost about $0.03365 including the start fee, 100 cost about $0.33605, and 1,000 cost about $3.36005. Apify selects the applicable tier for the account.

No proxy charge is required by this Actor. Empty searches incur the start event but no item events.

Recurring monitoring and integrations

The Actor returns current snapshots rather than a built-in change log. For monitoring:

1. save a stable input as an Apify Task;
2. schedule it daily, weekly, or monthly;
3. export each run's dataset;
4. compare credentialId, status, statusReason, expirationDate, and recordRefreshedOn in your system.

Useful integrations include Google Sheets, webhooks, Make, Zapier, cloud storage, databases, and internal compliance pipelines.

Run with the Apify API

Replace YOUR_TOKEN with an Apify API token.

cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~connecticut-nursing-license-lookup/runs?token=YOUR_TOKEN&waitForFinish=120" \
  -H "Content-Type: application/json" \
  -d '{"queries":[{"licenseNumber":"10.061935"}],"maxItems":1}'

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/connecticut-nursing-license-lookup').call({
  queries: [{ credentialType: 'Advanced Practice Registered Nurse', status: 'ACTIVE', city: 'Hartford' }],
  maxItems: 25,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("automation-lab/connecticut-nursing-license-lookup").call(
    run_input={"queries": [{"name": "Smith", "credentialType": "Registered Nurse"}], "maxItems": 10}
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

Use through MCP

Claude Code setup

Add the Actor to Claude Code:

claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/connecticut-nursing-license-lookup"

Claude Desktop, Cursor, and VS Code setup

Claude Desktop, Cursor, and VS Code can use this MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/connecticut-nursing-license-lookup"
    }
  }
}

Example prompts:

• “Verify Connecticut registered nurse code 10.061935 and return its current status and expiry.”
• “Find active Connecticut APRN credentials in Hartford, limited to 25 results.”
• “Run these three nursing credential numbers and format status changes for a spreadsheet.”

Accuracy, freshness, and limitations

• Records come from Connecticut's official State Licenses and Credentials dataset.
• Connecticut describes the dataset as updated daily; this is not a real-time guarantee.
• The Actor does not expose private records, accounts, login-only data, or non-public discipline documents.
• A missing record is not proof that a person has never held a credential.
• Name searches are substring searches and can match multiple people.
• Address fields are public source fields and may be absent or outdated.
• The Actor does not decide whether a credential satisfies a role's legal requirements.
• Upstream outages or rate limits cause a clear failed run after bounded retries.

For consequential decisions, follow the verificationUrl and confirm the record with the responsible authority.

Failure diagnostics and privacy

Failed operations send sanitized diagnostic input, exceptions and Actor/build/run IDs to our private GlitchTip service for repair. Secret fields and URL query strings are removed; reports are retained for 30 days. Telemetry configuration is protected and is not a public input option.

No AI model is used and no data is sent to an AI provider. Public search filters are sent to Connecticut Open Data; run-owned datasets, original search filters in SUMMARY, and logs are stored in your Apify account. The Actor creates no cross-run cache and sets no custom storage retention: manage retention and deletion of run storage in Apify Console and your downstream integrations. Keep exports private and retain them only as long as necessary. For Actor questions or defects, open an issue on the Actor's Apify Issues tab.

Legality and responsible use

License and credential records can contain personal information. Use them for a legitimate verification purpose, minimize retained fields, secure exports, and follow applicable employment, privacy, discrimination, and records laws.

Do not use this Actor to harass individuals, construct sensitive profiles, or make automated adverse decisions without appropriate review. Apify users are responsible for their inputs, storage, integrations, and legal basis.

Troubleshooting

Why did my run return no results?

Check the spelling and remove one filter at a time. Filters inside one query object are combined, so an incorrect city or status can exclude an otherwise matching credential. Try the numeric portion and full credential code separately only when needed.

Why was my input rejected?

Every query needs at least one supported filter. Names and cities need at least two characters. License numbers accept letters, numbers, periods, and hyphens. Credential types and statuses must use a listed value.

Why did the run fail with an upstream error?

Connecticut Open Data may be unavailable or rate limited. Each request/body has a 15-second deadline and at most three attempts, with bounded exponential backoff, for transient transport failures, HTTP 429 or 5xx. Permanent 4xx and malformed successful payloads fail without blind retries. Errors identify query index and page, not holder identities. A failed run can contain partial output; inspect SUMMARY. Retry later rather than raising concurrency or adding proxies.

Why are two searches returning one row?

The Actor deduplicates overlapping searches by Connecticut credential identifier. The first matching query remains in the output row.

Related Automation Lab Actors

• Texas Pharmacy License Lookup for Texas pharmacist, pharmacy, intern, and technician verification.
• Virginia Real Estate License Lookup for Virginia real-estate regulant exports.
• Pennsylvania Attorney Registry Lookup for Pennsylvania attorney registration due diligence.

Choose this Actor when the job is specifically Connecticut public nursing credential verification.

FAQ

Does it require an eLicense login?

No. It uses Connecticut's anonymous official Open Data API.

Does it support inactive credentials?

Yes. Set status to INACTIVE, or omit status to include every public status matching the other filters.

Can I search only by credential type?

Yes. Set one supported credentialType and control the export size with maxItems.

Can it search several license numbers at once?

Yes. Add one query object per number, up to 25 searches per run.

Does it publish monitoring alerts?

No. Schedule an Apify Task and compare datasets in your chosen integration.

Are issue and expiration dates always present?

No. The Actor preserves missing source fields as null.

Is this an official Connecticut government service?

No. It is an independent Apify Actor that reads official public Connecticut datasets and preserves source links for verification.