# Texas New Restaurant & Bar Permits (`hospitalitystack/texas-new-restaurant-bar-permits`) Actor

New Texas restaurant and bar sales-tax permits from official state data, with opening dates and chain flags. Free tools at gethospitalitystack.com/free/

- **URL**: https://apify.com/hospitalitystack/texas-new-restaurant-bar-permits.md
- **Developed by:** [Hospitality Stack](https://apify.com/hospitalitystack) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.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 Restaurant & Bar Permits: Pre-Opening Leads

Find new Texas restaurants, bars, coffee shops, caterers and food trucks **before they open**. Each new food & drink outlet that registers for a Texas sales-tax permit is listed, along with its **planned first-sales date**, the owner entity, and **chain grouping**.

Data comes only from the official **Texas Comptroller of Public Accounts, Active Sales Tax Permit Holders** open dataset (data.texas.gov, Socrata API `jrea-zgmq`, refreshed daily). There's no scraping, no logins and no proxies, so runs are fast and cheap. Sole-proprietor personal names and home mailing addresses are removed; only business/entity names are kept.

### Who it's for

- POS, payments, payroll and restaurant-tech sales teams
- Food & beverage distributors, suppliers and equipment vendors
- Insurance, staffing, marketing and delivery platforms
- Market researchers tracking restaurant openings by city or county

### Input

| Field | Default | Description |
|---|---|---|
| `daysBack` | 30 | Permits issued in the last N days |
| `city` | – | Outlet city (e.g. `Austin`, `Houston`) |
| `county` | – | Texas county name (e.g. `Travis`, `Harris`, `Dallas`) |
| `categories` | all | NAICS 722 sub-categories: full-service, limited-service, cafeteria, snack/coffee bar, bar/drinking place, contractor, caterer, food truck |
| `newOutletsOnly` | true | Drop re-issued permits for outlets that were already selling |
| `upcomingOnly` | false | Only outlets whose planned first-sales date is today or later |
| `onlyNew` | false | De-dup across runs: output only records that are NEW or UPDATED since your last run |
| `dedupStoreName` | `tx-restaurant-permits-seen` | Name of the memory store used by `onlyNew` |
| `webhookUrl` | – | POST results as JSON to Zapier / Make / n8n / your CRM |
| `maxItems` | 500 | Max results |

### Output (one row per outlet)

`outletName`, `category`, `naicsCode`, `address`, `city`, `county`, `zip`, `permitIssueDate`, `firstSalesDate`, `daysUntilFirstSales`, `preOpening`, `taxpayerName`, `taxpayerNumber`, `ownershipType`, `chainKey`, `taxpayerOutletCount`, `isChain`, `mailingAddress`, `changeType` (NEW/UPDATED/UNCHANGED), `firstSeenAt`, `source`.

```json
{"outletName":"FULL TIME FOOD","category":"Caterer","address":"3400 Comsouth Dr","city":"Austin","county":"Travis","zip":"78744","permitIssueDate":"2026-10-23","firstSalesDate":"2026-10-23","preOpening":false,"taxpayerName":"FULL TIME FOOD LLC","taxpayerOutletCount":1,"isChain":false,"ownershipType":"LLC","changeType":"NEW"}
```

**Chain grouping:** `taxpayerOutletCount` is how many active permitted outlets the same taxpayer has across Texas, and `isChain` is true at 3 or more. `chainKey` is a normalized brand name (store numbers and LLC/INC removed), so you can group franchise locations that have different owners.

### Tips

- Schedule it daily with `onlyNew: true` and a `webhookUrl` to get a fresh lead feed with no duplicates.
- Sort by `daysUntilFirstSales` to reach owners while they're still choosing vendors.

### Limits

The Comptroller dataset lists *active* permits only, and the planned first-sales date is what the applicant reported. No phone or email is included in the source data.

Free tools at https://gethospitalitystack.com/free/

# Actor input Schema

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

Only outlets whose sales-tax permit was issued in the last N days.

## `city` (type: `string`):

Outlet city, e.g. Austin, Houston, San Antonio.

## `county` (type: `string`):

Texas county name, e.g. Travis, Harris, Dallas.

## `categories` (type: `array`):

Leave empty for all food & drink categories (NAICS 722xxx).

## `newOutletsOnly` (type: `boolean`):

Drop re-issued permits for businesses that were already selling (first-sales date before the window).

## `upcomingOnly` (type: `boolean`):

Only outlets whose planned first-sales date is today or later.

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

Max results.

## `onlyNew` (type: `boolean`):

Remembers what earlier runs returned (named key-value store) and outputs only records that are NEW or UPDATED since then. Every record gets a changeType tag either way.

## `dedupStoreName` (type: `string`):

Name of the key-value store that remembers seen records (letters, digits, hyphens). Use different names for separate watchlists.

## `webhookUrl` (type: `string`):

If set, results are POSTed as JSON {actorId, runId, count, items} at the end of the run (Zapier, Make, n8n, CRM).

## Actor input object example

```json
{
  "daysBack": 30,
  "city": "",
  "county": "",
  "newOutletsOnly": true,
  "upcomingOnly": false,
  "maxItems": 500,
  "onlyNew": false
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `results` (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,
    "city": "",
    "county": "",
    "maxItems": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("hospitalitystack/texas-new-restaurant-bar-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,
    "city": "",
    "county": "",
    "maxItems": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("hospitalitystack/texas-new-restaurant-bar-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,
  "city": "",
  "county": "",
  "maxItems": 500
}' |
apify call hospitalitystack/texas-new-restaurant-bar-permits --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hospitalitystack/texas-new-restaurant-bar-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/1cZh2QpcgLeMoRCae/builds/4apQe5uQFLVdtGvge/openapi.json