Mule Concur Connector

Thanh Nguyen

Introduction

• Concur is a SaaS provider from SAP for integrated travel and expense management solutions.

• Anypoint™ Connector for Concur operates as a bi-directional gateway between instances of Concur and Mule

• closed-source connector that supports SOAP and REST calls to various Concur APIs

Prerequisites

• Developer Sandbox or other valid Concur account

• MuleSoft Enterprise License

Namespace and Schema<mule xmlns:concur="http://www.mulesoft.org/schema/mule/concur" ... xsi:schemaLocation="http://www.mulesoft.org/schema/mule/concur http://www.mulesoft.org/schema/mule/concur/current/mule-concur.xsd"> ... <flow name="yourFlow"> ... </flow> </mule>

Using the Connector in a Mavenized Mule App

Attendee

• Attendee List: POST– Batches have a maximum size of 1000, and

anything above a size 1000 is ignored. The connector will throw an exception if a batch of size > 1000 items is submitted

Attendee

• Attendee List: POST– This API is fully supported under "Batch Attendee

List“– All Attendee List operations are managed in

batches, with a supplied Batch Type parameter determining if the batch should be CREATE-ed or UPDATE-ed

Attendee

• Attendee: GET– Fully supported as GET Attendee Details endpoint

• Attendee Type: GET– Fully supported.

Expense

• Posting expense report information is a multi-stage process

• Expense Entry Attendee: GET– Fully Supported.

• Expense Entry Attendee: POST– v1.1 of this API is supported, and operates in a

Batch.

Introduction

• Expense Entry: GET• Expense Entry: POST– Posts an expense entry for a given report, after a

report header has been created• Expense Report Header: POST– This API works in both single header and batch

modes

Introduction

• Expense Report: GET– GET List of Reports is supported, with a large

number of (all optional) search filters as parameters

• Expense Report: POST– Expense Report Submit is supported. Expense

Report Workflow actions are not supported at this time

Extract

• Extracts are not available in the Mule Connector

• Alternative integration means. There are no plans to support this resource

Image

• The imaging v3.0 APIs are mostly supported in JSON mode

• PUT and DELETE Operations are not supported at this time as during development the endpoints did not work as documented

Itinerary

• Itineraries are only partially supported. POST Itinerary Cancellations do not return valid XML

• Cannot be parsed and thus are not supported

Bookings

• Bookings are only partially supported• POST Booking Cancellations returns HTTP 404• Cannot be parsed and thus are not supported

Bookings

• Itinerary: GET– All APIs are supported: Get List of Itineraries, Get

Itinerary Details• Booking: POST– The bookings endpoints are not currently

supported.• Itinerary: POST– POST operations are not supported for Itineraries

at this time.

List Items

• List: GET– All APIs are supported: Get List of Lists, Get List

Details, Get List Items• List: POST– List updates are managed in batches, with a batch

type parameter determining if the list change will be Create, Update or Delete

– Batch limits are not discussed or tested, but it is safe to assume that batches must be less than 1000 or will be ignored, as with other batch API endpoints

Meeting

• Meeting endpoints are only supported in Travel for Concur Professional/Premium

• These APIs are not supported by the Anypoint Concur Connector

Payment Batch File

• GET List of Payment Batches is supported, with an optional status filter parameter

• POST Payment Batch Close is also supported, requiring the appropriate BatchID to be supplied.

Purchase Order Web Service

• Purchase Order endpoints are only supported in Invoice for Concur Professional/Premium

• These APIs are not supported by the Mule Connector

Quick Expenses

• Quick Expense v3.0 APIs are supported, using JSON as the interchange format

• All endpoints are supported: GET all quickexpenses, GET QuickExpense by ID, Create a new QuickExpense (POST), Update a QuickExpense by ID (PUT), and DELETE a QuickExpense by ID

Travel Request

• Travel Requests are only partially supported, as an integrator must partner with Concur as an appropriate organization type

• GET Travel Request Details is not supported, nor is POST Travel Request Workflow Action. GET List of Travel Requests is supported, however

Travel Profile

• Travel Profile APIs are fully supported

Trip Approval

• POST Trip Approval (the only API) is supported• This updates a Trip Approval as either

approved or rejected

User

• GET Employee Form Field– Get List of Employee Form Fields is supported.

• User: GET– Get User Information is fully supported.

• User: POST– POST New or Updated users is fully supported. The

batch can only support up to 500 users.• User Password: POST– Updates passwords for up to 500 users.

TripIt from Concur

• TripIt from Concur has not been considered in building the Mule Connector for Concur

Developer Preview APIs

• There are some APIs which are considered "Developer Previews“

• Connector support for these has not been added at this time due to the likelihood of significant API changes

Callouts

• Callouts are not available in the Concur connector

• Using the standard endpoint tools available in Mule, you will be able to integrate callouts

Question and answer