# New Restaurant & Bar Leads – Fresh Liquor Licenses (Colorado) (`leadsignal-data/colorado-new-restaurant-bar-leads`) Actor

Newly approved Colorado liquor licenses: restaurants, bars, breweries, liquor and grocery stores. Business, licensee, address, license type, issue date, from official CO Liquor Enforcement open data. Only new leads each run.

- **URL**: https://apify.com/leadsignal-data/colorado-new-restaurant-bar-leads.md
- **Developed by:** [Alex](https://apify.com/leadsignal-data) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.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

## New Restaurant & Bar Leads – Fresh Liquor Licenses (Colorado)

**Every newly approved Colorado restaurant, bar, brewpub and liquor store, within days. About 2¢ a lead.**

This feed comes from the **Colorado Liquor Enforcement Division's** official list of recently approved licenses, about **160 core licenses a month**. Each lead has the trade name, licensee entity, full premises address, license type and issue date. Add-on permits like takeout, sidewalk, manager and tobacco are filtered out by default, so every row is a real new or re-licensed venue.

👉 **Try it free:** new Apify accounts get **$5 of free platform credit every month**, enough for hundreds of leads. Click **Try for free**, set your filters and hit Start.

### Real sample leads (pulled October 2026)

| Business | Licensee | City | License | Issued |
|---|---|---|---|---|
| Sunny's | Turano LTD | Denver | Hotel & Restaurant (city) | 2026-09-30 |
| Odell Brewing Company | Odell Brewing Company Inc | Denver | Brew Pub (city) | 2026-09-29 |
| Bubba's 33 | Bubba's Holdings LLC | Northglenn | Hotel & Restaurant (city) | 2026-09-29 |

**ROI:** 1,000 new Colorado venues cost $20. One POS install or distributor account pays for years of runs.

### Who uses it

POS & payments resellers · beer, wine & spirits distributors and brand reps · food service, equipment, linen, pest control · liquor liability & commercial insurance · staffing, marketing, signage, music licensing, hospitality SaaS.

### Filters

- **Cities / ZIPs** for your territory
- **License types** (contains): `Hotel & Restaurant`, `Tavern`, `Brew Pub`, `Retail Liquor Store`, `Fermented Malt Beverage`
- **Exclude add-on permits** (on by default)
- Issue-date range

### Set it up as a daily lead feed

1. Set your filters (or leave them empty for everything).
2. Keep **Only new since last run** on. Each run returns only leads you haven't seen.
3. Click **Schedule → Daily**, then connect **Google Sheets, HubSpot, Salesforce, Slack, Zapier or Make** so fresh leads land in your tools automatically.

Runs with nothing new cost almost nothing, because you only pay for the leads you get.

### Input

```json
{"cities": ["Denver", "Boulder"], "licenseTypes": ["Hotel & Restaurant", "Tavern", "Brew Pub"], "dateFrom": "90 days", "onlyNew": true}
```

### Output fields

`address, businessName, city, issueDate, licenseNumber, licenseType, licensee, source, state, zip`. Export as CSV, Excel or JSON, or pull it through the API.

### Pricing

Pay per result: **$0.02 per lead** ($20 per 1,000). No subscription.

### FAQ

**Where does the data come from?** The "Recently Approved Liquor Licenses in Colorado" dataset on data.colorado.gov, the state's official open-data portal. It covers approvals from roughly the last three months, and the state adds new approvals in batches, so the newest ones are often 2 to 5 weeks old. Use a window like `"dateFrom": "90 days"` with **Only new** on, and each daily run returns just the approvals you haven't seen. (The Actor also drops the ~10% of rows the state publishes with scrambled columns.)
**Does it include phone numbers?** The source doesn't publish them. Enrich with your usual tool.
**How do I avoid duplicates?** Keep "Only new since last run" on, and use a different dedupe store name for each separate feed.

**Need another state or city?** Request it in the Issues tab. LeadSignal adds new feeds regularly.

***

*Last updated: October 11, 2026 · Built by **LeadSignal**: public-record lead feeds for B2B sales. Not affiliated with the Colorado Department of Revenue.*

# Actor input Schema

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

e.g. Denver, Boulder. Empty = all of Colorado.

## `zips` (type: `array`):

e.g. 80202.

## `licenseTypes` (type: `array`):

e.g. Hotel & Restaurant, Tavern, Brew Pub, Liquor Store, Fermented Malt Beverage, Retail Liquor Store.

## `excludeAddOns` (type: `boolean`):

Skip sidewalk service areas, optional premises and manager registrations.

## `dateFrom` (type: `string`):

YYYY-MM-DD or relative like '90 days'. The state publishes approvals in batches (the newest are often 2-5 weeks old), so short windows like '14 days' can come back empty.

## `dateTo` (type: `string`):

YYYY-MM-DD

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

Skip leads already returned by previous runs (ideal for scheduled daily feeds).

## `dedupeStoreName` (type: `string`):

Named key-value store used to remember seen leads. Use different names for different feeds.

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

Maximum leads to return in this run.

## Actor input object example

```json
{
  "cities": [
    "Denver"
  ],
  "excludeAddOns": true,
  "dateFrom": "90 days",
  "onlyNew": true,
  "dedupeStoreName": "co-liquor-seen",
  "maxItems": 1000
}
```

# Actor output Schema

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

All leads/records returned by 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 = {
    "cities": [
        "Denver"
    ],
    "dateFrom": "90 days"
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadsignal-data/colorado-new-restaurant-bar-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 = {
    "cities": ["Denver"],
    "dateFrom": "90 days",
}

# Run the Actor and wait for it to finish
run = client.actor("leadsignal-data/colorado-new-restaurant-bar-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 '{
  "cities": [
    "Denver"
  ],
  "dateFrom": "90 days"
}' |
apify call leadsignal-data/colorado-new-restaurant-bar-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leadsignal-data/colorado-new-restaurant-bar-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/2Cznmr3DWmdHuZrZm/builds/7rVXiHc71Dos0RygI/openapi.json