Olo emits outbound HTTP webhooks to partner-registered endpoints for order lifecycle, loyalty, gift-card, tender, and marketplace status events. Each delivery includes an X-Olo-Message-Id header (a unique message UUID), an X-Olo-Timestamp header (number of ticks since 0001-01-01T00:00:00Z UTC), and an HMAC-SHA256 signature computed over the newline-joined concatenation of the webhook URL, the raw request body, the message id, and the timestamp, using a shared secret. Reference signature-validation samples are published in C#, Java, PHP, Ruby, JavaScript, and Python in github.com/ololabs/dev-support-code-samples. The event catalog and field-level schemas are documented behind the gated Olo Developer Portal; the channels below model the documented event families.
View SpecView on GitHubFood ServiceRestaurantOnline OrderingDeliveryPoint-of-SaleHospitalityPaymentsLoyaltyMarketingAsyncAPIEventsWebhooks
Channels
orderEvents
Order lifecycle events for orders placed through Olo.
loyaltyEvents
Loyalty accrual and redemption events.
giftCardEvents
Gift-card activity events.
tenderEvents
Tender (payment) events for orders.
Messages
✉
OrderEvent
Order Event
An order lifecycle event.
✉
LoyaltyEvent
Loyalty Event
A loyalty accrual or redemption event.
✉
GiftCardEvent
Gift Card Event
A gift-card activity event.
✉
TenderEvent
Tender Event
A tender (payment) event.
Servers
https
partnerEndpoint
Partner-hosted HTTPS endpoint registered to receive Olo webhooks.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.