payments
SaaS plans
Starter, Pro and Business are published subscription plans with different booking capacities and connected-supplier limits.
Ogilio Platform
Flight API for agencies: verify content and ticketing scope
Confirm the flight supplier, API endpoints, credentials and issuing arrangement in a written proposal.
Cancel anytime
Evidence-based buying guide
Flight API for agencies: verify content and ticketing scope
Ogilio lists flight products and API access from Pro. That does not establish a universal GDS or NDC feed, a standalone Flight API licence, or ticketing under Ogilio's own accreditation. The available fares, booking steps and post-booking actions depend on the provider and commercial setup. Test your routes and issuing process before committing.
Ogilio pricing and plan scope · checked 18 Oct 2026
Ogilio offers
How Ogilio is offered
layers
Features by tier
Agency branding is listed across SaaS plans. Flight-plus-hotel packages and B2B agencies start at Pro; AI agents are listed for Business.
dns
Client-hosted option
Platinum is quoted for deployment on your infrastructure. Hosting, support and rights are defined in the contract.
Features
Travel infrastructure ready to sell
api
API entitlement
API access is listed from Pro; request current documentation for the actual flight integration.
hub
Supplier access
Confirm the active supplier and its credentials and contract; no universal feed is implied.
travel_explore
Product workflows
Ogilio lists flights, stays and own products; flight-plus-hotel packages start at Pro and depend on activation.
groups
B2B operations
Ogilio lists B2B agencies from Pro. Test partner roles, margins and any credit workflow in your own configuration.
database
Data and hosting
SaaS plans and client-hosted Platinum have different terms. Request export, licence and exit provisions in writing.
Use cases
Models for every agency
storefront
Branded booking site
Demo the customer journey with your own brand, selected inventory and configured payment gateway.
group_add
B2B network
Test a partner booking, pricing approval and support workflow against the plan in your quote.
dns
Client infrastructure
If hosting on your infrastructure matters, obtain a scoped Platinum proposal and contract.
Comparison
Apply the same criteria to every proposal
Questions for every vendor
Ogilio
API entitlement
info Which flight endpoints and limits are included in the selected plan?
info API access is listed from Pro; request current documentation for the actual flight integration.
Flight content
info Which GDS, airline or aggregator is connected for your markets?
info Confirm the active supplier and its credentials and contract; no universal feed is implied.
Ticketing responsibility
info Who issues tickets, handles accreditation and settles payment?
info Document the issuer and commercial roles for your account before selling flights.
Changes and refunds
info Which actions work for this fare and provider?
info Demonstrate cancellation, changes and refunds for the configured supplier where supported.
Testing and support
info Is a sandbox available and what service levels apply?
info Request test access, error handling and support terms in the written project scope.
Why Ogilio
Make the decision with a real configuration
check_circleUse one demo script for every vendor
Bring your supplier contracts, target markets, product list and booking workflow to each demo.
check_circleCompare full cost over your intended term
Include subscription or licence, setup, supplier access, payment fees and ongoing support.
check_circleDocument data access and exit terms
Ask both vendors to specify data export, retention and responsibilities at termination.
FAQ
Frequently asked questions
Evaluate Ogilio flight API access from Pro, available flight suppliers, ticketing responsibility and post-booking scope before integration.
The published plans list API access from Pro, but a standalone Flight API offer is not established by that listing. Ask for the current endpoints and commercial scope.
No such universal availability is established. Confirm the supplier, market, credentials and contract for your intended routes.
That depends on the issuing supplier or consolidator and your contract. Obtain the ticketing and settlement arrangement in writing.
Availability depends on the fare, airline and connected provider. Test the exact post-booking workflow before promising it to customers.
Do not assume it. Request current technical documentation, test access and service-level terms for your configuration.
Compare the platforms with your requirements
Confirm the flight supplier, API endpoints, credentials and issuing arrangement in a written proposal.
