API archive entry · source-reported

PourWire

New restaurant and bar liquor license applications in 7 US metros (TX, NY, Los Angeles)

Provider / source website

From the publisher

README & documentation

Source preview

Read the project’s overview, installation instructions and usage examples. The original README is the source of truth.

A free, machine-readable list of restaurants and bars that recently filed for a liquor license in 11 US metros: New York City, Westchester, Long Island, Los Angeles, Phoenix, the Chicago suburbs and five Texas metros (Houston, Dallas-Fort Worth, Austin, San Antonio, Waco-Temple). A liquor license application is usually the earliest public sign that a new restaurant or bar is about to open, often weeks before it opens its doors. This dataset is published by PourWire, which tracks these filings every day for insurance agents, POS resellers, equipment suppliers and food distributors who sell to new venues. Coverage: 225 filings from 2026-10-03 to 2026-11-02. data/filings-last-30-days.csv, one row per venue: data/liquor-license-wait-times.csv: how long restaurant and bar liquor license applications take in Texas, New York City and Los Angeles (median days, sample size, as-of date, source guide). See the section below. Public records from the Texas Alcoholic Beverage Commission (TABC), the New York…

Tintin-Intellegence-Limited/us-liquor-license-applications on GitHub A short preview, not the full document.

Read the full README ↗ · Preview checked 2026-11-04T19:01:57.159Z

Inside the original README — Document outline
  1. New restaurant and bar liquor license applications (US, last 30 days)
  2. File
  3. Sources
  4. How long does a liquor license take?
  5. Free JSON API
  6. Want the full record?
  7. License

Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.

Links from the README

References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.

Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.

Where these facts came from

AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Nov 4, 2026
  2. Last directory-field change: Nov 4, 2026
  3. Current source observation: Nov 4, 2026

Submit a source-backed correction

Source reference

public-apis/public-apis

This page separates source-reported facts from questions that need live provider verification.