Check-in feed
Goal: Render an activity feed from one filtered call.Prep time: ~5 minutes
Off the shelf
TheCheckInFeed component from @flynetdev/react renders a member’s recent check-ins for you. Wrap it in a FlynetProvider with a FlynetMemberClient built from the member’s OAuth token, and it fetches client-side under the read:user_checkins scope.
app/feed.tsx
RecentVisits instead.
From scratch
To filter the global feed yourself, or build the row markup by hand, it’s one call.What you will use
GET /flynet/v1/check_ins
Code
The venue feed is API-key auth (server-side; the key needsread:checkins):
location with restaurant and neighborhood, plus
timestamps, so one call powers a complete feed row.
Check-ins carry no member identity — render venue and time, not a name.
Tasting note - To show a member their own visit history, use
/users/me/check_ins: the subject comes from
the token, no UUID needed.Tasting note -
ended_at may be null for ongoing visits. Handle it
explicitly in UI.Narrow by venue or time
/check_ins is an anonymized venue feed. Narrow it to one brand or one
location, optionally bounded by time:
Tasting note -
/check_ins filters are optional
([restaurant, location, created_after, created_before]), and a
bare unfiltered list returns the full paginated set rather than a
400. Always page deliberately when you omit filters. See
the reference for the full filter matrix.?restaurant={uuid}&created_after=2026-04-01T00:00:00Z
returns that brand’s check-ins since the cutoff — the basis for a venue
heatmap.
Next: First payment - accept FLY from a member.