🏛️ Delaware Corporations Search Scraper — Live Delaware Division of Corporations entity-registry lookup

The Delaware Corporations Search Scraper queries the Delaware Division of Corporations' public entity-search system (the canonical registry for Delaware corporations, LLCs, LPs and statutory trusts). Pass entity names and/or Delaware file numbers; receive the registry's matching entities as clean JSON — file number and entity name — live from the official source. Useful for KYC, due-diligence, fund formation and confirming that a Delaware entity exists under the name or file number you were given.

What you get

One record per matching Delaware entity, with exactly these fields:

Field	Meaning
entity_name	Registered entity name, exactly as spelled in the registry
file_number	Delaware file number (the registry's canonical identifier)
search_query	The entity name or file number you submitted that produced this record
search_type	entity_name or file_number
state_of_formation	Always DE
source	icis.corp.delaware.gov

The actor returns the registry's search-results listing. It does not return entity status, formation/incorporation date, registered agent or agent address, entity type, last annual-report year, stock details, foreign-jurisdiction indicators or history flags.

Input

Key	Type	Meaning
entityNames	array of strings	Entity-name searches. Delaware matches names that begin with your text (punctuation ignored) and returns at most 50 matches per name — narrow the name if you get exactly 50.
fileNumbers	array of strings	Delaware file numbers (digits only, e.g. "4056247"). Exact lookup: one entity or no match.
queries	array of strings	Legacy alias of entityNames, kept for backward compatibility. Prefer entityNames.
entityName, companyName, query, search, searchTerm, keyword, name (and plurals)	string or array	Also accepted as aliases of entityNames — a comma-separated string works too. fileNumber / file_numbers alias fileNumbers.
maxEntities	integer 1–2000 (default 50)	Ceiling on unique entities delivered per run, counted by file number after de-duplication. A ceiling, not a promise: an exact search that matches one entity delivers one record. When the ceiling is reached the run stops early and says so in its status message.

Whitespace is normalized and duplicate searches run once. Order of results follows your input order, then Delaware's result order. At least one valid entity name or file number is required; otherwise the run fails with no records and no record charges.

Delivery guarantee

Every run ends in one of three states:

1. Complete — every search either returned records or was confirmed by Delaware as a genuine no-match; all unique records are delivered and charged exactly once.
2. Capped — maxEntities unique records were reached; exactly that many are delivered and charged, and the status message says the cap was reached.
3. Failed, nothing delivered — a search stayed blocked, returned an unreadable page, or could not be finished inside the run's time limit. The run fails with zero dataset rows and zero record charges. There is no partial, partially billed dataset.

Each search is attempted directly first; searches that hit a block or timeout are retried on fresh US residential proxy sessions (up to two retries), and every search gets its first attempt before any search gets a retry. An entity found by two overlapping searches is delivered once.

Quick start

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

run_input = {
    "entityNames": ["STRIPE 5", "BLUEGREEN CORPORATION GULF"],
    "fileNumbers": ["4056247"],
    "maxEntities": 100
}

run = client.actor("nexgendata/delaware-corporations-search-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["file_number"], item["entity_name"], item["search_type"])

From the Apify CLI:

apify call nexgendata/delaware-corporations-search-scraper --input='{
    "entityNames": ["STRIPE 5"],
    "fileNumbers": ["4056247"]
}'

queries still works as an alias for entityNames:

{ "queries": ["STRIPE 5"] }

Or from the web console: open the actor page on Apify, paste the input JSON, hit Run. Results land in the dataset, exportable as JSON / JSONL / CSV / Excel / HTML.

Scheduling and integration

Pairs with Apify Scheduler (hourly / daily / cron) — de-duplicate downstream on file_number. Webhook outputs are supported, so you can fire a Slack / Zapier / Make / n8n / your-own-API call when a run finishes. Rows are flat JSON and pipe directly into HubSpot / Salesforce / Pipedrive via Zapier or Make, or into BigQuery / Snowflake / Postgres on a schedule.

Pricing

Pay-per-event — you pay for delivered records, not run-time:

• $0.10 per delivered unique Delaware entity (one charge per dataset row)
• $0.00005 per actor-start event (one per run at default memory; negligible)

Cost worked example

A run that delivers 500 unique entities costs:

• 500 entities × $0.10 = $50.00
• 1 actor start × $0.00005 = negligible

So $50 per 500 delivered entities before any plan discounts — $0.10 per entity. A genuine no-match run costs only the actor-start event. A failed run delivers no records and charges no record events.

Why pay-per-event

• Predictable: cost = delivered records × $0.10, bounded by maxEntities.
• Failure-safe: if Delaware blocks the search or changes its page, the run fails with zero rows and you pay no record charges.
• Easy to attribute: one row = one unit cost.

Sister actors in the NexGenData fleet

Use case	Actor
Singapore ACRA UEN registry	singapore-acra-companies
Hong Kong Companies Registry	hk-companies-registry
India MCA company search	india-mca-companies
Y Combinator alumni database	yc-companies-directory-scraper
SEC Form D private placement filings	sec-form-d-scraper
Crunchbase news & funding announcements	crunchbase-news-scraper
PR Newswire press release stream	pr-newswire-press-releases-scraper

FAQ

Is the data live from Delaware? Yes — each search hits the Delaware Division of Corporations' public search at run time.

Can I search by name or file number? Both. Name searches return every entity whose name begins with your text (max 50 per search). File-number searches return the single entity with that file number.

What happens when Delaware blocks or times out? The search is retried on fresh residential sessions. If it still cannot be completed, the whole run fails with no records and no record charges — you never receive a silently incomplete dataset.

Output format? JSON, JSONL, CSV, Excel via Apify dataset export. Fields are listed above and are stable.

Schema stability

New fields may be added over time (they appear as new keys; older runs will not have them). Existing fields are not renamed or removed without a major-version bump. search_type was added in this version.

Compliance

• Reads public, unauthenticated pages of the Delaware Division of Corporations search, the same way a browser does.
• Requests use Apify's residential-proxy infrastructure for retries, with bounded concurrency.
• You are responsible for ensuring your downstream use complies with the source's terms and applicable law.
• No credentials for the target site are collected, stored or transmitted.

Support

Open an issue on the actor's Apify Issues tab.

About NexGenData

NexGenData publishes buyer-intent data actors covering SEC filings, company registries, lead generation, competitive intelligence, stock fundamentals, job boards and more, all pay-per-result. Browse the catalog at https://apify.com/nexgendata?fpr=2ayu9b

---

SEO: 🏛️ Delaware Corp Search Scraper — DE Registry Lookup API

---

🚀 New to Apify?

Don't have an Apify account yet? Get $5 in platform credit to try this Actor and 30,000+ others — no credit card required.