Concur Request automates the spend request and approval process for both travel and everyday expenses, giving you the data you need to accurately track and better control spending. By increasing visibility into planned expenses and up-to-date budget data, you can make strategic spending decisions before any spending actually occurs. The Request API provides many possibilities, particularly Requests creation and transition into the approval workflow.

Version 4.0 of Request API works only with the new Authentication API.

Get Started

• Overview
• Version
• Process Flow
• Products and Editions
• Scope Usage
• Dependencies
• Access Token Usage
• Request
• Workflow
• Expected Expense
• Request Policy
• Travel Agency
• Schema
• HTTP Status Codes
• Run in Postman

Overview

The Request v4 API exposes five different resources:

Resource	Description
Request	You can read, create, update or delete a Request and get the list of existing Requests.
Workflow	You can perform action in the approval workflow of a Request (submit, approve, cancel…)
Expected Expense	You can read, create, update or delete an expected expense, and get the list of expected Expenses for a specific Request.
Request Policy	You can get the list of existing Request policies.
Travel Agency	You can get the description of a Travel Agency office.

These resources are used to manage documents used for pre-spend authorizations within Concur Request.

Version

• Prior Versions
  • 3.0
  • 1.0

Process Flow

Products and Editions

• Concur Request Professional Edition
• Concur Request Standard Edition

Scope Usage

Name	Description	Endpoint
travelrequest.write	Read and write Requests	GET, POST, PUT, DELETE

Dependencies

SAP Concur clients must purchase Concur Request in order to use this API. This API requires the following additional SAP Concur APIs:

• List, to retrieve the listId
• User profile, to retrieve the userId
• Expense Report, to retrieve the reportId

Access Token Usage

This API supports both company level and user level access tokens.

Company Access Token

• The userId parameter is required to provide the user identity of who made the API call.
• Does not have an associated role.

User Access Token

• The userId parameter is not required.
• Requires the Web Service Admin role to call the API.