OPEN API FRAMEWORK
8 key principles
RTN brought restaurants and suppliers together over a span of two years to develop the restaurant industry’s first game-changing Open API Framework, cemented in these eight foundational principles.
Standardized
Terms & SLAs
Easily understood terms, requirements and expectations across all levels of support and agreements.
Extensibility, Enhancements, Flexibility & Updates
The API must be actively supported with an appropriate roadmap (including end-of-life announcements).
Pricing & Business Model Transparency
Pricing and business models are easily understood and predictable.
Validation and Certification
Business partners must be able to audit & verify connectivity and appropriate usage.
Re-Use of Best Practice Data
The API should use standardized data models across functions, where possible.
Testing / Sandbox Environments
Appropriate and easily accessible testing suites utilizing commonly available tools.
Self-Service Sign-Up
for API partners
An easily accessible, straightforward process to initiate the integration project, which may include automated product API access. This may include API publishers or subscribers.
Public-Facing Documentation
Thorough, easily accessible public information about how to access, consume, and receive support for the API.
main contributors:
My company supports RTN's Open API Framework.
ADD ME TO THE LIST!
API Supplier Readiness Survey
RTN's OPEN API FRAMEWORK EBOOK
Open API Standard Webinar
On-demand
Leading Industry Voices
additional supporting brands:
Angela Diffly | angela@restauranttechnologynetwork.com | 404-550-7789
(former brand/title)
(former brand/title)