Use cases overview

Operator: Download RFQ

As an operator, I want to download my Avinode RFQ information to my application.

This use case should be implemented when an operator wants to view RFQ's in the their own quoting system. This solution is typically implemented by a Flight Management System (FMS) provider that operators use to manage their aircraft operations.

The Operator: Download RFQ page has detailed information how to implement this use case.

Operator: Respond to RFQ

As an operator, I want to respond to an RFQ

This use case should be implemented when an operator wants to respond to an RFQ from outside Avinode. This solution is typically implemented by a Flight Management System (FMS) provider that operators use to manage their aircraft operations.

The Operator: Respond to RFQ page has detailed information how to implement this use case.

Operator: Compare in Avinode

As an operator, I want to run a comparative search in Avinode
Use the data in your incoming trip requests (RFQs) to initiate a compare search in Avinode. This is a way to benchmark yourself against the market when evaluating an RFQ.

Broker: Automatic search in Avinode

As a broker (or sub chartering operator), I want to find options for my trip without having to type in the trip details in two systems.

By integrating an external quoting tool with Avinode, you can trigger and run a pre-filled out aircraft search in Avinode, avoiding the need to enter trip details twice.

This use case should be implemented when a broker wants to find and view available options for a trip inside Avinode, and has the trip data in an external quoting tool.

Read more about how to implement this use case on the Broker: Automatic Search in Avinode page.

End-client: Find trip options

As an end-client, I want to find options for my trip.

This use case should be implemented when the end-client wants to find and view available options for a trip. The API allows searching for all available aircraft or searching only for empty legs.

The End-client: Find trip options page has detailed information on how to implement this use case.

For related use cases see pages End-client: Search Empty Legs and End-client: Send booking request.

Empty leg subscription

As a broker, I want to be notified every time a new empty leg of interest is published in Avinode.

This use case should be implemented when the broker wants to subscribe to notifications every time there is an empty leg published or updated in Avinode Marketplace, from a certain company and/or for a certain route of interest. The empty leg data can then be downloaded and published in an end-client app to allow browsing and to book available flights.


Did this page help you?