{"introduction":"This document provides a reference to the SSO Context API. This document includes a series of notes and instructions that outline the ContextAPI.","audience":{"label":"Audience","description":"This document is aimed for the Egencia SSO Context API customers, partners and software developers who would like to consume the SSO Context API."},"overview":{"label":"Overview","description":"The SSO Context API is a set of APIs that allow you to quickly create a trip by pre-populating the corresponding fields, such as search form data (from, to, departure date, arrival date), or custom data fields (also known as analytics data) in the Egencia booking page. This document will help you to find links to different API Endpoints for context data management."},"versioning":{"versions":[{"id":"2.0","change_description":"New version of the API with additional search parameters."},{"id":"1.0","change_description":"First stable version."}]},"error_codes":[],"api_details":{"label":"SSO Context API","description":"Egencia SSO Context API (current) is created to provide proactive as well as on-demand contextual data to various platform services to serve you better in a more informed manner.\n The Partner Specific contextual data can be classified as Data which includes Traveler Demographics, Loyalties, Profiles, Bookings Data, Communications/Notifications - Booking/Cancellation Email Confirmations to travelers etc. \n The SSO Context API allows you to transfer context data during the authentication. \n When provided, the Context data will be pre-populated in the corresponding fields, such as search form data (from, to, departure date, arrival date), or custom data fields (also known as analytics data). The pre-populated data will appear in the checkout and it will flow back to the.originating system through Expense SPI. \n Context data includes \"TravelRequest\", \"PurchaseOrder\", \"MissionOrder\". Providing this data during authentication in a Custom Data Field will include this data in the downstream API, data feeds or receipt/invoice.","subheadings":[{"label":"Implementation Method","description":"Follow the below steps:\n\t 1. The vanity URL is defined by Egencia and you will provide IDP (either by the client or one of our partner.)\n\t 2. The API call is made using this vanity URL + the booking context (For example: https://customerabc.egencia.be/<booking context parameters>) \n\t 3. Egencia's Auth component will detect the vanity URL \n\t 4. Auth triggers a SAML Request to the configured IDP \n\t 5. Once the authentication is done, Auth redirects to the home page pre-populated with the context. \n\t So, to open a new tab redirecting to Egencia while including the context, you just have to have an IDP (for test) and use the vanity URL in your Call To Action."}]},"enumerations":{"Itinerary Type":[{"name":"RT","description":"Return trip - Default value if Itinerary type is not provided"},{"name":"OW","description":"One way"}],"Product Type":[{"name":"FLIGHT","description":"AIR - Line of Business"},{"name":"TRAIN","description":"RAIL - Line of Business"},{"name":"HOTEL","description":"HOTEL - Line of Business"},{"name":"CAR","description":"CAR - Line of Business"}],"Custom Data Fields":[{"name":"COST_CENTER_1","description":"Cost Center 1"},{"name":"COST_CENTER_2","description":"Cost Center 2"}]},"documentation_link":"https://apis.egencia.com/openconnect-sso/docs/api-docs/sso"}