# US Alcohol License Feed — Colorado + Missouri (`pennant/us-alcohol-licenses`) Actor

Current or newly approved liquor licenses from Colorado and Missouri in one schema (bars, restaurants, liquor stores, breweries, wineries, distributors). Filter by name, license type, city, ZIP, county or date. No contact names or phones; street addresses off by default.

- **URL**: https://apify.com/pennant/us-alcohol-licenses.md
- **Developed by:** [Pennant](https://apify.com/pennant) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 license 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

## US Alcohol License Feed — Colorado + Missouri

**Pennant** — Official public records as clean, tested data feeds.

One normalized feed of liquor and alcohol licenses from two state open-data portals. By default it returns **new approvals** from recent weeks. Switch to current licenses to pull the full active lists. Every item uses the same keys, whichever state or mode it came from, so you can schedule one weekly run and collect every new bar, restaurant, liquor store, brewery, winery, distributor or out-of-state shipper licensed in both states.

**Source:** Colorado Information Marketplace (data.colorado.gov, Public Domain) and Missouri open data (data.mo.gov, Missouri Division of Alcohol and Tobacco Control). Both states' required disclaimers are in the "Data sources and licenses" section below.

### Who it's for

Beverage distributors and brand reps, POS and bar-software vendors, insurance, linen and equipment suppliers, and market researchers who want to reach newly licensed venues first — or to build a two-state list of licensed premises.

**Use cases**

- A weekly list of newly approved bars, restaurants and liquor stores in both states, for distributor or rep outreach.
- Current breweries and liquor stores in a few cities, in-state premises only (`mode: "active"`, `inStateOnly: true`).
- A Missouri county-by-county list of licensed premises for territory planning (`counties`).
- One combined two-state file in a single schema, instead of two different state downloads.

### Input examples

New approvals in both states from the past few weeks (default mode):

```json
{ "mode": "newApprovals", "states": ["CO", "MO"], "maxItems": 200 }
```

Current liquor stores and breweries in Denver and Kansas City, in-state premises only:

```json
{
  "mode": "active",
  "licenseTypeContains": ["Retail Liquor Store", "Brew"],
  "cities": ["Denver", "Kansas City"],
  "inStateOnly": true,
  "maxItems": 500
}
```

The first example at a glance:

| Field | Example value | What it does |
|---|---|---|
| `mode` | `newApprovals` | Recently approved licenses (default) |
| `states` | `["CO", "MO"]` | Both states (default) |
| `inStateOnly` | `true` | Skip out-of-state shippers and suppliers |
| `maxItems` | `200` | Stop after 200 licenses |

### Input

| Field | Type | Notes |
|---|---|---|
| `mode` | `newApprovals` (default) or `active` | New approvals = recent weeks. Active = all current licenses. |
| `states` | `CO`, `MO` | Default: both. |
| `nameContains` | string | Case-insensitive substring of the licensee or DBA name. |
| `licenseTypeContains` | string list | Case-insensitive substrings of the license type, any match. |
| `cities`, `zipCodes` | string lists | Exact city names (case-insensitive) or 5-digit ZIPs. |
| `counties` | string list | Missouri counties only (Colorado does not publish county). |
| `inStateOnly` | boolean | Default off. Skip out-of-state licensees (direct shippers, solicitors, suppliers). |
| `dateFrom` / `dateTo` | YYYY-MM-DD | New approvals only. |
| `entitiesOnly` | boolean | **Default on.** Skip licensees listed only under a personal name. |
| `excludeSpecialPermits` | boolean | **Default on.** New approvals only: skip Missouri special permits and permissions (for example "Permission - Employ Minors"). |
| `sort` | `date`, `name`, `license` | Default: date for new approvals, name for current licenses. |
| `maxItemsPerState` / `maxItems` | integers | Caps (default 100 / 200). Each result is one billable event. |
| `includeStreetAddress` | boolean | **Default off.** Only city, state, ZIP and (Missouri) county unless you turn this on. Also controls Colorado map points. |
| `requestDelayMs`, `maxRetries` | integers | Politeness delay (default 1,100 ms) and retries. |

### Sample output (one item per license)

Street address and map point are omitted under the default privacy setting:

```json
{
  "licenseState": "CO",
  "feed": "newApprovals",
  "licenseNumber": "03-15258",
  "licenseType": "Hotel & Restaurant (city)",
  "licenseTypes": ["Hotel & Restaurant (city)"],
  "secondaryLicenseNumber": null,
  "status": null,
  "approvalDate": "2026-09-30",
  "expirationDate": null,
  "licenseeName": "BOTANAS LOKAS LLC",
  "dbaName": "BOTANAS LOKAS LLC",
  "businessStructure": null,
  "address": { "street": null, "city": "Aurora", "state": "CO", "zip": "80014", "county": null },
  "outOfState": false,
  "geo": null,
  "sourceDataset": "https://data.colorado.gov/Licensing/Recently-Approved-Liquor-Licenses-in-Colorado/htyp-tqzh",
  "sourceRecordUrl": "https://data.colorado.gov/resource/htyp-tqzh.json?license_number=03-15258",
  "retrievedAt": "2026-11-15T16:00:00.000Z"
}
```

The run also writes `RUN_SUMMARY` (per-state counts, skips and errors) and `SOURCE_NOTICE` (both states' required disclaimers). Fields a source does not publish are `null`.

**Example output as a table** (fictional rows, key columns only; street fields are null by default and not shown):

| licenseState | licenseType | licenseeName | dbaName | approvalDate | city | zip |
|---|---|---|---|---|---|---|
| CO | Hotel & Restaurant (city) | Copper Kettle Kitchen LLC | Copper Kettle | 2026-09-24 | Aurora | 80014 |
| MO | Retail Package Liquor | Riverbend Spirits Inc | Riverbend Spirits | 2026-11-03 | Columbia | 65201 |
| CO | Brew Pub (city) | Foothill Brewing Co LLC | Foothill Brewing | 2026-09-18 | Golden | 80401 |

### Privacy defaults

- **Registered businesses only (default on):** skips licensees listed only under a personal name, Missouri "Sole Proprietor" records, and Colorado person-only records (manager permits, "Master File (Person)"). When a person trades under a business-style DBA, the DBA is kept and the personal licensee name is hidden.
- **No contact names or phone numbers:** Missouri contact-person, contact-phone and business-phone columns are never requested. The Missouri new-licenses and Colorado datasets do not have those columns.
- **Street address and map point off by default:** only city, state, ZIP and (Missouri) county unless `includeStreetAddress` is on.
- **One item per license:** Colorado add-on permits are merged into the base license; repeats are de-duplicated per state.

### Limitations

- Covers **Colorado and Missouri only**.
- Colorado datasets have no county; the `counties` filter applies to Missouri only (noted in `RUN_SUMMARY`).
- Missouri current licenses have no date column; `sort: date` there means highest (newest) license numbers first.
- Missouri new-license dates are published as text (MM/DD/YYYY), so that listing is read in one request and date-filtered locally.
- Some Colorado recent-approval rows have the licensee and DBA swapped, and at least one issue date is far in the future (year 2262); approval dates after today are excluded unless `dateTo` is set.
- Colorado's "recently approved" dataset can lag by several weeks (newest date seen on 2026-11-15 was 2026-09-30).
- Missouri's new-licenses listing also contains special permits and permissions. They are skipped by default (`excludeSpecialPermits`); add-on privileges such as Sunday sales, tastings, extended hours and caterer licenses are kept.
- Under date sort, a Colorado add-on permit approved on a different day than its base license is not merged; the license appears once (newest row).

### Data sources and licenses

Both portals are read through the documented Socrata SODA API, with at least 1.1 seconds between pages (`Crawl-delay: 1`). This Actor is not affiliated with or endorsed by the State of Colorado or the State of Missouri. Both states require their disclaimer on any public page that uses the data; both appear below and are also written to `SOURCE_NOTICE`.

| Mode | Colorado (data.colorado.gov) | Missouri (data.mo.gov) |
|---|---|---|
| `newApprovals` (default) | Recently Approved Liquor Licenses (`htyp-tqzh`) | New Liquor Licenses (`dymb-xy5c`), past ~3 weeks |
| `active` | Liquor Licenses in Colorado (`ier5-5ms2`), ~16,650 licenses | Missouri Active Alcohol License Data (`yyhn-562y`), ~15,900 licenses |

- **Colorado:** Colorado Information Marketplace terms ([data.colorado.gov/terms](https://data.colorado.gov/terms)). Dataset licence: **Public Domain**.
- **Missouri:** State of Missouri Data Policy ([mo.gov/data-policy](https://mo.gov/data-policy)). Attribution: Missouri Division of Alcohol and Tobacco Control.

**Colorado disclaimer**

> The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk.

**Missouri disclaimer** (required on any public page that uses this data)

> The data made available here has been modified for use from its original source, which is the State of Missouri. THE STATE OF MISSOURI MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF MISSOURI EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk.

### Pricing

Pay per event, billed by Apify:

| Event | Price |
|---|---|
| Run start (`apify-actor-start`) | $0.005 per run |
| Each license returned (`result`) | $0.002 per license |

**Worked example:** one run that returns 200 licenses costs $0.005 + 200 × $0.002 = **$0.405**. A run of 1,000 licenses costs **$2.005**.

To control spend, set `maxItems` (the Actor never returns more), and set a maximum cost per run in Apify. The Actor stops cleanly when it reaches the caller's max charge, and the licenses already returned are kept.

### FAQ

**What does it cover, and what doesn't it?**

Liquor and alcohol licenses issued by Colorado and Missouri: new approvals from recent weeks, or the full current lists. It does not cover other states, local (city or county) permits in other places, or food-service licences.

**What happens to personal names and addresses?**

Licensees listed only under a personal name, Missouri sole proprietors and Colorado person-only records (manager permits, "Master File (Person)") are skipped by default. If a person trades under a business-style DBA, the DBA is kept and the personal name hidden. Missouri contact names and phone numbers are never requested. Street address and map point are off unless you turn on `includeStreetAddress`.

**Is this official data or a scrape?**

Official open data. The Actor reads each government portal's documented Socrata API, at a polite pace (at least 1.1 seconds between pages). It does not log in anywhere or scrape a private website.

**How do I cap the cost of a run?**

Set `maxItems`; each returned record is one billable result. The default is 200 in total (and 100 per state). You can also set a maximum cost per run in Apify, and the Actor stops cleanly when it reaches it.

**How fresh is the data?**

Every run reads both portals live. Missouri's new-licence list covers about the past three weeks. Colorado's recently-approved dataset can lag by several weeks (on 2026-11-15 its newest approval date was 2026-09-30).

**Is Pennant affiliated with the source?**

No. Pennant is not affiliated with or endorsed by the State of Colorado or the State of Missouri. The source agency is the authoritative record; confirm anything important with it.

**Where do I get help?**

Email 51wrw1aj@mail.grokbot.com. For a bad or unexpected record, include the run ID and the record's ID or licence number.

### For AI agents

- **Purpose:** list current or newly approved alcohol licenses in Colorado and/or Missouri.
- **Call when:** the user wants new-venue leads or a two-state licensed-premises list.
- **Minimal input:** `{}` (defaults to recent new approvals in both states).
- **Cost control:** one `result` event per license; set `maxItems`.

# Actor input Schema

## `mode` (type: `string`):

"New approvals" = Colorado recently approved licenses (htyp-tqzh) + Missouri new liquor licenses for the past ~3 weeks (dymb-xy5c). "Current licenses" = all active licenses (Colorado ier5-5ms2 + Missouri yyhn-562y).

## `states` (type: `array`):

States to include.

## `nameContains` (type: `string`):

Case-insensitive substring of the licensee or DBA (trade) name.

## `licenseTypeContains` (type: `array`):

Case-insensitive substrings of the license type, any match, e.g. Brew, Winery, Restaurant, Tavern, Retail Liquor Store, Original Package, By Drink, Solicitor, Wholesale.

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

Exact city names, case-insensitive.

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

5-digit ZIPs.

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

Missouri county names (prefix match, e.g. BOONE, ST. LOUIS). Colorado datasets do not publish a county, so this filter applies to Missouri only.

## `inStateOnly` (type: `boolean`):

Skip out-of-state licensees (direct shippers, solicitors, suppliers).

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

YYYY-MM-DD. New approvals only.

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

YYYY-MM-DD. New approvals only. Defaults to today (a source date in the future is treated as an error).

## `entitiesOnly` (type: `boolean`):

Skip licensees listed only under a personal name, sole proprietors and person-only records (manager permits, person master files); hide the licensee name when a person trades under a business-style DBA. Turn off to get every license as published.

## `excludeSpecialPermits` (type: `boolean`):

New approvals only. Missouri's new-licenses listing also publishes special permits and permissions (e.g. "Permission - Employ Minors", "Permission - Central Warehouse", license numbers starting with SP). They are not new liquor licenses, so they are skipped by default; turn off to include them. Add-on privileges such as Sunday sales, tastings, extended hours and caterer licenses are kept. Has no effect on Colorado or on "All current licenses".

## `sort` (type: `string`):

Default: date for new approvals, name for current licenses.

## `maxItemsPerState` (type: `integer`):

Cap per state.

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

Run-wide cap (each result is one billable event).

## `includeStreetAddress` (type: `boolean`):

If on, street lines (and the Colorado latitude/longitude) are returned; otherwise only city, state, ZIP and county.

## `requestDelayMs` (type: `integer`):

Politeness delay between API pages (robots.txt Crawl-delay: 1).

## `maxRetries` (type: `integer`):

Retries on timeouts, HTTP 408/429/5xx with exponential backoff and Retry-After.

## Actor input object example

```json
{
  "mode": "newApprovals",
  "states": [
    "CO",
    "MO"
  ],
  "inStateOnly": false,
  "entitiesOnly": true,
  "excludeSpecialPermits": true,
  "maxItemsPerState": 100,
  "maxItems": 200,
  "includeStreetAddress": false,
  "requestDelayMs": 1100,
  "maxRetries": 4
}
```

# Actor output Schema

## `licenses` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

## `sourceNotice` (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("pennant/us-alcohol-licenses").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("pennant/us-alcohol-licenses").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 pennant/us-alcohol-licenses --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pennant/us-alcohol-licenses"
        }
    }
}
```

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/WcpPcqJuhbGALF9gA/builds/iXi6oQsKsRaDImehg/openapi.json
