# Texas Tobacco & Vape Retailer Leads - New Permits Daily (`pink_comic/texas-tobacco-vape-retailer-leads`) Actor

Search 60k active Texas cigarette/tobacco and e-cigarette retailer permits from the Comptroller (updated daily): owner name, outlet (store) name, permit type, permit number, permit begin date, address, city, ZIP and county. Newest permits first for fresh store leads.

- **URL**: https://apify.com/pink_comic/texas-tobacco-vape-retailer-leads.md
- **Developed by:** [Ava Torres](https://apify.com/pink_comic) (community)
- **Categories:** Lead generation, Business, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 retailer permits

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 Tobacco & Vape Retailer Leads - New Permits Daily

Search the **Texas Comptroller Active Cigarette/Tobacco Retailers** file on data.texas.gov (about 60,000 active cigarette/tobacco and e-cigarette retailer permits, updated daily, 89k downloads).

Each result includes:

- **store (outlet) name** and **owner name** (the permit holder)
- Texas taxpayer ID and location number (find every store of one owner)
- **permit type**: cigarette/tobacco retailer or e-cigarette retailer
- permit number and **permit begin date**
- street address, city, ZIP+4 and county

Results are newest permit first, so a blank run shows stores permitted in the last few days. No API key, no CAPTCHA. Pricing: **$0.002 per permit + $0.0001 start**.

```json
{ "permitTypes": ["E-CIG"], "permitAfter": "2026-10-01", "maxResults": 500 }
```

```json
{ "counties": ["HARRIS"], "permitTypes": ["CIG/TOB"] }
```

### Use cases

Leads for convenience store, smoke shop and vape shop suppliers, distributors, POS and payments, ATM placement, security, insurance and compliance vendors; new-store tracking; market research by county.

### Limits

Texas only. No phone or email in the source. Stores that sell both product types appear once per permit type. Names are matched as substrings.

### Related

- [Pennsylvania Tobacco Retailer Leads](https://apify.com/pink_comic/pennsylvania-tobacco-retailer-leads)
- [Texas New Business Leads - Sales Tax Permits](https://apify.com/pink_comic/texas-new-business-leads-sales-tax-permits)

# Actor input Schema

## `query` (type: `string`):

Quick single store (outlet) or owner name search (contains match). Leave blank for the newest permits statewide.

## `names` (type: `array`):

Store (outlet) or owner names, contains match, case-insensitive.

## `permitAfter` (type: `string`):

Optional YYYY-MM-DD permit begin date, e.g. to get only stores permitted this month.

## `permitTypes` (type: `array`):

Contains match: 'CIG/TOB' for cigarette/tobacco retailers, 'E-CIG' for e-cigarette/vape retailers.

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

City, e.g. 'HOUSTON', 'DALLAS', 'SAN ANTONIO', 'AUSTIN'.

## `counties` (type: `array`):

County, e.g. 'HARRIS', 'DALLAS', 'BEXAR', 'TRAVIS', 'TARRANT'.

## `zipCodes` (type: `array`):

Exact 5-digit ZIP codes, e.g. '77002'.

## `permitNumbers` (type: `array`):

Exact Comptroller permit numbers for lookup.

## `taxpayerIds` (type: `array`):

Exact 11-digit Texas taxpayer IDs, returns every permitted location of that owner.

## `maxResults` (type: `integer`):

Maximum total paid dataset items, split across search terms. The default returns 10 permits (about $0.0201 including the start event).

## Actor input object example

```json
{
  "query": "",
  "names": [],
  "permitAfter": "",
  "permitTypes": [],
  "cities": [],
  "counties": [],
  "zipCodes": [],
  "permitNumbers": [],
  "taxpayerIds": [],
  "maxResults": 10
}
```

# Actor output Schema

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

Dataset items.

# 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 = {
    "query": "",
    "names": [],
    "permitAfter": "",
    "permitTypes": [],
    "cities": [],
    "counties": [],
    "zipCodes": [],
    "permitNumbers": [],
    "taxpayerIds": [],
    "maxResults": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("pink_comic/texas-tobacco-vape-retailer-leads").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 = {
    "query": "",
    "names": [],
    "permitAfter": "",
    "permitTypes": [],
    "cities": [],
    "counties": [],
    "zipCodes": [],
    "permitNumbers": [],
    "taxpayerIds": [],
    "maxResults": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("pink_comic/texas-tobacco-vape-retailer-leads").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 '{
  "query": "",
  "names": [],
  "permitAfter": "",
  "permitTypes": [],
  "cities": [],
  "counties": [],
  "zipCodes": [],
  "permitNumbers": [],
  "taxpayerIds": [],
  "maxResults": 10
}' |
apify call pink_comic/texas-tobacco-vape-retailer-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pink_comic/texas-tobacco-vape-retailer-leads"
        }
    }
}
```

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/zztNncP19uLdrnaCD/builds/diQniprW5bnbrKIBn/openapi.json