# New Restaurant & Bar Openings (Liquor License Leads) (`pourwire/pourwire-restaurant-openings`) Actor

Restaurants and bars about to open in 11 US metros, from state liquor license filings. Name, address, license type, filing date, owner and phone where public. For POS, payments, insurance and food vendors.

- **URL**: https://apify.com/pourwire/pourwire-restaurant-openings.md
- **Developed by:** [PourWire](https://apify.com/pourwire) (community)
- **Categories:** Lead generation, Business, Open source
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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

## New Restaurant & Bar Openings (Liquor License Leads)

Find restaurants and bars **before they open**, in Texas (Austin, Dallas-Fort Worth, Houston, San Antonio, Waco-Temple), New York City and Los Angeles. This actor returns venues that have filed a liquor license application or a build-out permit, with the estimated opening window and the filing trail.

Free. No API key. Data by [PourWire](https://pourwire.com/?utm_source=apify), updated daily from public government records (TX TABC, NY SLA, CA ABC and city permit portals).

### Who uses this

- **Insurance agents**: liquor liability has to be bound before the license issues, so the pending application is the window to quote. See [how insurance agents find new restaurants](https://pourwire.com/leads/insurance?utm_source=apify).
- **POS and payments reps**: operators pick a POS 45 to 60 days before opening. See [the POS guide](https://pourwire.com/leads/pos?utm_source=apify).
- **Food and beverage distributors, equipment and build-out suppliers**: [distribution](https://pourwire.com/leads/food?utm_source=apify), [equipment](https://pourwire.com/leads/equipment?utm_source=apify).

### Output

One row per venue:

| Field | Example |
|---|---|
| metro | Austin |
| business_name | trade name on the filing |
| legal_name | the applicant entity |
| venue_type | restaurant, bar |
| street | street name (no house number) |
| city, zip | |
| estimated_opening | Dec 2026 |
| status | new, in_buildout, approved |
| first_filed | 2026-09-02 |
| filings | source, filing type, date, license type |
| page_url | the venue's PourWire page |

### What this actor does not include

This is the public tier: filings older than 30 days, street-level address, no owner contacts. The **newest filings (last 30 days), owner names, exact addresses and owner contacts where public records have one** are in the PourWire feed, emailed daily. [Start a free trial](https://pourwire.com/start?utm_source=apify), no card needed.

Browse the same data as web pages: [Austin](https://pourwire.com/austin/restaurants-opening-soon?utm_source=apify), [Dallas-Fort Worth](https://pourwire.com/dallas-fort-worth/restaurants-opening-soon?utm_source=apify), [Houston](https://pourwire.com/houston/restaurants-opening-soon?utm_source=apify), [San Antonio](https://pourwire.com/san-antonio/restaurants-opening-soon?utm_source=apify), [New York City](https://pourwire.com/new-york/restaurants-opening-soon?utm_source=apify), [Los Angeles](https://pourwire.com/los-angeles/restaurants-opening-soon?utm_source=apify).

### Input

- **metros**: which metros to return
- **status**: one filing stage, or any pre-opening stage
- **maxPerMetro**: up to 200

You can also call the JSON directly: `https://pourwire.com/api/public/openings?metro=austin`.

# Actor input Schema

## `metros` (type: `array`):

Which metros to return.

## `status` (type: `string`):

Only this stage. Leave empty for every pre-opening stage.

## `maxPerMetro` (type: `integer`):

Up to 200 openings per metro, newest filings first.

## Actor input object example

```json
{
  "metros": [
    "austin",
    "dallas-fort-worth",
    "houston",
    "new-york",
    "los-angeles"
  ],
  "status": "",
  "maxPerMetro": 100
}
```

# Actor output Schema

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

// Run the Actor and wait for it to finish
const run = await client.actor("pourwire/pourwire-restaurant-openings").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("pourwire/pourwire-restaurant-openings").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 pourwire/pourwire-restaurant-openings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pourwire/pourwire-restaurant-openings"
        }
    }
}
```

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/nxfeOwAYgfNrpPeY7/builds/2XsFFFURqhK6iYaBR/openapi.json
