Check if a user has been to a venue (from the cache)
untappd_cache_has_visitedCheck if a user has visited one or many venues from cached venue history only—no API call—by matching venue IDs, names, city/state, or coordinates.
Instructions
Answer "has this user been here?" for one or many places in ONE call, from the cached venue history only — NO API call. Each query matches by exact venue_ids, by name (case-insensitive substring or all significant words, optionally narrowed by city/state), and/or by lat/lng within radius_m (default 150 m); venue_ids are unioned with the name/geo match, and name + lat/lng together must both hold. Name/location matching matters because a brewery_id is NOT its taproom's venue_id, a brewery can have several venues, and Untappd keeps "… (duplicate of …)" venues — so expect, and check, several matches. Returns per query: visited, the matched venues (first_visit, recent_visit, total_count, is_duplicate, distance_m, and — once untappd_sync_venue_drinks has fetched them — drinks: the beer from the first/recent visit check-ins — and favorite {is_favorite, sources, reason}: derived from the visit history or added with untappd_favorite_add), and total_visits; plus a freshness block (last_synced_at, coverage_complete, caveat). Run untappd_sync_user_venues first.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| queries | Yes | Places to check (1–50); each needs venue_ids, name, or lat+lng | |
| username | No | Untappd username. Omit to use your own configured account (UNTAPPD_USERNAME). | |
| max_matches | No | Most matched venues listed per query (default 10) |