Texas Active Franchise Taxpayers avatar

Texas Active Franchise Taxpayers

Pricing

from $13.40 / 1,000 registry records

Go to Apify Store
Texas Active Franchise Taxpayers

Texas Active Franchise Taxpayers

One record per active TX franchise taxpayer (identity, SOS/COA file number, organization type, charter/status dates, right-to-transact status) from the keyless TX Socrata resource.

Pricing

from $13.40 / 1,000 registry records

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Security

Limited permissions

Share

🔔 Texas Active Franchise Taxpayers

One record per active TX franchise taxpayer (identity, SOS/COA file number, organization type, charter/status dates, right-to-transact status) from the keyless TX Socrata resource. Status fields are carried verbatim — the actor never re-labels a row 'active' beyond what right_to_transact_status / sos_status_code publish. Built by NexGen Watch on Apify.

Public, robots-honoured.

Output is one tx_franchise_taxpayer 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.texas.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 Texas franchise tax or Texas business entity.

  • Sales and lead-generation teams building lists from Texas franchise tax.
  • KYB, onboarding and compliance teams checking Texas business entity.
  • Market researchers and data teams that need the official record as rows.

📊 Sample Output

Texas Active Franchise Taxpayers sample output — a table of real registry record rows (taxpayer_number, name, organization_type, responsibility_beginning_date) from run lWcrY5rteFNTWmtp9 on build 0.1.6

Real rows from run lWcrY5rteFNTWmtp9 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):

taxpayer_numbernameorganization_typeresponsibility_beginning_dateaddresscity
10101858008FIRST HARTFORD CORPORATIONCF2008-01-01T00:00:00.000149 COLONIAL RDMANCHESTER
10102062600CIANBRO CORPORATIONCF1982-08-18T00:00:00.000101 CIANBRO SQPITTSFIELD
10102338943GEIGER BROSCF1995-02-01T00:00:00.000PO BOX 1609 C/O BLAINE MARTINEAULEWISTON
10102421053FRASER PAPER LIMITEDCF2004-07-15T00:00:00.0002350 FRANKLIN RD STE 230BLOOMFIELD
10102871471ADVANTAGE PAYROLL SERVICES, INC.CF2001-08-13T00:00:00.000911 PANORAMA TRL S ATTN:DIANA WALDRUFFROCHESTER
10103094396IRVING FOREST PRODUCTS INCCF1994-10-01T00:00:00.000PO BOX 5888SAINT JOHN
10103300256JOHNSON OUTDOORS WATERCRAFT INC.CF2009-03-01T00:00:00.000555 MAIN ST STE 242RACINE
10103462742XTRA LLCCF2001-01-01T00:00:00.0007911 FORSYTH BLVD STE 600SAINT LOUIS

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. tx_franchise_taxpayer
  • taxpayer_number (string/null) — e.g. 10101858008
  • name (string/null) — e.g. FIRST HARTFORD CORPORATION
  • organization_type (string/null) — e.g. CF
  • record_type_code (string/null) — e.g. X
  • sos_coa_file_number (string/null) — e.g. 0005566306
  • sos_charter_date (string/null) — e.g. 1982-08-18T00:00:00.000
  • sos_status_date (string/null) — e.g. 2010-08-12T00:00:00.000
  • sos_status_code (string/null) — e.g. R
  • responsibility_beginning_date (string/null) — e.g. 2008-01-01T00:00:00.000
  • right_to_transact_status (string/null) — e.g. A
  • current_exempt_reason_code (string/null) — null in every sample row
  • exempt_begin_date (string/null) — null in every sample row
  • address (string/null) — e.g. 149 COLONIAL RD
  • city (string/null) — e.g. MANCHESTER
  • state (string/null) — e.g. CT
  • zip (string/null) — e.g. 06042
  • county_code (string/null) — e.g. 0
  • source (string/null) — e.g. texas-active-franchise-taxpayers
  • release_date (string/null) — null in every sample row
  • source_url (string/null) — e.g. https://data.texas.gov/resource/9cir-efmm.json
  • observed_at (string/null) — e.g. 2026-09-18T20:01:25Z
  • 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
  • license (string/integer/null) — null in every sample row
  • attribution (string/integer/null) — null in every sample row

✅ What you get

  • record_type (string) — e.g. tx_franchise_taxpayer
  • taxpayer_number (string/null) — e.g. 10101858008
  • name (string/null) — e.g. FIRST HARTFORD CORPORATION
  • organization_type (string/null) — e.g. CF
  • record_type_code (string/null) — e.g. X
  • sos_coa_file_number (string/null) — e.g. 0005566306
  • sos_charter_date (string/null) — e.g. 1982-08-18T00:00:00.000
  • sos_status_date (string/null) — e.g. 2010-08-12T00:00:00.000
  • sos_status_code (string/null) — e.g. R
  • responsibility_beginning_date (string/null) — e.g. 2008-01-01T00:00:00.000
  • right_to_transact_status (string/null) — e.g. A
  • current_exempt_reason_code (string/null) — null in every sample row
  • exempt_begin_date (string/null) — null in every sample row
  • address (string/null) — e.g. 149 COLONIAL RD
  • city (string/null) — e.g. MANCHESTER
  • state (string/null) — e.g. CT
  • zip (string/null) — e.g. 06042
  • county_code (string/null) — e.g. 0
  • source (string/null) — e.g. texas-active-franchise-taxpayers
  • release_date (string/null) — null in every sample row
  • source_url (string/null) — e.g. https://data.texas.gov/resource/9cir-efmm.json
  • observed_at (string/null) — e.g. 2026-09-18T19:31:14Z
  • 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
  • license (string/integer/null) — null in every sample row
  • attribution (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)

{
"maxRecords": 10
}

The sample run charged exactly: 2 × $0.02 apify-actor-start + 50 × $0.02 registry_record = $1.04 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

{
"maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

3. A full-size run

{
"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

{
"maxRecords": 10,
"fieldMatch": {
"name": "caldwell river ranch"
}
}

Texas taxpayers whose name contains caldwell river ranch; 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 lWcrY5rteFNTWmtp9, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "tx_franchise_taxpayer",
"taxpayer_number": "10101858008",
"name": "FIRST HARTFORD CORPORATION",
"organization_type": "CF",
"record_type_code": "X",
"sos_coa_file_number": null,
"sos_charter_date": null,
"sos_status_date": null,
"sos_status_code": null,
"responsibility_beginning_date": "2008-01-01T00:00:00.000",
"right_to_transact_status": "A",
"current_exempt_reason_code": null,
"exempt_begin_date": null,
"address": "149 COLONIAL RD",
"city": "MANCHESTER",
"state": "CT",
"zip": "06042",
"county_code": "0",
"source": "texas-active-franchise-taxpayers",
"release_date": null,
"source_url": "https://data.texas.gov/resource/9cir-efmm.json",
"observed_at": "2026-09-18T20:01:25Z"
}

🔧 How it works

Source. The actor reads data.texas.gov — endpoints: https://data.texas.gov/resource/9cir-efmm.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. Pacing: CRAWL_DELAY=0.0.

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

Rows are paged from the TX Socrata resource (:id order, $limit/$offset) and the count(*) reconciled against delivery. right_to_transact_business_code and sos_status_code are emitted exactly as published; no derived active/inactive flag is added. Streaming, bounded to maxRecords. A Socrata error on page 0 fails loud.

Source

https://data.texas.gov/resource/9cir-efmm.json

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

💰 Pricing example

EventFreeBronzeSilverGold
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.

This actor reads public, logged-out pages and feeds published by data.texas.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.texas.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 NexGen Watch actors actors?
A: Same output shape and billing model; this one covers data.texas.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 (CRAWL_DELAY=0.0) 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.
  • Spain BOE Official Records — One structured official_notice per entry in the Boletín Oficial del Estado daily summary, from the official BOE open-data API — keyless, logged-out
  • Spain BORME Company Acts Scraper — One record per registered company act ('Actos inscritos') — company name, act text, province, BORME document id and publication date — extracted as s…
  • Spain CNMC Numbering Assignments — One record per telephone-numbering allocation from the official CNMC bd-num.zip, with record_type preserving WHICH numbering table it came from and t…
  • UK Licensed Sponsor Register (Workers) — Each record carries the organisation, town/city, county, licence type & rating, and immigration route from the newest official CSV, with the register…
  • USDA Branded Food Product Master — One structured branded_food_record per branded product in USDA FoodData Central — GTIN/UPC, brand owner and name, serving size, market country, and p…
  • USDA FDC Ingredient / Label Attribute Index — One food_attribute_record per row of USDA FoodData Central's food_attribute table — the heterogeneous per-food attribute values USDA records (an attr…
  • 🏢 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.