The Happy Hour API / implementation preview
Local context.
Endless possibilities.
The happy hour layer for what you're building.
Explore the data model behind nearby discovery, neighborhood research and changing offers. Public API access and commercial licenses are not yet enabled; this page describes the current implementation, not a deployed service.
Discovery
city · latitude · longitude · radius_miles
venues · published offer schedules · source
Historical observations
venue · captured_at · source · schedule
Eligible aggregate insights
approved review count · average rating
cohorts of at least 10 distinct membersA useful local layer
From nearby to market-wide.
Our current implementation separates public venue inventory from verified offer records. A discovered venue does not mean that it has a published happy hour. Schedule records carry public-source provenance and observation dates.
| Dataset | What it describes |
|---|---|
| Venue discovery | Launch city, venue location, nearby filters and available verified offers. |
| Offer observations | Posted happy hour details, schedule, source and last check where established. |
| Historical snapshots | Changes observed since our collection began—not a reconstruction of past years. |
| Eligible insights | Approved review counts and average ratings grouped by venue, with small cohorts suppressed. |
Designed for engineering teams
A small, practical surface.
The v2 implementation uses versioned JSON routes, geographic and city filters, bounded pagination, a machine-readable OpenAPI contract, scoped API keys and usage allowances. Public hosting and access activation are separate launch steps.
Implementation route preview — not live on this website
GET /api/v2/cities/
GET /api/v2/venues/
GET /api/v2/venues/{id}/
GET /api/v2/data/venues/ licensed scope
GET /api/v2/data/history/ licensed scope
GET /api/v2/data/insights/ licensed scope
GET /api/v2/schema/Nearby discovery accepts latitude, longitude and radius_miles; the consumer app starts at half a mile. Launch city slugs are columbus-oh and new-york-ny. Historical filters use timezone-aware observation timestamps.
Do not use these preview routes as production endpoints. We will provide a verified base URL, contract and access terms when hosting and onboarding are ready.
Know what the record represents
Provenance, not guesswork.
Our crawler checks public venue sources weekly for Columbus and New York. Uncertain offers remain unpublished. Display the source and last-checked time alongside an offer, and treat unknown schedules as unknown.
Historical records describe what we observed at that time. They do not establish that an offer was honored on every intervening day. Coverage is growing; we do not claim every restaurant or happy hour is represented.
Venue location discovery includes data © OpenStreetMap contributors under the Open Database License. Applicable attribution and redistribution obligations must be preserved. Public-source offer observations and commercial entitlements are separately identified.
Useful patterns, protected people
Insights without identity.
The current aggregate insights implementation returns approved review counts and average ratings grouped by venue only where at least 10 distinct members qualify. Smaller cohorts are suppressed, and some markets may have no qualifying insight data.
Licensed access does not include raw user profiles, email addresses, precise location histories, private receipts or unmoderated uploads. Do not attempt to identify individuals or circumvent suppression.
Read our privacy notice ↗Access follows an agreed license
What will you build?
When access opens, describe your use case, markets, datasets and expected volume. Pricing, license terms, redistribution rights, scope and allowances must be agreed before activation. No price, subscription or service-level commitment is offered by this website.
Keep future API keys in a server-side secret store, not a browser bundle, mobile app or public repository. Design integrations for timeouts, bounded pagination, rate limits and changing source coverage.
Contact & inquiry information ↗