EveryBite APIs
EveryBite provides a comprehensive suite of APIs to power personalized dining experiences.Available APIs
SmartMenu API
Real-time menu personalization based on dietary preferences, allergens, and health goals
GuestIQ
Guest identification, segmentation, and behavioral signals for personalized experiences
Getting Started
- Get API credentials - Contact us to get your API key
- Choose your API - Select the APIs that match your use case
- Authenticate - Include your API key in the Authorization header
- Start building - Follow the Quickstart Guide
Authentication
All EveryBite APIs use API key authentication. Include your key in every request as the rawAuthorization header value:
pk_... value.
Postman users: Do not use the Authorization tab with type “Bearer Token” — Postman will prepend
If your chain API key is restricted to specific origins, also add an
Bearer to the value, which will cause authentication to fail.Instead, go to the Headers tab and add the key manually:| Key | Value |
|---|---|
Authorization | pk_YOUR_API_KEY |
Origin header with one of the approved values, otherwise the request will be rejected:| Key | Value |
|---|---|
Origin | https://your-approved-origin.com |
- API key types (Restaurant, Chain, Brand)
- Session-based context
- Rate limits and error handling
Rate Limits
| Key Type | Requests/minute | Requests/day |
|---|---|---|
| Restaurant | 60 | 10,000 |
| Chain | 300 | 100,000 |
| Brand | 1,000 | Unlimited |
Need Help?
- Check our Guides for implementation patterns
- Contact api-partnerships@everybite.com for support