One API for the local food network
One REST API for the local food network — kitchens, farms, bookings, payments, credits and referrals in a single predictable interface. JSON in, JSON out.
curl https://api.foodweb.network/v1/map/entities \
--data-urlencode "bbox=-64.0,44.5,-63.4,44.8" \
--data-urlencode "types=kitchen,farm" -G{
"items": [
{
"entity_id": "b1c2…",
"name": "Sunrise Commercial Kitchen",
"type": "kitchen",
"place": { "city": "Halifax" }
}
],
"next_cursor": "eyJjcmVhdGVk…"
}What you can build
Seven domains, one surface
From public map reads to authenticated bookings and the credit ledger — the public platform surface is available over HTTPS.
Map & discovery
Query places and entities in a viewport. Public, no auth, keyset-paginated.
PublicBookings & availability
Register bookables, manage availability, create orders, approve and rate.
AuthPayments
Stripe PaymentIntents and Checkout Sessions, with credits applied at checkout.
AuthCredits & grants
Renter grants, partner pools, balances, invites, and the credit ledger.
AuthReferrals & partners
Join the program, mint codes, track clicks and payouts; partner self-serve.
AuthMessaging
Send messages and manage conversations; realtime reads via Firestore.
AuthSuggestions
Submit proposed map edits as a verified contributor for moderation.
AuthBearer tokens, nothing fancy
Authenticated requests carry a Firebase ID token as a Bearer token. Public map endpoints need no credentials at all.
Authorization: Bearer <firebase-id-token>Three steps to your first call
- 1
Create a key in your Food Web dashboard.
- 2
Set the header on your HTTP client.
- 3
Call an endpoint — start with the map.
Platform API updates
Release notes, endpoint changes, and developer resources from the Food Web Platform API team.
Start building on Food Web
Free in test mode. Generate a key and make your first call in minutes.