Skip to main content

​
Start building today

The Flynet API gives you read access to Blackbird’s dining graph and write access to FLY Payment Intents. Before you write code, walk through the steps below.
1

Get sandbox access

Request staging credentials via Request access. Approval typically takes about a week.
2

Read the house rules

Skim Concepts: auth, pagination, errors, and data model basics take ten minutes and save you bug reports later.
3

Run the quickstart

Quickstart makes three authenticated calls (wallets, check-ins, restaurants) and confirms both credential schemes work.
4

Pick a recipe

Browse Recipes for working code on common product slices: discovery, profile UI, activity feeds, and payments.
5

Wire up authentication

For production, integrate OAuth. The OAuth concept page walks the full PKCE flow in about 10 minutes. For server-to-server calls without a member context, use your API key; see API keys. Or drop in the TypeScript client and skip the plumbing.
6

Bring your AI agent

Building with Claude Code or Cursor? Build with AI wires your agent into the live docs, the API, and the SDK’s rules — or follow the full walkthrough from empty directory to a Vercel deploy.
Keep credentials server-side. Your API key and client_secret are server-to-server secrets; they must only ever be used from your backend, never shipped to a browser, mobile client, or any code your users can see. Route Discovery and token-exchange calls through your own backend; the only thing that belongs client-side is the short-lived OAuth access token, held in memory. See API keys and OAuth.

​
What you can build

Restaurant network growth

Consumer discovery

Data visualizations

Data marketplaces

Consumer marketplace tooling

Third-party tools

Get API keys →

Request sandbox access and join the developer community.

​
Resources

  • API reference: interactive playground for the launch endpoints
  • Recipes: copy-paste code for common product slices
  • FAQ: common gotchas
  • Support: get help when you’re blocked