# Texas New Business Leads (Sales Tax Permits) (`ledgerstar/texas-sales-tax-permits`) Actor

Newly issued Texas sales tax permits from the Texas Comptroller's official open data. Filter by city, ZIP, industry and date to find new businesses. Records include business name, address, NAICS code and permit date. Ready for accountants, sales teams and market research.

- **URL**: https://apify.com/ledgerstar/texas-sales-tax-permits.md
- **Developed by:** [Ledger Star](https://apify.com/ledgerstar) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Texas New Business Leads (Sales Tax Permits)

Every week thousands of Texas businesses receive a new sales tax permit. This Actor turns the Comptroller's official list into ready-to-use leads: business name, address, industry and permit date, filtered to your city and trade.

### What you get

- Fresh volume: the Comptroller issued between 3,880 and 4,593 new sales tax permits per week over the four complete weeks ending September 14, 2026 (all permit types). The count varies week to week.
- Each record has business name, legal name, address, city, ZIP, NAICS industry code and permit issue date. Business entities only by default.
- Filters for date, city, ZIP and industry, plus an alert mode that returns only permits you have not seen yet.

### Quick start

1. Choose a date range: the last N days (default 30) or an exact start date.
2. Add filters if you want them: cities, ZIP prefixes, NAICS prefixes, and a result limit.
3. Click Start, then export the results.

**Worked example:** city Austin, NAICS prefix 722 (restaurants and food service), last 7 days. In the week we measured, that search matched 26 permits, which costs about $0.10 at $0.004 each. Your count will differ week to week.

### Who uses it

- **Accountants and bookkeepers:** every new permit is a business that must now file Texas sales tax returns.

- **Local B2B sales:** new locations in your territory buying equipment, supplies and services.

- **Market research:** track new business activity by city, industry and week from official data.

### Sample output

Example rows showing the format:

| Business Name | City | ZIP | NAICS Code | Permit Issued |
|---|---|---|---|---|
| LONE STAR TACO #2 | AUSTIN | 78704 | 722513 | 2026-09-18 |
| THE COFFEE HOUSE | AUSTIN | 78701 | 722515 | 2026-09-19 |
| RETAIL SUPPLIES CO | AUSTIN | 78705 | 424990 | 2026-09-21 |

<details><summary>Full JSON example</summary>

```json
{
  "businessName": "LONE STAR TACO #2",
  "legalName": "LONE STAR TACO LLC",
  "isLegalEntity": true,
  "taxpayerNumber": "32000000000",
  "organizationTypeCode": "CL",
  "permitIssueDate": "2026-09-18",
  "firstSalesDate": "2026-09-22",
  "address": "211 S LAMAR BLVD",
  "city": "AUSTIN",
  "state": "TX",
  "zip": "78704",
  "countyCode": "227",
  "naicsCode": "722513",
  "outletNumber": "00002",
  "legalAddress": "103 CONGRESS AVE, AUSTIN, TX 78701",
  "source": "Texas Comptroller of Public Accounts — Active Sales Tax Permit Holders (Texas Open Data Portal)",
  "sourceUrl": "https://data.texas.gov/dataset/jrea-zgmq",
  "scrapedAt": "2026-09-25T14:00:00.000Z"
}
```

</details>

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| Permits issued in the last N days | integer | 30 | Look back this many days from today. Overridden if you set an exact start date. |
| Issued on or after | date | none | Exact start date in YYYY-MM-DD format. Overrides the N days option. |
| Cities | array | none | One or more Texas city names, case-insensitive exact match. |
| ZIP codes or ZIP prefixes | array | none | Full ZIP (78701) or prefix (787) to cover a region. |
| Industry (NAICS code prefixes) | array | none | 722 for restaurants, 44 or 45 for retail, 8121 for personal care. |
| Maximum results | integer | 20 | Stop after this many results. You pay per result saved. |
| Alert mode: only permits new since | string | none | Enter a date in YYYY-MM-DD format or the word lastRun to receive only new permits. Turns on alert mode. |

<details><summary>Advanced options</summary>

- **Include sole proprietors** (boolean, default false): Include sole proprietor locations when on. Personal names and taxpayer numbers are not returned.
- **Maximum source rows to scan** (integer, default 20000): Safety cap on how many source rows are read per run.
- **Socrata app token** (string, optional): Free app token from the Texas Open Data Portal. Raises rate limits for large pulls.
- **Alert mode: lookback safety window in days** (integer, default 7, max 30): Only used with lastRun above. Checks this many days before your last run for permits the source posted late. You are never charged twice for the same permit.
- **Alert mode: stable state name** (string, optional): Only used with alert mode. Give this a fixed name such as "austin nightly" so this schedule always uses the same saved last run date, even if you change other filters. Letters, numbers, and hyphens only, up to 30 characters.

</details>

### Alert mode: only new records

Run the Actor on a schedule and get only the permits issued since your last run. The first run returns normal results; every run after that returns only new permits. You pay only for new results, so a run with nothing new costs nothing.

Set it up in three steps:

1. Create a Task in Apify Console with all your filters (city, ZIP, NAICS).
2. In the Task input, set "Alert mode: only permits new since" to lastRun.
3. Go to the Task Schedule tab, click Add Schedule, and choose daily or weekly.

Keep your filters the same on every run. How the Actor remembers what it already sent is explained in the FAQ.

### Pricing

$4.00 per 1,000 results ($0.004 per business).

Worked examples: 100 results cost $0.40, 1,000 results cost $4.00, and 10,000 results cost $40.00. Set a maximum cost per run and the Actor stops cleanly at your budget.

### Integrations

- **Google Sheets:** send every run's results to a sheet automatically.
- **Zapier and Make:** trigger a workflow for each new lead, for example add it to your CRM.
- **Slack:** post a message when a run finds new permits.
- **Apify API:** download results as CSV, Excel or JSON from your own code.
- **Export:** CSV, Excel and JSON downloads straight from the dataset view.

### Data source and compliance

The data is official open data from the Texas Comptroller of Public Accounts, read through its public API without login. Only registered business entities are returned by default. The Actor never returns phone numbers, personal names or personal details of sole proprietors.

### FAQ

**How current is the data?**
Each run queries the live dataset, so results are as current as the Comptroller's latest update (schedule on https://data.texas.gov/dataset/jrea-zgmq).

**Why do some records have missing fields?**
Some fields, such as first sales date and legal address, are optional in the source and come back as null.

**What do NAICS codes mean?**
The North American Industry Classification System. Common prefixes: 722 restaurants and food service, 44 and 45 retail trade, 8121 personal care. Full list at census.gov.

**How does alert mode remember which permits to skip?**
A permit counts as new if its issue date is on or after the previous run date. The Actor looks back 7 days before the last run by default (up to 30) to catch permits the source posts late, and never charges twice for the same permit. It saves the run timestamp and a list of delivered permit ids to a named key value store in your Apify account called alert-texas-sales-tax-permits-{code}, where {code} is your 8-character store identifier. On the next run, it checks this list and skips any permit it has already sent you. Permit ids not seen for 60 days are pruned automatically. To start over and receive all permits again, delete that store in Storage in Apify Console, or set a custom alert mode stable state name to use a different store.

**Can I use this for cold outreach?**
Yes, within CAN-SPAM (email) and TCPA (phone) rules. This is public business data, not a mailing list, so contact the business, never a personal residence or personal number.

### More from Ledgerstar

- **New Business Filings:** Colorado and New York business formation data: https://apify.com/ledgerstar/state-business-filings

- **Nonprofit Finder:** IRS Exempt Organizations by state: https://apify.com/ledgerstar/nonprofit-finder

- **Chamber of Commerce Directory Scraper:** Local Chamber of Commerce business lists: https://apify.com/ledgerstar/chamber-directory-scraper

- **Building Permits Leads:** new construction and contractor permits across several cities (arriving on the Store soon)

### Support

Support: open an issue on this Actor's Issues tab in Apify Console.

# Actor input Schema

## `daysBack` (type: `integer`):

Look back this many days from today. Ignored when 'Issued on or after' is set.

## `issuedSince` (type: `string`):

Exact start date (YYYY-MM-DD). Overrides 'last N days'.

## `newSince` (type: `string`):

Turns on alert mode: only return permits issued on or after this date. Use an exact date (YYYY-MM-DD) or the word lastRun to return only permits issued since the previous successful run. Leave empty to turn alert mode off and use the settings above instead.

## `cities` (type: `array`):

Only businesses located in these Texas cities, e.g. Austin, Round Rock. Case-insensitive, exact city name.

## `zipPrefixes` (type: `array`):

e.g. 78701 for one ZIP, or 787 for all of central Austin.

## `naicsPrefixes` (type: `array`):

e.g. 722 = restaurants & bars, 44 / 45 = retail, 8121 = personal care. Leave empty for all industries.

## `includeSoleProprietors` (type: `boolean`):

Off by default: only registered entities (LLC, Inc., LP, …) are returned. When on, sole proprietors are included as business locations only — their personal name and taxpayer number are never returned.

## `maxItems` (type: `integer`):

Stop after this many results. You are charged per result.

## `maxRowsScanned` (type: `integer`):

Safety limit on how many raw rows are read while filtering (1,000 rows per request, one request per second).

## `alertLookbackDays` (type: `integer`):

Only used with the word lastRun above. Also checks this many days before your last run for permits the source posted late. You are never charged twice for the same permit, so a larger number is always safe.

## `appToken` (type: `string`):

Optional free app token from the Texas Open Data Portal. Gives higher rate limits for very large pulls. Not needed for normal use.

## `alertStateKey` (type: `string`):

Only used with alert mode (the field above). Give this a fixed name such as austin nightly so this schedule always uses the same saved last run date, even if you change other filters. Letters, numbers and hyphens only, up to 30 characters. Leave empty to have one chosen automatically based on your filters.

## Actor input object example

```json
{
  "daysBack": 30,
  "includeSoleProprietors": false,
  "maxItems": 20,
  "maxRowsScanned": 20000,
  "alertLookbackDays": 7
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

## `output` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "daysBack": 30,
    "maxItems": 20,
    "alertLookbackDays": 7
};

// Run the Actor and wait for it to finish
const run = await client.actor("ledgerstar/texas-sales-tax-permits").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "daysBack": 30,
    "maxItems": 20,
    "alertLookbackDays": 7,
}

# Run the Actor and wait for it to finish
run = client.actor("ledgerstar/texas-sales-tax-permits").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "daysBack": 30,
  "maxItems": 20,
  "alertLookbackDays": 7
}' |
apify call ledgerstar/texas-sales-tax-permits --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ledgerstar/texas-sales-tax-permits"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/es3D5CNtlTpUzfUSP/builds/Kyj1jvfEqun7ZdRVY/openapi.json