Flynet API

This reference documents Flynet’s launch API under: https://api.staging.blackbird.xyz/flynet/v1

Authentication

Flynet uses two credentials:

OAuth bearer tokens for /users/me/*, /check_ins/{id}, /memberships, and /payment_intents/*
API keys in X-API-Key for /restaurants*, /locations*, and the /check_ins feed (key needs the read:checkins scope)

Member routes resolve the subject from the token and are gated by scope. See Authentication for the per-route table and scope model.

Member context - the authenticated member’s profile, status, wallets, metadata tags, and check-ins via /users/me/*
Memberships - the authenticated member’s membership records
Restaurants - brand-level metadata and image assets
Locations - venue detail with address, geo, weekly open hours, and reservation fields
Check-ins - feed (filters optional) and single check-in detail
Payments - Payment Intents for FLY-funded transactions

Each endpoint has an interactive playground. Keep credentials out of screenshots and public repos.

Error response shapes vary by route family. See Pagination + errors before wiring error handling.