Dev:PAX Portal API

User authentication endpoints

• /paxportal-authorize-passenger - this tries to authenticate the using passenger against a TravelID-account
• /paxportal-authorize-passenger-callback - the callback endpoint for travelID, which stores the cookie and redirects 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

See also

• Dev:PAX.Portal Application Development