Seekapedia: API data sets

For procurement and compliance review

Methodology and limits

How the Liquor License API gets its data, what it means, how records are matched, and what it does not do. Written to be read by someone deciding whether the data is safe to rely on.

1. Data sources and coverage

All data comes from official state agency publications. We do not buy data, scrape behind sign-ins, or infer licenses.

StateSource
TexasTexas Alcoholic Beverage Commission (TABC) license information
New YorkNew York State Liquor Authority, active licenses
New YorkNew York State Liquor Authority, inactive licenses
New YorkNew York State Liquor Authority, pending applications
CaliforniaCalifornia Department of Alcoholic Beverage Control (ABC), daily export of licenses and applications
ColoradoColorado Department of Revenue, Liquor Enforcement Division, active liquor licenses (monthly)
ColoradoColorado Department of Revenue, Liquor Enforcement Division, licenses expired or surrendered in the last three months (monthly)
OregonOregon Liquor and Cannabis Commission (OLCC), liquor business licenses and endorsements (daily)
GeorgiaGeorgia Department of Revenue, active and closed alcohol accounts (workbook, about quarterly)
WashingtonWashington State Liquor and Cannabis Board, on-premise and off-premise retail licensees, distillers and distributors (workbooks, replaced every few days)
VirginiaVirginia Alcoholic Beverage Control Authority, licensee workbook (daily)
MichiganMichigan Liquor Control Commission, master license list (workbook, about monthly)
MissouriMissouri Division of Alcohol and Tobacco Control, active alcohol licenses (daily)
IndianaIndiana Alcohol and Tobacco Commission, alcohol permit database (public Tableau export)
NebraskaNebraska Liquor Control Commission, active license roster (workbook)
StateRecords
Texas128,945
California128,294
New York126,335
Georgia98,892
Virginia59,500
Florida55,249
Michigan35,861
Oregon22,182
Indiana17,086
Colorado16,800
Washington16,257
Missouri15,907
Nebraska8,163
Total729,471

Live count from the API. Data as of November 21, 2026.

Alcohol licenses only. Local permits are not covered. State cannabis licenses are a separate product, the Cannabis License API, and are not in these counts. The live list of sources, with each agency's schedule and our latest fetch, is at GET /v1/sources.

2. What the statuses mean

We keep the agency's own status text (status_raw) and map it to one set: active, expired, suspended, cancelled, surrendered, pending, revocation_pending, inactive and unknown. A value we cannot map is unknown, never a guess. California status code R64B is not defined on any ABC page we could read, so it is reported as unknown with the code preserved.

Colorado and Oregon publish no status column. Colorado's active file lists only active licenses, so being listed there is what we report as active, and its other file states Expired or Surrendered; Oregon's file has an expired flag, which we report as expired or active. A Colorado license that was renewed after it expired can appear in both files, and then shows as a conflict for a person to look at.

Georgia publishes a workbook of alcohol accounts marked Active or Closed, which we report as active and inactive. It has no expiration date and no trade name, so those fields are empty for Georgia, never inferred. Georgia posts a new file about every quarter, with no fixed day; its freshness is judged by the age of the file (overdue after 130 days).

Washington publishes retail licensees as separate on-premise and off-premise workbooks, plus distillers and distributors, replaced every few days. A license appears once per privilege, so we keep one record per license and flag it when its rows disagree (for example an issued row beside a pending temporary one). We do not collect Washington's winery lists: they have no status column.

Virginia's workbook is refreshed daily and carries a status and expiration date for each privilege (beer and wine, mixed beverage). We report one status per license: active if any privilege is active, otherwise pending, otherwise inactive, with the latest expiration among the privileges that carry it. Tobacco permits and permits issued to individuals are left out.

Michigan's master list has no expiration date. We report Escrow (a license held out of use) as inactive and Conditional (issued subject to conditions not yet met) as pending, and keep the agency's word in status_raw. Michigan updates its list about monthly.

Missouri's open-data list contains active licenses only, with no status or expiration column, so being listed is what we report as active, as with Colorado.

Indiana's permit database is exported from the Commission's public Tableau view, which carries no publication time, so Indiana's freshness is reported as unknown. Active is reported as active, In Escrow (held out of use) as inactive and Pending Application as pending; the transitional statuses Underlying, Transfer Pending and Pending Auction are reported as unknown, with the agency's word in status_raw.

Nebraska's active roster lists active licenses only, so being listed is what we report as active; a primary license and its secondary licenses (catering, growler) share a number and appear as one record. Dates in the file are Excel day numbers, converted to calendar dates.

Colorado republishes both files monthly (the 6th), so a Colorado answer can be up to a month behind the agency; its freshness block says so. Oregon publishes daily.

A license can be marked active by the agency after its expiration date. We report both (expiration_passed) and do not decide which is right.

Applications (New York pending, California rows marked as applications) are separate records, record_kind: "application", never merged with licenses.

3. Matching

4. Freshness, conflicts and broken downloads

5. Refresh and corrections

Every source is read once a day at 14:45 UTC. We do not edit agency data. To correct a record, contact the issuing agency; the source link is on every record. Tell us at support@kixlogic.com if our copy differs from the agency's published data.

6. Security and access

All traffic is HTTPS. Each customer has an API key; every saved item (checks, watches, portfolios, policies) is private to that key. Webhooks are signed with a per-watch secret and sent only to public HTTPS addresses. Cursors are signed and bound to the key that received them. An account can issue team keys with a role (viewer, reviewer, approver or admin), and every change made through the API, and every review step, is written to a hash-chained audit log. Sign-in through an identity provider uses OpenID Connect with PKCE or SAML 2.0 with signed assertions, each checked for signature, audience, expiry and replay; stored provider secrets are encrypted, and sessions last at most eight hours. Your identity provider can provision and deactivate people over SCIM 2.0, using a bearer token we store only as a hash.

7. Customer data and retention

We store what you submit to us: key request details; webhook URLs and secrets; portfolios and the licenses in them; saved checks including the names and addresses you submitted; your policies; team members' names, optional emails and roles; reviews, with the license data as it was when each was opened; the audit log; and alert email addresses you confirm. Saved checks stay until you delete them (DELETE /v1/checks/{id}); policy versions are immutable. There is no automatic expiry yet. Ask us at support@kixlogic.com to delete anything else. We do not use your submissions for anything other than serving you.

8. Support and incidents

Support is by email at support@kixlogic.com. Response-time commitments are agreed in contract; none are published yet.

9. Permitted use

For your own internal screening and monitoring. Showing this data to your own end users, embedding it in a product, or reselling it is a separate license. Not for decisions about individuals' employment, housing, credit or insurance.

10. What this is not

It is license-data screening and monitoring. It is not a finding that a business meets every legal obligation, legal advice, a consumer report, or an enforcement history. Your policy result says only whether the data meets your rules, for a stated policy version.