Developer Platform Release Notes

2017 2016 2015 2014
February February
April April
May May
June
July
August
October

App Center Release Notes

2017 2016 2015 2014
January January
February February February  
May      
July      
August      
September      
October      
March March
April
May May May
June June
July July July
August August
September September September
October October October
November November
December December December

Combined App Center and Developer Platform Release Notes

Release Month
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013

Release Notes

April 2016

Travel: Form of Payment 1.0 Deprecated

Effective May 1, 2016, Form of Payment 1.0 API will be deprecated. Issues will continue to be addressed for this API until Nov. 1, 2016. After that date, no new issues will be addressed and the API will be retired. Therefore, we encourage all current users to migrate to version 2.0 as soon as possible. Please note that after the API is in a retired state and there are three consecutive months of inactivity, the API will be decommissioned and no longer available.

Please refer to our deprecation policy for definitions additional information.


February 2016

Travel Profile 1.0 Deprecated

Effective May 1, 2016, the Travel Profile 1.0 API will be deprecated. Issues will continue to be addressed for this API until Nov. 1, 2016. After that date, no new issues will be addressed and the API will be retired. Therefore, we encourage all current users to migrate to version 2.0 as soon as possible. Please note that after the API is in a retired state and there are three consecutive months of inactivity, the API will be decommissioned and no longer available.

Please refer to our deprecation policy for definitions additional information.


August 2015

Form of Payment API Version 2.0

Overview Concur offers a profile API, which passes profile data from Concur to third parties. With this release, we have separated the form of payment section from profile. In addition, we now support corporate ghost cards to be passed to 3rd party vendors, such as TripLink vendors and fulfillment TMCs.

In order to ensure all existing partners are not affected by this change, we are going to offer a new version of the Form of Payment API with a new endpoint.

Concur’s deprecation policy requires everyone to move off the existing version within twelve months. Once the new endpoint is in place, changes to both versions will be supported for six months. After six months, changes will only occur in the new end point (2.0).

Please Note: Concur will continue to add new elements/values as we see fit. It is imperative that partners are aware of this and program accordingly to avoid challenges when the new elements/values are introduced.

Changes in v2.0 of Travel FOP API GET
Below is a list of changes with version 2.0. Concur strongly recommends that vendors/partners begin coordinating with their development team to take advantage of this new endpoint.

Schema changes

  • New endpoint: /api/travelprofile/v2.0/FOP

  • Sunset endpoint: /api/travelprofile/v1.0/FOP

  • Move FOP scope out of the Travel Profile scope so it operates independently

  • Concur will pass a flag to note whether the card is personal or company ghost

  • New scope under the FOP scope called Company Ghost Cards

    • Card type
    • Card number
    • Card expiration date
    • Card billing address
    • Card name
    • Flag that denotes whether the card is mandatory (no other card can be used) or not
    • Flag that denotes whether the card should be the default

Schema Additions

  • Documentation will be provided closer to the delivery date

Configuration for Professional and Standard Travel To take advantage of the new version of the Form of Payment API, partners need to code to the new endpoints.


Concur Request 3.1

This service is known as Authorization Request, Concur Request, or simply Request and was formerly known as Travel Request. Concur changed the name to better align with its broader capabilities. This service is different from the legacy authorization request feature that was available within Concur Expense.

Overview: Concur is exposing a new endpoint providing the ability for a client vendor to create a Request on behalf of the actual Request user.

This new feature is for instance highly beneficial when an employee plans a trip and needs to request the authorization to travel. A Travel Request has to be created and submitted to the manager. However, as the user is on the road and plans to depart tomorrow, this individual decides to call the TMC to obtain a reservation right away. The TMC will first generate a Request on behalf of this traveler, and then associate the booking to this Request, so that the manager can easily review all the trip details and decide to approve or reject.

Details: In version 3.1, the Post Request Header endpoint now has a “User” element to designate the user on behalf of which the Request will be created. The API consumer, as the Request creator, has to be granted the Proxy Logon user role.

Effective Date: August 2015


July 2015

Travel API

Travel Profile API Changes

Overview: New elements added to the Travel Profile API

Additions:

  • Rail Preferences
  • Rail Loyalty Programs
  • National ID

Effective Date: July 2015 release

Overview: Changes to the APIs and Scopes for Travel Profile API in Register/Modify Partner Application

Change 1:

  • Removed: Form of Payment scope from Travel Profile API
  • Added: Form of Payment API

Change 2:

  • Removed: Driver’s License and Rate Preference
  • Moved: Custom Fields under Company Details

Effective Date: July 2015 release