# Texas Bar Receipts Tracker — Mixed Beverage Sales (`recordstack/texas-bar-receipts-tracker`) Actor

Monthly mixed-beverage receipts for every licensed Texas bar and venue, from Texas Comptroller data: liquor, wine, beer and cover receipts with month-over-month and year-over-year change and city rank computed per location. For beverage distributors, alcohol brands and hospitality research.

- **URL**: https://apify.com/recordstack/texas-bar-receipts-tracker.md
- **Developed by:** [Alex Meacham](https://apify.com/recordstack) (community)
- **Categories:** Lead generation, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 locations

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 Bar Receipts Tracker — Mixed Beverage Sales

Monthly mixed-beverage gross receipts for **every licensed Texas bar, restaurant and venue**, from the Texas Comptroller's official Mixed Beverage Gross Receipts data — with the comparisons computed for you: **month-over-month and year-over-year change, and each location's rank within its city**.

### What you get

One row per location for the reporting period: TABC permit number, location name and business address, liquor / wine / beer / cover-charge receipts, total receipts, the prior month's and year-ago totals with percentage change, and city rank (with the number of locations ranked). Sorted by total receipts, highest first.

Reference point: the latest complete month at build time (September 2026) covered **20,942 locations and $855.0M in statewide receipts** — 1,409 locations in Austin alone.

### Who it's for

- Beverage distributors and alcohol brands: account growth, slide and churn watch by territory
- Hospitality market research and site selection
- Lenders, landlords and investors sizing up venues and trade areas

### Filters

- **Period** (YYYY-MM) — default: latest complete month (a month whose filings are still under half the prior month's is treated as still filing, and the previous month is used)
- **City** or **county code**, **minimum total receipts**
- **Only new since last run** — run it monthly and each location-period is delivered once

### Data notes

- Filings post with a lag: the newest *complete* month is typically one to two months behind the calendar. The period is printed on every row.
- Change percentages are computed on filed receipts. Event and seasonal venues (stadiums, festival sites) swing hard between months, and a venue that changes permit or location number breaks its own continuity — the numbers are the filings, not a smoothed estimate.
- Output carries the licensed business at its public business location only. The dataset's taxpayer (mailing) fields are never requested.

### Pricing

Pay per location delivered — $0.01 per location-month record with computed changes.

# Actor input Schema

## `period` (type: `string`):

Reporting month to deliver, e.g. 2026-09. Blank = latest complete month in the data.

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

Only locations in this city (e.g. Austin). City rank is computed within the city either way. Blank = statewide.

## `countyCode` (type: `string`):

Only locations in this Texas Comptroller county code (e.g. 101 = Harris). Blank = any.

## `minTotalReceipts` (type: `number`):

Only locations whose period total receipts are at or above this amount.

## `onlyNewSinceLastRun` (type: `boolean`):

Monitor mode: skip location-periods already delivered in earlier runs, so each month is delivered once.

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

Cap on locations delivered (and charged) per run, highest receipts first.

## Actor input object example

```json
{
  "period": "",
  "city": "",
  "countyCode": "",
  "minTotalReceipts": 0,
  "onlyNewSinceLastRun": false,
  "maxResults": 200
}
```

# Actor output Schema

## `datasetUrl` (type: `string`):

Open the dataset with the rows found in this run.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("recordstack/texas-bar-receipts-tracker").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("recordstack/texas-bar-receipts-tracker").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 '{}' |
apify call recordstack/texas-bar-receipts-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,recordstack/texas-bar-receipts-tracker"
        }
    }
}
```

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/D5B8EhwX3NAdfJsxz/builds/BBqFf21rISyu7PnLV/openapi.json