Merge pull request #2835 from concur/preview

Preview -> livesite 2021-08-17

src/_data/sidebars/api-guides.yml

@@ -24,9 +24,13 @@
 - title: Travel
   url: ''
   children:
+      - title: Duty of Care
+        url: /api-guides/travel/duty-of-care.html
       - title: Itinerary - GET Itinerary & Trip Details
         url: /api-guides/travel/get-itinerary.html
       - title: Itinerary - Add a New Itinerary Manually
         url: /api-guides/travel/new-itinerary-manual.html
+      - title: Itinerary - Business Travel Events
+        url: /api-guides/travel/itin-with-events.html
 - title: VAT Reclaim Integration
   url: /api-guides/vat-reclaim/vat-reclaim-guide.html

src/api-guides/travel/itin-with-events.markdown

@@ -6,12 +6,12 @@ layout: reference
 * [Introduction](#introduction)
 * [Data Scope](#data-scope)
 * [Event details](#event-details)
-* [Itinerary V4 API](#itinerary)
+* [Itinerary v4 API](#itinerary)
 * [References for Enumeration Types](#references)
 
 ## <a name="introduction"></a>Introduction
 
-The event driven GET Itinerary V4 API will provide a scalable solution by allowing partners to get near real time updates for trips being created, updated, cancelled, deleted, and anonymized.
+The event driven GET Itinerary v4 API will provide a scalable solution by allowing partners to get near real time updates for trips being created, updated, cancelled, deleted, and anonymized.
 
 ## <a name="data-scope"></a>Data Scope
 
@@ -27,9 +27,9 @@ The Event Subscription Service (ESS) enables the set up/creation of a subscripti
 *  [Event Subscription Management](/event-topics/index.html)
 *	 [Travel Itinerary Event](/event-topics/travel/v4.itinerary-events.html)
 
-## <a name="itinerary"></a>Itinerary V4 API
+## <a name="itinerary"></a>Itinerary v4 API
 
-Using a Company Level Token and the href from the Events payload, partners use the Itinerary V4 API endpoint to obtain trip details.
+Using a Company Level Token and the `href` from the Events payload, partners use the Itinerary v4 API endpoint to obtain trip details.
 
 Schema and Sample API Request and Response can be found in:
 
@@ -39,7 +39,7 @@ Schema and Sample API Request and Response can be found in:
 
 ## <a name="References"></a>References for Enumeration Types
 
-#### Itin Source  Names
+#### Itinerary Source  Names
 
 >**Note**: The source name appears both at the Itinerary level and the Booking level.  The value at the Booking level is generally more useful.  The value at the Itinerary level represents that value of the first booking added to the Itinerary and could therefore be misleading.
 

src/api-reference/request/v4.endpoints.agency proposal-resources_EA version.markdown

@@ -611,11 +611,11 @@ Name|Type|Format|Description
 `agencyProposalType`|`string`|-|**Required** The agency proposal type value. Supported value: `API`.
 `importDate`|`timestamp`|`YYYY-MM-DDThh:mm:ss.SSS'Z`|**Read only** The date of the import.
 `proposalUuid`|`string`|-|**Read only** The unique identifier of one proposal for a Request.
-`providerMessageId`|`string`|-|The unique identifier of the client’s batch of proposal.
+`providerMessageId`|`string`|-|The unique identifier of the client’s batch of proposal.
 `proposalBatchSize`|`integer`|-|**Required** Size of the client’s batch of proposal. <br>Note: If this value is greater than 1, the Request will not be sent back to the traveler as long as the expected number of proposals (respective proposalOrder) are not integrated into the Request.
 `proposalOrder`|`integer`|-|**Required** Sequence order of the proposal for the request.
 `booked`|`boolean`|-|**Required** If `true`, this trip is (or has to be) handled by a travel agency.
-`approvalLimitDate`|-|`yyyy-MM-dd'T'HH:mm:ss.SSS'Z'`|Limit approval date of the proposal. Past this date, the proposal will not be viable any more.
+`approvalLimitDate`|-|`yyyy-MM-dd'T'HH:mm:ss.SSS'Z'`|Limit approval date of the proposal. Past this date, the proposal will not be viable any more.
 `status`|`string`|-|**Required** Supported values: `PROPOSAL`,`CONFIRMED`,`TICKETISSUED`.
 `proposal`|`boolean`|-|**Read only** If `true`, this proposal is still in the `PROPOSAL` status.  If `false`, the proposal status is `CONFIRMED` (tickets issued).
 `comments`|`string`|-|Free text.
@@ -671,7 +671,6 @@ Name|Type|Format|Description
 `flightNumber`|`string`|-|**Required** The flight number for the booking.
 `seatNumber`|`string`|-|The number of the seat.
 `aircraft`|`string`|-|The code of the aircraft type.
-`mealPreference`|`string`|-|The booked meal.
 `departureTerminal`|`string`|-|The departure terminal for the air segment leg.
 `arrivalTerminal`|`string`|-|The arrival terminal for the air segment leg.
 `startLocation`|`object`|[`Location`](#schema-location)|**Required** The start location of the air segment leg (Air location schema).
@@ -692,7 +691,6 @@ Name|Type|Format|Description
 `endRailStation`|`string`|-|The code for the ending station of the segment leg.
 `endRailStationName`|`string`|-|The name of the ending station of the segment leg.
 `endLocation`|`object`|[`Location`](#schema-location)|**Required** The end location of the rail segment leg (Rail location schema).
-`mealPreference`|`string`|-|The booked meal.
 
 ### <a name="schema-agencyproposalcarsegment"></a>Agency proposal car segment
 

src/tools-support/deprecation-policy.markdown

@@ -5,6 +5,8 @@ layout: reference
 
 The API Lifecycle & Deprecation Policy is part of our [API terms and conditions of use.](/Terms-of-Use.html) We may make periodic updates to this policy, at which time we will notify those who have agreements with us.
 
+>**NOTE**: For the policy that applies to APIs deprecated prior to August 2021, see: https://developer.concur.com/tools-support/deprecation-policy-legacy.html.
+
 ## API Version Status  
 
 * **Active:** An active API version is the most current and fully supported API. It is the recommended version for everyone to use.