New Features
API
RESTv1 (See the API documentation for further details)
The frequentFlyers/{key}/loyaltyAccountTransactions endpoint now supports POST/PUT/DELETE transactions. This allows API users with the appropriate permissions to add or remove point transactions from a frequent traveler’s profile.
A new POST /reservations/{key}/paymentTransactions/{paymentTransactionKey}/refundTransactions endpoint has been created. This will allows your external applications to refund payment transactions.
GET queues now supports reservationNumber and reservationLocator as optional parameters. When included, only queue items related to the specified PNR will be returned.
The permission API > Expose Summary Contact Information is now required for passenger contact data to be included in GET departures calls.
...
Call centre agents can now conveniently send a payment link for PNR transactions via email. This can be done when a user wants to pay using an online payment method. Reach out to InteliSys today to activate this seamless payment option for your airline.
The user would select “Request Payment by Customer”, fill in the appropriate data and send.
An email is sent using the information entered.
When the recipient clicks the link, they will be sent to the PNR on the SOAR MMB site. They can click Settle to make a payment using any of the supported methods.
For a new booking, the PNR is left on hold until the payment is made. If the payment is not made by the end of the hold period, it is cancelled.
Ancillary items can be marked as non-refundable. If a non-refundable ancillary item is cancelled or removed, the associated charge will remain on the PNR.
When making a change using the IROPS tool, you now have the option to notify passengers during the Bulk Move phase. This saves someone from having to go into alerts and send the notifications laterfeature eliminates the need for manual alerts and delayed notifications.
When appending a new note to a PNR, the system can now append the note to display it at the top so for immediate visibility of the most recent is immediately visible. Please contact updates. Reach out to InteliSys to have enable this enabled feature for your airlinesairline.
Enhancements / Improvements
IASCASE / Issue # | Description |
---|---|
19867/22052/24953/26635/28717/29593 / AMELIA-16996 | In certain cases when rerouting multiple bags, the bag would appear on the wrong flight with incorrect passenger information. |
30767 / AMELIA-24527 | When checking in, the IATCI popup message box would show even when there was no partner airline that needed an IATCI message. This has been removed. |
Info |
---|
DATABASERefer to the following for 23.08 DB Schema Changes. |