EveryBite Passport
One identity. Every restaurant. Your entire dining life. EveryBite Passport is a universal dining identity that follows diners across all participating restaurants. Set preferences once, and they’re applied everywhere.
What Passport Provides
Dietary Preferences
Diets, allergens, and nutrient targets - set once, applied everywhere
Saved Dishes
Favorite dishes from any restaurant, all in one place
Meal History
Every meal tracked with full nutrition data
Health Export
Export dining data to Apple Health, Google Fit, and more
Meta-Loyalty
All loyalty programs unified under one identity
The Passport Promise
| Without Passport | With Passport |
|---|---|
| Re-enter allergies at every restaurant | Set once, known everywhere |
| Loyalty cards scattered across apps | All programs in one place |
| No record of what you’ve eaten | Complete dining history |
| Health apps don’t know your diet | Auto-sync nutrition data |
| Start fresh at every new restaurant | Recognized instantly |
How It Works
Integration Options
Option 1: Passport-Aware Menu API
The simplest integration - pass a Passport token to the Menu API:Option 2: Full Passport Integration
Access all Passport features:Authentication
Passport uses OAuth 2.0 for user authentication:1
Redirect to EveryBite
2
User Authenticates
User signs in or creates an EveryBite account
3
Receive Token
4
Use Token
Include in API requests:
Scopes
Request only the access you need:| Scope | Access |
|---|---|
passport.read | Read preferences, saved dishes |
passport.write | Update preferences, save dishes |
passport.history | Read meal history |
passport.loyalty | Access loyalty programs |
passport.health | Export to health apps |
Quick Start
Privacy & Data
User controls their data
User controls their data
Users can view, export, and delete all their Passport data at any time.
Origin tracking
Origin tracking
Passport tracks which app/restaurant created the profile and where it’s been used. This data is available to the user and used for analytics.
Developer access
Developer access
Developers only see data the user has authorized. Meal history from other restaurants is not shared unless explicitly authorized.