Blackbird · Authentication Profile
Blackbird Authentication
Authentication
Flynet uses two credentials for two route families, never interchangeable: an X-API-Key (fly_live_/fly_test_) for Discovery routes (/restaurants*, /locations*, /check_ins feed), and an OAuth 2.0 + PKCE bearer JWT for member routes (/users/me/*) and all payment intent routes. The spec models the bearer as http/JWT; the OAuth flow and scopes are documented in scopes/blackbird-scopes.yml.
Blackbird secures its APIs with apiKey and http across 2 declared security schemes, as derived from its OpenAPI definitions.
CompanyRestaurantsLoyaltyPaymentsDiningMembershipCryptoBlockchainWeb3
Methods: apiKey, http
Schemes: 2
OAuth flows:
API key in: header
Security Schemes
oauthBearer http
apiKey apiKey