Dev:PAX Portal API
User authentication endpoints
/paxportal-authorize-travelid-start- this triggers the user authentication a TravelID-account/paxportal-authorize-travelid-callback- the callback endpoint for travelID, which creates after successful authentication a local user access token and stores it as cookie and redirects the user to the Passenger Overview Screen/authorize-travelagent- endpoint invoked by the travel agent login screen, which does the b-op delegated authentication, which after success, stores the cookie and redirects to the Dev:PPA - Travel Partner Overview Screen
Regular operations endpoints
--> get-assistancerequests-of-pax
--> PAX-UID
<-- Overviewdata
--> get-assistancerequests-of-travelPartner
--> TravelParter-UID
TravelAgent-UID
<-- Groups + Data of first group
--> get-assistancerequests-of-group
--> group-UID
<-- Group data for overview
--> CreateNewRequest
--> PAXUID (if knwon)
--> TravelpartnerUID (if knwon)
--> TravelagentUID (if knwon)
--> TargetGroupUID (if knwon)
<-- RequestUID
--> get-headerpage-data
--> RequestUID
<-- Headerdetails
--> send-headerpage-data
--> HeaderDetails
<-- StateOfPersistance
--> get-serviceselectionpage-data
--> RequestUID
<-- ServiceSelectionPageDataAndOptions
--> send-serviceselectionpage-data
--> ServiceSelectionData
<-- State of Persistance
--> get-finalizationpage-data
--> RequestUID
<-- PageDataAndOptions
--> send-finalizationpage-data
--> ServiceSelectionData
<-- State of Persistance
--> cancel-request
--> requestID
<-- OK
--> file-request
--> requestID
<-- OK