🔎 Connecticut Business Filing Events

One record per CT business filing event in a requested date window (type, company-account join key, filing date) from the keyless CT Socrata history — the window's Socrata count is reconciled against delivery.

Public, robots-honoured.

Output is one ct_business_filing_event row per result; billing is pay-per-event, the value event being one registry_record (a $0.02 start fee per run, then $0.02 per registry_record). Source: data.ct.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

Who buys this

Buyers usually search for Connecticut business filings or new business filings.

• Sales and lead-generation teams building lists from Connecticut business filings.
• KYB, onboarding and compliance teams checking new business filings.
• Market researchers and data teams that need the official record as rows.

📊 Sample Output

Real rows from run SN2FRvSTWG0otIBC1 on build 0.1.6 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

filing_number	company_account	type	filing_type	filing_date	record_created
BF-0014199751	001t000000Wo6iPAAR	Interim Notice	Interim Notice	2026-07-21T00:00:00.000	2026-09-01T00:00:00.000
BF-0014186261	001t000000WnvupAAB	Change of Business Address	Business Address Change	2026-07-02T00:00:00.000	2026-09-01T00:00:00.000
BF-0013787035	001t000000Wn0ZYAAZ	Annual Report	Annual Report	2026-07-06T00:00:00.000	2026-09-01T00:00:00.000
BF-0013606000	0018y000008p9aXAAQ	Annual Report	Annual Report	2026-07-18T00:00:00.000	2026-09-01T00:00:00.000
BF-0014198026	001eq00000aDG3rAAG	Dissolution	Certificate of Dissolution	2026-07-20T00:00:00.000	2026-09-01T00:00:00.000
BF-0013909413	001t000000WoF3ZAAV	Annual Report	Annual Report	2026-07-28T00:00:00.000	2026-09-01T00:00:00.000
BF-0014190449	001eq00001QMO5qAAH	Business Formation	Certificate of Organization	2026-07-09T00:00:00.000	2026-09-01T00:00:00.000
BF-0013696440	001eq00000SCWKCAA5	Annual Report	Annual Report	2026-07-17T00:00:00.000	2026-09-01T00:00:00.000

The run finished with the status message: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. ct_business_filing_event
• filing_number (string/null) — e.g. BF-0014199751
• company_account (string/null) — e.g. 001t000000Wo6iPAAR
• type (string/null) — e.g. Interim Notice
• filing_type (string/null) — e.g. Interim Notice
• filing_date (string/null) — e.g. 2026-07-21T00:00:00.000
• record_created (string/null) — e.g. 2026-09-01T00:00:00.000
• physical_filing (boolean/null) — e.g. False
• source (string/null) — e.g. connecticut-business-filing-events
• release_date (string/null) — null in every sample row
• source_url (string/null) — e.g. https://data.ct.gov/resource/ah3s-bes7.json
• observed_at (string/null) — e.g. 2026-09-18T20:00:37Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row

✅ What you get

• record_type (string) — e.g. ct_business_filing_event
• filing_number (string/null) — e.g. BF-0014199751
• company_account (string/null) — e.g. 001t000000Wo6iPAAR
• type (string/null) — e.g. Interim Notice
• filing_type (string/null) — e.g. Interim Notice
• filing_date (string/null) — e.g. 2026-07-21T00:00:00.000
• record_created (string/null) — e.g. 2026-09-01T00:00:00.000
• physical_filing (boolean/null) — e.g. False
• source (string/null) — e.g. connecticut-business-filing-events
• release_date (string/null) — null in every sample row
• source_url (string/null) — e.g. https://data.ct.gov/resource/ah3s-bes7.json
• observed_at (string/null) — e.g. 2026-09-18T19:30:05Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row

What you get

One registry_record per entity, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, reconciliation counts, and delivered/duplicate totals.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "dateFrom": "2026-07-01",
  "dateTo": "2026-07-31",
  "maxRecords": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 50 × $0.02 registry_record = $1.02 on the Free tier — every delivered row was billed. If you leave maxRecords out, the run delivers at most 5000 rows (the schema default); pass a number up to 500000 for a bigger export. An explicit value is always honoured up to that maximum.

2. A smaller, narrowed run

{
  "dateFrom": "2026-07-01",
  "dateTo": "2026-07-31",
  "maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02). dateFrom narrows what the source is asked for.

3. A full-size run

{
  "dateFrom": "2026-07-01",
  "dateTo": "2026-07-31",
  "maxRecords": 5000
}

Up to 5000 rows — about $100.02 on the Free tier ($0.02 start + 5000 × $0.02) if the source has that many; maxRecords goes up to 500000.

4. A filtered run

{
  "dateFrom": "2026-09-01",
  "dateTo": "2026-09-30",
  "maxRecords": 10,
  "fieldMatch": {
    "filing_type": "Certificate of Organization"
  }
}

September 2026 filings of one filing type; the source applies this filter before paging and before the maxRecords cap, so a match deep in the dataset is found, the reconciled count is the matched count, and only delivered matches are billed. A confirmed no-match ends EMPTY_SELECTION with nothing charged.

🧾 JSON sample record

One real record from run SN2FRvSTWG0otIBC1, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "ct_business_filing_event",
  "filing_number": "BF-0014199751",
  "company_account": "001t000000Wo6iPAAR",
  "type": "Interim Notice",
  "filing_type": "Interim Notice",
  "filing_date": "2026-07-21T00:00:00.000",
  "record_created": "2026-09-01T00:00:00.000",
  "physical_filing": false,
  "source": "connecticut-business-filing-events",
  "release_date": null,
  "source_url": "https://data.ct.gov/resource/ah3s-bes7.json",
  "observed_at": "2026-09-18T20:00:37Z"
}

🔧 How it works

Source. The actor reads data.ct.gov — endpoints: https://data.ct.gov/resource/ah3s-bes7.json. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each registry_record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

How it behaves

Supply a dateFrom/dateTo window (YYYY-MM-DD). Filing events are paged from Socrata and the window count reconciled. company_account is the join key to the CT business registry. An empty window or a Socrata error fails loud.

Source

https://data.ct.gov/resource/ah3s-bes7.json

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
registry_record (registry_record)	$0.02	$0.018	$0.016	$0.0134

Worked at the live Free-tier price:

• 8 registry_records: $0.02 start + 8 × $0.02 = $0.18
• 25 registry_records: $0.02 start + 25 × $0.02 = $0.52
• 5000 registry_records: $0.02 start + 5000 × $0.02 = $100.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by data.ct.gov. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (data.ct.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 5000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other company registry checks actors?
A: Same output shape and billing model; this one covers data.ct.gov. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Connecticut Business Registry (Master) — One master record per CT company (status, legal form, registration, jurisdiction, address, annual-report date) with the published diversity-ownership…
• Connecticut Business Status Check — A per-identity check: submit identifiers, get one official answer each. Billed per completed official resolution — a not-found, ambiguous, or unavail…
• Connecticut Certified Suppliers — One record per CT certified small business (certification type, services, codes, DAS prequalification, employee-size band, dates, location) from the…
• CQC Care Provider Directory Scraper — One care_provider_record per CQC-registered location: name, address, postcode, phone, website, service types, latest-check date, specialisms, provide…
• 🏢 About NexGen Watch — NexGen Watch is a catalog of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.