Operator: Respond to RFQ

As an operator, I want to respond to an incoming RFQ

This use case should be implemented when the operator wants to respond to an RFQ. The application should use the different actions that was returned when the RFQ was downloaded with the GET /rfqs/{id} operation.

Quote a specific requested lift

The application should call the sellerLift.actions.submitQuote action, using the lift Id.

Decline a specific requested lift

The application should call the sellerLift.actions.decline action, using the lift Id.

15521552

Quote or decline a specific tail using the seller lift Id

Add an additional quote

The application should call the actions.submitQuote action, using the RFQ Id. The additional tail should be specified in the request body under quote.lift.aircraftTail.

Decline the entire RFQ

The application should call the actions.decline action, using the RFQ Id.

13581358

Quote an additional tail or decline the entire RFQ at once using the RFQ Id

Floating Fleet quoting options

With the addition of Floating Fleet support, the Avinode API is now able to allow quoting on a category or type of aircraft instead of, as previously, only on a tail. This will give you greater flexibility and control over how to structure, and use, the data available through the Avinode API. See input example below.

14151415

Action input

📘

Remember!

The requestId used as path param is either a:

  • lift Id - using this will decline a specific requested lift in the RFQ. If the RFQ contains other requested lifts, not yet declined or quoted, then these will still be considered unanswered.
  • RFQ Id - using this will decline the entire RFQ, including any requested lift.

Answer all RFQs

For each RFQ the operator should ideally complete at least one of these:

  • Answer all requested lifts by either calling the sellerLift.actions.submitQuote action or the sellerLift.actions.decline action, using the lift Id.
  • Decline entire RFQ by calling the actions.decline action, using the RFQ Id.

As long as the operator hasn’t completed this, the broker will see the RFQ as unanswered or partially unanswered, and the broker would still expect more information from the operator.

🚧

Note!

Leaving RFQ's unanswered or partly unanswered will affect the operator response statistics in Avinode negatively.

📘

Keeping data in sync

Sometimes a quote may be changed or updated in the operator's system outside of Avinode. For example, perhaps a price is negotiated over the phone. In those cases the operator should submit the quote again via the methods described above to ensure that the change is reflected in Avinode and that the change is distributed to all other systems connected to Avinode.

Go Live!

Let's see if you are ready to go to production.

👍

Implementation checklist

All items on this check list must be true in order for an application implementing this use case to be allowed to call the live Avinode Marketplace environment.

  • The application enables the user to quote or decline all of the lifts requested by the broker.
  • The application keeps data in sync. The application submits updated versions of the quote as needed, including all the quote line items.

What’s Next

Check out the API reference for all the endpoint details:

Did this page help you?