Feature #312
openAPI Integration
Start date:
02/20/2024
Due date:
% Done:
30%
Estimated time:
Owner(Agency):
Travvise
Time Taken(HH):
Module:
API
Tested By:
Code Reviewed By:
Subtasks
Related issues
Updated by Junaid M about 1 year ago
- Status changed from New to Coding Started
- % Done changed from 0 to 40
Updated by Junaid M about 1 year ago
API Documentation Shared To Abijith on 07/03/2024
Updated by Junaid M 9 months ago
API Integration Changes (13/06/2024)
----------------------------------------------
1. Create New Api For Direct Void (ticket only). * Validation: - Reject and Return Validation Response If Issued/sold record exist * Input - No fare 2. Do these changes in Refund Void API (Existing API) * Validation - If Issue/Sold record does not exist in TAAS. validate and return response ("Ticket doesnt have any issue record in TAAS, Use Direct Void instead") * Input - Add strAction Field (Values: ADD, EDIT, DELETE) Add New Section in Admin Settings --------------------------------------- 1. Booking System Integration -> Refund Void Case (Ticket Only) [Selectbox] option 1 -> Sale&Refund Seperate (*Default) option 2 -> Move to direct void (All fare components in Issue & Cancel record should be same) *in this option do validation, issue date == cancel date, issue sup, customer amount == cancel sup, customer amount option 3 -> Auto/Both (If same value in issue, cancel(input) fare component then apply direct void, otherwise keep seperate (sale&refund)) => Add in Bsp Reco redmine: Add 2 Section in void Tab 1. Refund Void Issue & Cancel Different Amount 2. Issue&Cancel Date Difference (Compare issue date and refund void date)