A basket is a collection of products requested by a pilot but still not paid.
Baskets can have additional information that was submitted by the pilot during his request depending on the airports’ configuration, such as ETA, ETD, POB, PAX, Commercial Flight, Cross-Country Flight, Training, Destination, Alternative airport and pilots’ comment.
Baskets are created based on the products category values. We recommend processing baskets of different types in separate orders.
You can interact with one or with all of the baskets of a given airport.
An Order is a paid basket.
After the pilot has paid for his basket, it is transformed into an order. For each order created, you can interact with the generated document and refund.
As an airport, you can post a new invoice, or get/edit an existing one.
In case of old fuel pumps, the pilot can take a picture of the pump after refueling. The image is used by the airport managers to register the data and generate an invoice.
Those routes allow you to interact (i.e. get, create, post, edit or delete), with an airports’ products. A product can be a landing, a fueling or any billable service offered by the airport.
You can use the message route to communicate with the pilot via text messages. For instance you could inform the pilot if processing of a payment fails. Messages will be send to the users email address.
Get submitted data from PPR form network
These routes allow you to get data that was submitted to a PPR form from the aeroPS PPR service.
Those routes allow you to get fuel requests by an app user. Requests include the targeted pump id and the inquired amount of fuel.