FLYR Labs
FLYR (formerly FLYR Labs) is a San Francisco-headquartered travel technology company, founded in 2013, that builds an AI-native commercial operating system for airlines, cargo carriers and hospitality operators. Its airline portfolio spans the Cirrus Revenue Operating System (deep-learning forecasting, dynamic pricing and revenue management) and an Offer & Order Management System built on IATA open standards — NDC and ONE Order — with a certified NDC+ API, an NDC Gateway for indirect and B2B channels (GDS, OTAs), and a Legacy Translator for backward compatibility with existing PSS estates. Its hospitality arm, FLYR Hospitality (built on the acquired Pace Revenue platform), ships Optimize, Insights, Planning and Groups to 2,300+ properties with native two-way integrations into property management systems including Mews, Oracle OPERA Cloud, Apaleo, Cloudbeds, RMS Cloud, Stayntouch and Planet/Protel. FLYR has raised over $500M and employs more than 700 people. Its APIs are commercial and partner-gated: the developer portal at developer.flyr.com requires an account, and no OpenAPI, AsyncAPI or GraphQL schema is published to anonymous callers.
FLYR Labs publishes 2 APIs on the APIs.io network. Tagged areas include Company, Travel Technology, Airlines, Hospitality, and Revenue Management.
FLYR Labs’ developer surface includes documentation, support, engineering blog, legal docs, and 15 more developer resources.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
FLYR Offer & Order APIs
FLYR's airline retailing API surface — the Offer & Order Management System (OOMS), a certified NDC+ API for rich-content offers and orders, an NDC Gateway that extends modern re...
FLYR Hospitality Platform API
The API tier behind the FLYR Hospitality (Pace Revenue) revenue management platform — Optimize, Insights, Planning and Groups — serving the app.pacerevenue.com console and the n...
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.