# New Bar & Restaurant Leads – Oregon Liquor License Applications (`leadsignal-data/oregon-new-liquor-license-applications`) Actor

Brand-new Oregon liquor license applications received by the OLCC: restaurants, bars, breweries, wineries, grocery and convenience stores, often weeks before opening. Trade name, license type, status and premises address. Only new leads each run.

- **URL**: https://apify.com/leadsignal-data/oregon-new-liquor-license-applications.md
- **Developed by:** [Alex](https://apify.com/leadsignal-data) (community)
- **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 Bar & Restaurant Leads: Oregon Liquor License Applications

**Every brand-new liquor license application the OLCC receives, from restaurants, bars, taprooms, hotels and wineries to groceries and convenience stores. Most arrive weeks before the doors open. About 2¢ a lead.**

The Actor reads the **Oregon Liquor and Cannabis Commission's official "Liquor Applications Received" open data**. It keeps **new applications only**, so renewals and premises amendments are excluded. By default it also drops out-of-state supplier and shipper permits, which leaves about **60–70 real Oregon outlets a month**. Each lead includes the trade name, license type (full on-premises, limited on-premises, off-premises, winery, brewery, caterer), application status, date received, and the parsed premises street, city and ZIP.

👉 **Try it free:** new Apify accounts get **$5 of free platform credit every month**.

### Real sample leads (pulled October 2026)

| Trade name | City | License type | Status | Received |
|---|---|---|---|---|
| Dinsdale Wines | Salem | Winery - Non-Consumption | In Review | 2026-10-08 |
| RiverStoneMarket | Keizer | Off-Premises Sales | In Review | 2026-10-02 |
| Staybridge Suites | Hillsboro | Limited On-Premises Sales | In Review | 2026-10-02 |
| Taqueria El Paisano Restaurant and Bar LLC | Portland | Limited On-Premises Sales | In Review | 2026-10-02 |
| Jakarta Bistro | Portland | Limited On-Premises Sales | In Review | 2026-10-01 |

**ROI:** 1,000 new Oregon venues cost $20. One POS install, distributor account or liquor-liability policy covers years of runs.

### Who uses it

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

### Filters

- **Cities / ZIPs** for your territory
- **License types** (contains): `Full On-Premises`, `Limited On-Premises`, `Off-Premises`, `Winery`, `Brewery`
- **Application statuses**: `In Review`, `Approved`, `Waiting on Information`
- **Trade name keywords**
- **Exclude supplier & shipper permits** and **Oregon premises only** (both on by default)
- Date-received range

### Set it up as a daily lead feed

1. Set your filters, or leave them empty to get all of Oregon.
2. Keep **Only new since last run** on.
3. Click **Schedule → Daily** and connect Google Sheets, HubSpot, Salesforce, Slack, Zapier or Make.

### Input

```json
{ "cities": ["Portland", "Bend"], "licenseTypes": ["On-Premises"], "dateFrom": "30 days", "onlyNew": true }
```

### Output fields

`tradeName, licenseType, applicationType, applicationStatus, dateReceived, dateAssigned, address, city, state, zip, fullAddress, source`

### Pricing

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

### FAQ

**Where does the data come from?** The OLCC "Liquor Applications Received" dataset on data.oregon.gov, the state's official open-data portal.
**Why applications instead of issued licenses?** An application is the earliest public signal. You reach the owner while they are still choosing suppliers.
**Does it include the owner's name or phone number?** OLCC publishes only the trade name and premises address. Enrich with your usual tool.

***

*Last updated: October 14, 2026 · Built by **LeadSignal**: public-record lead feeds for B2B sales. Not affiliated with the Oregon Liquor and Cannabis Commission.*

# Actor input Schema

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

e.g. Portland, Bend, Eugene, Salem. Empty = all of Oregon.

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

e.g. 97204.

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

e.g. Full On-Premises, Limited On-Premises, Off-Premises, Brewery, Winery, Caterer.

## `statuses` (type: `array`):

In Review, Waiting on Information, Approved, Withdrawn, Inactive.

## `tradeNameKeywords` (type: `array`):

e.g. Taqueria, Pizza, Market, Brewing.

## `excludeSupplierPermits` (type: `boolean`):

Skip Certificates of Approval, direct shipper/retailer permits, industrial alcohol and for-hire carrier applications (mostly out-of-state producers).

## `oregonOnly` (type: `boolean`):

Drop applications whose address is outside Oregon.

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

YYYY-MM-DD or relative like '30 days'.

## `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": [
    "Portland"
  ],
  "excludeSupplierPermits": true,
  "oregonOnly": true,
  "dateFrom": "30 days",
  "onlyNew": true,
  "dedupeStoreName": "oregon-new-liquor-license-applications-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": [
        "Portland"
    ],
    "dateFrom": "30 days"
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadsignal-data/oregon-new-liquor-license-applications").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": ["Portland"],
    "dateFrom": "30 days",
}

# Run the Actor and wait for it to finish
run = client.actor("leadsignal-data/oregon-new-liquor-license-applications").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": [
    "Portland"
  ],
  "dateFrom": "30 days"
}' |
apify call leadsignal-data/oregon-new-liquor-license-applications --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leadsignal-data/oregon-new-liquor-license-applications"
        }
    }
}
```

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/fVUdGu2J4147umayQ/builds/nwb74ibz1I05CbfG2/openapi.json