Home Providers Olo
Olo
Olo is a leading on-demand commerce platform powering the digital experience for restaurant brands, serving approximately 750+ enterprise and emerging chains across 90,000+ restaurant locations. The Olo platform combines online ordering, delivery dispatch, marketplace integration (Rails), payments (Olo Pay), guest data (GDP / Marketing), loyalty, and POS connectivity (Omnivore) into a single restaurant commerce stack. Developers and certified Olo Connect partners build against the Ordering API (custom order injection), Rails API (third-party marketplace order delivery), Dispatch API (delivery orchestration), the POS Interface (OloCloud) for direct POS integrations, the Omnivore API (multi-POS abstraction), the Olo Pay SDKs (iOS, Android, Flutter, Digital Wallets), and a webhook surface that fires order, loyalty, gift-card, and tender events. APIs use signature-based request authorization (HMAC) for ordering/rails plus webhook signature validation; sample code is published for C#, Java, PHP, Ruby, JavaScript, and Python. Olo (NYSE - OLO) is headquartered in New York City and went public in March 2021.
Olo publishes 15 API contracts indexed on the APIs.io network, including Webhooks, Accounts API, Accruals API, and 12 more. Tagged areas include Food Service, Restaurant, Online Ordering, Delivery, and Point-of-Sale.
The Olo catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 3 Spectral governance rulesets.
Olo’s developer surface includes authentication, developer portal, signup flow, documentation, support, engineering blog, YouTube channel, and 36 more developer resources.
2 published contracts1 MCP Servers18 Features10 Use Cases
On this page
Kin Score FAQ ☀ Get your badge Standards 3
APIs 15
Postman 6
Open Collections 8
MCP Servers 1
Pricing
Pricing Plans 1
Rate Limits 1
FinOps 1
Features 18
Event Specs 1
Vocabularies 1
Spectral Rules 3
JSON Schema 2
JSON Structure 1
Examples 4
Security Posture 3
Agentic Access 1
Use Cases 10
Integrations 17
Solutions 3
Resources 43
apis.yml
Business capabilities this provider's published APIs can perform, derived from its own
contracts. Browse all capabilities →
42 Operational Transparency
0 Create-or-Update Ergonomics
Composite quality — 52.7/100 · developing
Agent readiness — 32/100 · agent ready
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted .
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons ; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
measured — observed by APIs.io (verified)
measured — observed by APIs.io (published)
measured — observed by APIs.io (published)
Individual APIs this provider publishes, each with its own machine-readable definition.
Scroll for all 15
Ready-to-run Postman collections for exercising this provider's APIs.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Scroll for all 8
Model Context Protocol servers that expose these APIs to AI agents.
Olo API pricing
Not yet checked against Olo's own pricing page. Compiled by API Evangelist on 2026-05-25 from www.olo.com/ ; confirm before you rely on a figure.
Plan Price
Olo Restaurant Platform (Brand Contract) enterprise
— Olo Pay (Embedded Payments) enterprise
— Omnivore POS Partner API partner
— Olo Connect Partner Program partner
—
Plan details, limits and sources →
Rate limits
Olo Ordering API partner limits: not publicly published; defined per partner agreement requests Olo Rails API partner limits: not publicly published; defined per Rails partner agreement requests Omnivore POS API partner limits: not publicly published; aggregate platform handles 5.6M calls/day across 23k+ locations requests
Compiled by API Evangelist, not yet checked against Olo's documentation. All 4 limits →
Published pricing tiers and plan structures.
Documented rate limits and quota policies.
Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.
Cost, billing, and metering signals for API financial operations.
Notable capabilities this provider offers.
Direct Online Ordering White-label web, mobile, and kiosk ordering surfaces backed by the Olo Ordering API for 800+ enterprise restaurant brands.
Rails Marketplace Integration Bidirectional integration with DoorDash, Uber Eats, Grubhub, Google, and 25+ marketplaces for menu sync and order injection.
Dispatch Direct Delivery Multi-DSP delivery orchestration across DoorDash Drive, Uber Direct, Postmates, and Relay with quote-and-tender routing.
Olo Network (Second-Party Distribution) Curated ordering distribution to super-apps, voice agents, and AI assistants while restaurants retain the guest relationship.
Omnivore Universal POS API Single REST interface abstracting 12+ POS systems (Aloha, PAR Brink, Micros, POSitouch, etc.) for partner integrations.
Olo Pay Embedded Payments PCI-compliant card capture, network tokenization, Apple Pay / Google Pay, and fraud prevention via native iOS, Android, and Flutter SDKs.
Guest Data Platform (GDP) Unified first-party guest profile combining ordering, payments, loyalty, host, and sentiment signals for segmentation and personalization.
Olo Marketing Lifecycle campaigns and personalization driven by GDP audiences and integrations with Attentive, Infobip, and email providers.
Olo Loyalty Native loyalty plus integrations with Punchh, Paytronix, and Thanx with loyalty SSO bound to ordering and POS.
Olo Host Reservations, waitlist, and table management (formerly Wisely) feeding GDP for unified guest profiles.
Sentiment and Reputation Aggregated post-order surveys, public review monitoring, and automated guest recovery workflows.
Catering+ Catering order management with capacity controls, lead times, and large-order workflows on top of the Ordering API.
Switchboard Digitized phone-order capture that routes voice orders into Olo Ordering and the POS Interface.
Serve and Olo Accounts Front-end ordering kit and passwordless guest checkout that reduce friction across guest channels.
Sync (Local Listings) Local listing management across Google, Yelp, and search surfaces tied to restaurant store data.
Webhooks for Order and Loyalty Events Outbound HMAC-signed webhooks for order lifecycle, loyalty, gift-card, and tender events.
Sandbox Environment Dedicated sandbox issued through the Olo Developer Portal for partner certification and integration testing.
Olo Connect Partner Program Tiered (Standard, Gold, Platinum) partner program governing certification, co-marketing, and integration distribution.
Scroll for all 18
AsyncAPI definitions for this provider's event-driven and streaming APIs.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral governance rulesets for linting and validating these APIs.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure definitions describing this provider's data shapes.
Example request and response payloads for these APIs.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Recommended x-agentic-access execution contracts for AI agents.
What developers build with this provider.
Scroll for all 10
Pre-built integrations with other platforms and tools.
Scroll for all 17
Packaged solutions this provider offers.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 12
SDKs, sample code, and the tooling you integrate with
Scroll for all 12
Access & Security 5
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
aid: olo
name: Olo
description: Olo is a leading on-demand commerce platform powering the digital experience for restaurant brands, serving approximately
750+ enterprise and emerging chains across 90,000+ restaurant locations. The Olo platform combines online ordering, delivery
dispatch, marketplace integration (Rails), payments (Olo Pay), guest data (GDP / Marketing), loyalty, and POS connectivity
(Omnivore) into a single restaurant commerce stack. Developers and certified Olo Connect partners build against the Ordering
API (custom order injection), Rails API (third-party marketplace order delivery), Dispatch API (delivery orchestration),
the POS Interface (OloCloud) for direct POS integrations, the Omnivore API (multi-POS abstraction), the Olo Pay SDKs (iOS,
Android, Flutter, Digital Wallets), and a webhook surface that fires order, loyalty, gift-card, and tender events. APIs
use signature-based request authorization (HMAC) for ordering/rails plus webhook signature validation; sample code is published
for C#, Java, PHP, Ruby, JavaScript, and Python. Olo (NYSE - OLO) is headquartered in New York City and went public in March
2021.
type: Index
deliveryModel:
model: saas
license_evidence:
not_product:
- ololabs/dev-support-code-samples
- ololabs/olo-serve-gtm-templates
- ololabs/promotions-sdk
open_source: unknown
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: low
source:
- openapi
- pricing
- repository-not-product
generated: '2026-09-25'
method: derived
accessModel:
pricing: enterprise
onboarding: unknown
trial: false
try_now: false
public: false
label: Enterprise
confidence: medium
source:
- plans
- authentication
- security
generated: '2026-11-06'
method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/olo.png
tags:
- Food Service
- Restaurant
- Online Ordering
- Delivery
- Point-of-Sale
- Hospitality
- Payments
- Loyalty
- Marketing
tags_raw:
- Food Service
- Restaurants
- Online Ordering
- Delivery
- Point of Sale
- Hospitality
- Payments
- Loyalty
- Marketing
created: '2026-05-25'
modified: '2026-06-03'
url: https://raw.githubusercontent.com/api-evangelist/olo/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis:
- aid: olo:olo-dispatch
name: Olo Dispatch API
description: The Olo Dispatch API orchestrates direct delivery for restaurants by routing orders to a network of delivery
service providers (DSPs) such as DoorDash Drive, Uber Direct, Postmates, and Relay. Dispatch handles quote retrieval,
driver assignment, status callbacks, fee calculation, and tipping. Restaurants use Dispatch to power their own branded
delivery without operating a fleet.
humanURL: https://www.olo.com/products/dispatch
tags:
- Dispatch
- Delivery
- Logistics
- Last Mile Delivery
tags_raw:
- Dispatch
- Delivery
- Logistics
- Last Mile
properties:
- type: Documentation
url: https://www.olo.com/products/dispatch
- type: StatusPage
url: https://status.olo.com/
- aid: olo:olo-pos-interface
name: Olo POS Interface (OloCloud)
description: The Olo POS Interface Specification (commonly OloCloud) is the contract POS vendors implement to make their
point-of-sale system natively integrable with Olo's ordering platform. The interface defines menu synchronization, order
injection, store hours, store status (eighty-sixing), and tender configuration that the POS must accept and respond to.
Certified POS systems include NCR Aloha, PAR Brink, Oracle Micros Simphony, POSitouch, Squirrel, and others.
humanURL: https://olosupport.zendesk.com/hc/en-us/articles/115002761943-Olo-POS-Interface-Specification-aka-OloCloud
tags:
- Point-of-Sale
- Integration
- Menus
tags_raw:
- POS
- Point of Sale
- Integration
- Menus
properties:
- type: Documentation
url: https://olosupport.zendesk.com/hc/en-us/articles/115002761943-Olo-POS-Interface-Specification-aka-OloCloud
- aid: olo:olo-omnivore
name: Omnivore POS API
description: Omnivore (acquired by Olo in 2019) is a universal POS API that abstracts 12+ point-of-sale systems behind a
single REST surface, handling 5.6M API calls per day across 23,000+ restaurant locations. Endpoints cover tickets, menus,
employees, tenders, modifiers, discounts, and location data. Supported POS systems include NCR Aloha, PAR Brink, Dinerware,
Micros Simphony, Micros 3700, POSitouch, Squirrel, XPIENT, Maitre'D, NCR Cloud Connect, Simphony FE, and SimphonyCloud.
humanURL: https://www.olo.com/omnivoreapi
tags:
- Point-of-Sale
- Omnivore
- Ticketing
- Multi-POS
tags_raw:
- POS
- Omnivore
- Tickets
- Multi-POS
properties:
- type: Documentation
url: https://www.olo.com/omnivoreapi
- type: Login
url: https://panel.omnivore.io/login
- aid: olo:olo-pay
name: Olo Pay API
description: Olo Pay is the platform's embedded payments solution, providing PCI-compliant card capture, tokenization, Apple
Pay / Google Pay digital wallet acceptance, network tokenization, fraud prevention, and chargeback handling for restaurant
brands. Developers integrate via native SDKs (iOS, Android, Flutter) and a Digital Wallets SDK that complements the Olo
Ordering API checkout flow. Olo Pay is also offered as Borderless Payments for cross-border transactions.
humanURL: https://www.olo.com/products/pay
tags:
- Payments
- Pay
- PCI
- Digital Wallet
tags_raw:
- Payments
- Pay
- PCI
- Digital Wallets
properties:
- type: Documentation
url: https://www.olo.com/products/pay
- type: SDKs
url: https://github.com/ololabs/olo-pay-ios-sdk-releases
- type: SDKs
url: https://github.com/ololabs/olo-pay-android-sdk-releases
- type: SDKs
url: https://github.com/ololabs/olo-pay-flutter-sdk-releases
- type: SDKs
url: https://github.com/ololabs/pay-digitalwallets-ios-sdk-releases
- type: SDKs
url: https://github.com/ololabs/pay-digitalwallets-android-sdk-releases
- type: SDKs
url: https://github.com/ololabs/pay-digitalwallets-flutter-sdk-releases
- aid: olo:olo-network
name: Olo Network API
description: The Olo Network is a second-party ordering ecosystem that exposes participating restaurant brands' menus and
ordering surfaces to high-intent guest channels (super-apps, wallets, voice agents, AI assistants) while keeping the restaurant
in control of the guest relationship. Network API access lets approved channel partners discover stores, fetch menus,
build baskets, and submit orders that flow through the same Ordering / POS Interface pipeline.
humanURL: https://www.olo.com/network
tags:
- Networks
- Second-Party
- Distribution
- Channels
tags_raw:
- Network
- Second-Party
- Distribution
- Channels
properties:
- type: Documentation
url: https://www.olo.com/network
- aid: olo:olo-marketing
name: Olo Marketing & Guest Data Platform API
description: Olo Marketing and the Guest Data Platform (GDP) unify first-party guest data captured across ordering, payments,
loyalty, host, and sentiment signals into a single guest profile that powers segmentation, lifecycle campaigns, and personalization.
The Marketing surface exposes segments, campaigns, audiences, events, and webhooks used by ESPs, SMS providers (Attentive,
Infobip), and loyalty engines to engage guests at scale.
humanURL: https://www.olo.com/products/marketing
tags:
- Marketing
- Guest Data Platform
- GDP
- Segmentation
- Personalization
properties:
- type: Documentation
url: https://www.olo.com/products/marketing
- aid: olo:olo-host
name: Olo Host API
description: Olo Host (acquired from Wisely) provides reservations, waitlist, table management, and host-stand workflows
for restaurants. The Host API exposes reservation creation, waitlist updates, table state, and guest tagging, integrating
with the Guest Data Platform so dine-in behavior enriches the same guest profile used in ordering and marketing.
humanURL: https://www.olo.com/products/host
tags:
- Hosts
- Reservations
- Waitlist
- Dine-In
tags_raw:
- Host
- Reservations
- Waitlist
- Dine-In
properties:
- type: Documentation
url: https://www.olo.com/products/host
- aid: olo:olo-sentiment
name: Olo Sentiment API
description: Olo Sentiment aggregates guest feedback signals - post-order surveys, public reviews (Google, Yelp), and social
mentions - and exposes them through a sentiment API used for reputation management dashboards and automated guest recovery
workflows.
humanURL: https://www.olo.com/products/sentiment
tags:
- Sentiment
- Reviews
- Reputation
- Feedback
properties:
- type: Documentation
url: https://www.olo.com/products/sentiment
- aid: olo:olo-webhooks
name: Olo Webhooks
description: Olo exposes outbound webhooks that fire on order lifecycle events (placed, confirmed, ready, completed, refunded),
gift-card activity, loyalty accrual / redemption, tender events, and marketplace status changes. Webhooks are HMAC-signed;
reference signature-validation samples are published in C#, Java, PHP, Ruby, JavaScript, and Python in the ololabs/dev-support-code-samples
repository.
humanURL: https://github.com/ololabs/dev-support-code-samples
tags:
- Webhook
- Event
- Notification
tags_raw:
- Webhooks
- Events
- Notifications
properties:
- type: Documentation
url: https://github.com/ololabs/dev-support-code-samples
- type: CodeExamples
url: https://github.com/ololabs/dev-support-code-samples
- type: AsyncAPI
url: asyncapi/olo-webhooks-asyncapi.yml
- aid: olo:olo-accounts-api
name: Olo Accounts API
description: Loyalty account creation and lookup
humanURL: https://developer.olo.com/
tags:
- Account
tags_raw:
- Accounts
properties:
- type: OpenAPI
url: openapi/olo-accounts-api-openapi.yml
- type: DeveloperPortal
url: https://developer.olo.com/
- type: Authentication
url: https://github.com/ololabs/dev-support-code-samples
- type: CodeExamples
url: https://github.com/ololabs/dev-support-code-samples
- type: Examples
url: examples/olo-ordering-check-user-exists-example.json
- type: Examples
url: examples/olo-ordering-create-basket-example.json
- type: Documentation
url: https://www.olo.com/products/rails
- type: Documentation
url: https://www.olo.com/products/olo-loyalty
- type: SDKs
url: https://github.com/ololabs/promotions-sdk
- type: Examples
url: examples/olo-promotions-validate-example.json
- type: Examples
url: examples/olo-promotions-account-example.json
- type: JSONSchema
url: json-schema/olo-promotions-account-schema.json
- type: JSONSchema
url: json-schema/olo-promotions-request-schema.json
- type: JSONStructure
url: json-structure/olo-promotions-structure.json
- aid: olo:olo-accruals-api
name: Olo Accruals API
description: Loyalty point accrual and void
humanURL: https://developer.olo.com/
tags:
- Accruals
properties:
- type: OpenAPI
url: openapi/olo-accruals-api-openapi.yml
- type: DeveloperPortal
url: https://developer.olo.com/
- type: Authentication
url: https://github.com/ololabs/dev-support-code-samples
- type: CodeExamples
url: https://github.com/ololabs/dev-support-code-samples
- type: Examples
url: examples/olo-ordering-check-user-exists-example.json
- type: Examples
url: examples/olo-ordering-create-basket-example.json
- type: Documentation
url: https://www.olo.com/products/rails
- type: Documentation
url: https://www.olo.com/products/olo-loyalty
- type: SDKs
url: https://github.com/ololabs/promotions-sdk
- type: Examples
url: examples/olo-promotions-validate-example.json
- type: Examples
url: examples/olo-promotions-account-example.json
- type: JSONSchema
url: json-schema/olo-promotions-account-schema.json
- type: JSONSchema
url: json-schema/olo-promotions-request-schema.json
- type: JSONStructure
url: json-structure/olo-promotions-structure.json
- aid: olo:olo-brand-api
name: Olo Brand API
description: Brand-level configuration and metadata
humanURL: https://developer.olo.com/
tags:
- Brands
tags_raw:
- Brand
properties:
- type: OpenAPI
url: openapi/olo-brand-api-openapi.yml
- type: DeveloperPortal
url: https://developer.olo.com/
- type: Authentication
url: https://github.com/ololabs/dev-support-code-samples
- type: CodeExamples
url: https://github.com/ololabs/dev-support-code-samples
- type: Examples
url: examples/olo-ordering-check-user-exists-example.json
- type: Examples
url: examples/olo-ordering-create-basket-example.json
- type: Documentation
url: https://www.olo.com/products/rails
- type: Documentation
url: https://www.olo.com/products/olo-loyalty
- type: SDKs
url: https://github.com/ololabs/promotions-sdk
- type: Examples
url: examples/olo-promotions-validate-example.json
- type: Examples
url: examples/olo-promotions-account-example.json
- type: JSONSchema
url: json-schema/olo-promotions-account-schema.json
- type: JSONSchema
url: json-schema/olo-promotions-request-schema.json
- type: JSONStructure
url: json-structure/olo-promotions-structure.json
- aid: olo:olo-promotions-api
name: Olo Promotions API
description: Validation and redemption of coupons and loyalty rewards
humanURL: https://developer.olo.com/
tags:
- Promotions
properties:
- type: OpenAPI
url: openapi/olo-promotions-api-openapi.yml
- type: DeveloperPortal
url: https://developer.olo.com/
- type: Authentication
url: https://github.com/ololabs/dev-support-code-samples
- type: CodeExamples
url: https://github.com/ololabs/dev-support-code-samples
- type: Examples
url: examples/olo-ordering-check-user-exists-example.json
- type: Examples
url: examples/olo-ordering-create-basket-example.json
- type: Documentation
url: https://www.olo.com/products/rails
- type: Documentation
url: https://www.olo.com/products/olo-loyalty
- type: SDKs
url: https://github.com/ololabs/promotions-sdk
- type: Examples
url: examples/olo-promotions-validate-example.json
- type: Examples
url: examples/olo-promotions-account-example.json
- type: JSONSchema
url: json-schema/olo-promotions-account-schema.json
- type: JSONSchema
url: json-schema/olo-promotions-request-schema.json
- type: JSONStructure
url: json-structure/olo-promotions-structure.json
- aid: olo:olo-rails-api
name: Olo Rails API
description: Marketplace Rails partner export and order injection operations
humanURL: https://developer.olo.com/
tags:
- Ruby on Rails
tags_raw:
- Rails
properties:
- type: OpenAPI
url: openapi/olo-rails-api-openapi.yml
- type: DeveloperPortal
url: https://developer.olo.com/
- type: Authentication
url: https://github.com/ololabs/dev-support-code-samples
- type: CodeExamples
url: https://github.com/ololabs/dev-support-code-samples
- type: Examples
url: examples/olo-ordering-check-user-exists-example.json
- type: Examples
url: examples/olo-ordering-create-basket-example.json
- type: Documentation
url: https://www.olo.com/products/rails
- type: Documentation
url: https://www.olo.com/products/olo-loyalty
- type: SDKs
url: https://github.com/ololabs/promotions-sdk
- type: Examples
url: examples/olo-promotions-validate-example.json
- type: Examples
url: examples/olo-promotions-account-example.json
- type: JSONSchema
url: json-schema/olo-promotions-account-schema.json
- type: JSONSchema
url: json-schema/olo-promotions-request-schema.json
- type: JSONStructure
url: json-structure/olo-promotions-structure.json
- aid: olo:olo-users-api
name: Olo Users API
description: Guest account lookups
humanURL: https://developer.olo.com/
tags:
- User
tags_raw:
- Users
properties:
- type: OpenAPI
url: openapi/olo-users-api-openapi.yml
- type: DeveloperPortal
url: https://developer.olo.com/
- type: Authentication
url: https://github.com/ololabs/dev-support-code-samples
- type: CodeExamples
url: https://github.com/ololabs/dev-support-code-samples
- type: Examples
url: examples/olo-ordering-check-user-exists-example.json
- type: Examples
url: examples/olo-ordering-create-basket-example.json
- type: Documentation
url: https://www.olo.com/products/rails
- type: Documentation
url: https://www.olo.com/products/olo-loyalty
- type: SDKs
url: https://github.com/ololabs/promotions-sdk
- type: Examples
url: examples/olo-promotions-validate-example.json
- type: Examples
url: examples/olo-promotions-account-example.json
- type: JSONSchema
url: json-schema/olo-promotions-account-schema.json
- type: JSONSchema
url: json-schema/olo-promotions-request-schema.json
- type: JSONStructure
url: json-structure/olo-promotions-structure.json
common:
- type: FinOps
url: finops/olo-finops.yml
- type: Website
url: https://www.olo.com/
- type: CapabilityMap
url: capabilities/olo-capability-edges.yml
name: Olo Business Capability Map
- type: IssueTracker
url: https://github.com/ololabs/promotions-sdk/issues
- type: Releases
url: https://github.com/ololabs/promotions-sdk/releases
- type: PostmanWorkspace
url: https://www.postman.com/kinlaneapi/olo/overview
- type: AgenticAccess
url: agentic-access/olo-agentic-access.yml
- type: TrustCenter
url: security/olo-trust-center.yml
- type: DomainSecurity
url: security/olo-domain-security.yml
- type: Authentication
url: authentication/olo-authentication.yml
- type: Portal
url: https://www.olo.com/
- type: DeveloperPortal
url: https://developer.olo.com/
- type: Signup
url: https://developer.olo.com/Account/Register
- type: Login
url: https://developer.olo.com/Account/Login
- type: Documentation
url: https://developer.olo.com/
- type: Partners
url: https://partners.olo.com/
- type: TermsOfService
url: https://www.olo.com/api-usage-terms/
- type: PrivacyPolicy
url: https://www.olo.com/privacy-policy/
- type: StatusPage
url: https://status.olo.com/
- type: Support
url: https://olosupport.zendesk.com/hc/en-us
- type: KnowledgeCenter
url: https://olosupport.zendesk.com/hc/en-us
- type: Blog
url: https://www.olo.com/blog
- type: GitHubOrganization
url: https://github.com/ololabs
- type: GitHubRepository
url: https://github.com/ololabs/dev-support-code-samples
- type: GitHubRepository
url: https://github.com/ololabs/promotions-sdk
- type: GitHubRepository
url: https://github.com/ololabs/olo-serve-gtm-templates
- type: SpectralRules
url: rules/olo-spectral-rules.yml
- type: LinkedIn
url: https://www.linkedin.com/company/olo
- type: X
url: https://twitter.com/olo
- type: YouTube
url: https://www.youtube.com/@OloRestaurantTech
- type: Security
url: https://www.olo.com/security/
- type: TrustCenter
url: https://trust.olo.com/
- type: CodeExamples
url: https://github.com/ololabs/dev-support-code-samples
- type: SDKs
url: https://github.com/ololabs/olo-pay-ios-sdk-releases
- type: SDKs
url: https://github.com/ololabs/olo-pay-android-sdk-releases
- type: SDKs
url: https://github.com/ololabs/olo-pay-flutter-sdk-releases
- type: SDKs
url: https://github.com/ololabs/pay-digitalwallets-ios-sdk-releases
- type: SDKs
url: https://github.com/ololabs/pay-digitalwallets-android-sdk-releases
- type: SDKs
url: https://github.com/ololabs/pay-digitalwallets-flutter-sdk-releases
- type: Plans
url: plans/olo-plans-pricing.yml
- type: RateLimits
url: rate-limits/olo-rate-limits.yml
- type: Vocabulary
url: vocabulary/olo-vocabulary.yaml
- type: JSONLD
url: json-ld/olo-context.jsonld
- type: Features
data:
- name: Direct Online Ordering
description: White-label web, mobile, and kiosk ordering surfaces backed by the Olo Ordering API for 800+ enterprise restaurant
brands.
- name: Rails Marketplace Integration
description: Bidirectional integration with DoorDash, Uber Eats, Grubhub, Google, and 25+ marketplaces for menu sync and
order injection.
- name: Dispatch Direct Delivery
description: Multi-DSP delivery orchestration across DoorDash Drive, Uber Direct, Postmates, and Relay with quote-and-tender
routing.
- name: Olo Network (Second-Party Distribution)
description: Curated ordering distribution to super-apps, voice agents, and AI assistants while restaurants retain the
guest relationship.
- name: Omnivore Universal POS API
description: Single REST interface abstracting 12+ POS systems (Aloha, PAR Brink, Micros, POSitouch, etc.) for partner
integrations.
- name: Olo Pay Embedded Payments
description: PCI-compliant card capture, network tokenization, Apple Pay / Google Pay, and fraud prevention via native
iOS, Android, and Flutter SDKs.
- name: Guest Data Platform (GDP)
description: Unified first-party guest profile combining ordering, payments, loyalty, host, and sentiment signals for
segmentation and personalization.
- name: Olo Marketing
description: Lifecycle campaigns and personalization driven by GDP audiences and integrations with Attentive, Infobip,
and email providers.
- name: Olo Loyalty
description: Native loyalty plus integrations with Punchh, Paytronix, and Thanx with loyalty SSO bound to ordering and
POS.
- name: Olo Host
description: Reservations, waitlist, and table management (formerly Wisely) feeding GDP for unified guest profiles.
- name: Sentiment and Reputation
description: Aggregated post-order surveys, public review monitoring, and automated guest recovery workflows.
- name: Catering+
description: Catering order management with capacity controls, lead times, and large-order workflows on top of the Ordering
API.
- name: Switchboard
description: Digitized phone-order capture that routes voice orders into Olo Ordering and the POS Interface.
- name: Serve and Olo Accounts
description: Front-end ordering kit and passwordless guest checkout that reduce friction across guest channels.
- name: Sync (Local Listings)
description: Local listing management across Google, Yelp, and search surfaces tied to restaurant store data.
- name: Webhooks for Order and Loyalty Events
description: Outbound HMAC-signed webhooks for order lifecycle, loyalty, gift-card, and tender events.
- name: Sandbox Environment
description: Dedicated sandbox issued through the Olo Developer Portal for partner certification and integration testing.
- name: Olo Connect Partner Program
description: Tiered (Standard, Gold, Platinum) partner program governing certification, co-marketing, and integration
distribution.
- type: UseCases
data:
- name: Branded Direct Ordering for Enterprise Restaurant Chains
description: Power web, app, kiosk, and voice ordering for chains like Five Guys, P.F. Chang's, Portillo's, and First
Watch.
- name: Marketplace Order Injection
description: Inject DoorDash, Uber Eats, and Grubhub orders into the restaurant POS via Rails without manual tablet workflows.
- name: Restaurant-Operated Direct Delivery
description: Dispatch routes direct-delivery orders to DSPs without operators running their own fleet.
- name: POS Partner Integrations via Omnivore
description: Loyalty, payroll, KDS, and analytics vendors integrate against Omnivore once and reach 12+ POS systems.
- name: Loyalty and Gift Card Programs
description: Tie accrual / redemption directly to checkout via Olo Loyalty and webhooks.
- name: Guest Data Activation
description: Build first-party audiences in GDP and activate them through Olo Marketing, Attentive SMS, and email ESPs.
- name: Catering and Large-Order Channels
description: Manage catering capacity, lead times, and corporate accounts with Catering+ on top of Ordering API.
- name: Voice and AI Assistant Order Channels
description: Olo Network distributes ordering capabilities into voice, super-app, and AI assistant surfaces.
- name: Reservations and Hospitality
description: Run host stand, waitlist, and reservation flows via Olo Host while feeding the same guest profile.
- name: Reputation and Guest Recovery
description: Aggregate sentiment signals and trigger automated recovery workflows after negative experiences.
- type: Integrations
data:
- name: DoorDash
description: Marketplace ordering via Rails and direct delivery via Dispatch.
- name: Uber Eats
description: Marketplace integration via Rails and Uber Direct via Dispatch.
- name: Grubhub
description: Marketplace order injection via Rails.
- name: Google
description: Order with Google integration and Sync local listings.
- name: Toast
description: POS interoperability for shared restaurant brands.
- name: NCR Aloha
description: POS Interface and Omnivore-supported point-of-sale.
- name: PAR Brink
description: POS Interface and Omnivore-supported point-of-sale.
- name: Oracle Micros Simphony
description: POS Interface support for Simphony and SimphonyCloud.
- name: POSitouch
description: POS Interface and Omnivore-supported point-of-sale.
- name: 7shifts
description: Labor scheduling integration consuming Olo restaurant and order data.
- name: Attentive
description: SMS marketing activation driven by GDP audiences.
- name: Infobip
description: Conversational messaging integration for marketing and order updates.
- name: Punchh
description: Third-party loyalty engine integrated via Olo Loyalty.
- name: Paytronix
description: Loyalty and gift-card integration via Olo Loyalty.
- name: Thanx
description: Loyalty engine integration.
- name: Apple Pay
description: Digital wallet acceptance via Olo Pay SDKs.
- name: Google Pay
description: Digital wallet acceptance via Olo Pay SDKs.
- type: Solutions
data:
- name: Increase Orders
description: Ordering, Serve, Dispatch, Rails, Catering+, Loyalty, Order with Google, Switchboard, and Olo Network.
- name: Streamline Operations
description: Olo Pay, Host, and Sync to streamline payments, reservations, and local listings.
- name: Improve Guest Experiences
description: Marketing, GDP, Sentiment, and Olo Accounts for unified, personalized guest journeys.
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
Olo API — frequently asked questions
Does Olo have an API?
Yes. APIs.io lists 15 APIs from Olo, including Olo Dispatch API, Olo POS Interface (OloCloud) and Omnivore POS API, and 12 more.
Is there an OpenAPI specification for the Olo API?
Yes. APIs.io indexes 6 OpenAPI specifications for Olo, each linked for download from this page.
How do I authenticate with the Olo API?
Olo uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Olo Authentication.
How much does the Olo API cost?
APIs.io lists 4 pricing plans for Olo, with each plan's price, limits and inclusions under Pricing on this page.
Does Olo have an MCP server?
Yes. APIs.io lists 1 MCP server for Olo: Remote MCP server at mcp.olo.com over HTTP; 17 tools listed.
Is the Olo API ready for AI agents?
Olo has a Kin Score of 52.7 out of 100 (developing) and an Agent Readiness score of 31.7 (agent-ready), scored by API Evangelist on 2026-11-06.
Every provider here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog. get_provider_artifactsEvery artifact this provider publishes, grouped by type. get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec. get_provider_toolsEvery MCP tool they ship, with the operation each wraps. get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it. get_provider_ratingPRO — composite, band, trend and facet scores. apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total. resolveTurn a domain, URL or GitHub org into the provider it belongs to. find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This provider
curl "https://apis.io/api/v1/providers/olo"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/olo/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/olo/evidence"
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 .
A second provider on the same verified email joins the account you already have.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: