Concur Request Event


This page will host the documentation for all the Concur Request related events that are publicly available on the public.concur.request topic in the Event Subscription Service (ESS). Subscribers will be able to subscribe to these events by following the steps described on the Event Subscription Service v4 page.

Concur Request related events are relevant for applications that are interacting with travelers before they book their trip, such as applications that context to the traveler regarding company policy, preferences, or general compliance requirements for booking travel.


This event subscription is only available to partners who have been granted access by SAP Concur. Access to this documentation does not provide access to the subscription.

Scope Usage

Name Description
travelrequest.write Read and write Requests.


This section lists all the publicly available events.

Request Status Changed Event

The statusChanged event is intended to publish a message whenever the status of a Request changes as it traverses the approval workflow during its life cycle. Subscribers of the event are able to leverage the data in the message to perform synchronous or asynchronous actions depending on their business processes. For example, this could trigger an application to make API calls to Concur Request or start of a process in a third party application.

The statusChanged event will always be published for the following status changes without any additional configuration:

  • Whenever a Request is submitted.
  • Whenever a Request is sent back to the employee by an approver/processor.
  • Whenever a Request is recalled by the employee.
  • Whenever a Request is closed.
  • Whenever a Request is reopened.
  • Whenever a Request is cancelled.
  • Whenever a Request is approved.
  • Whenever a Request stops in the legacy external validation step that is. configured using the application connector.

In addition to the above, any workflow step configured for notifications by the administrator will also be published. Please refer to the Procedure: Creating External Validations and Workflow Event Notifications section of the Workflow General - Setup Guide for more information on how the events can be configured and optimized.


status Changed Event Payload Schema

Name Type Format Description
id string UUID Randomly generated unique identifier of this the event.
correlationId string UUID SAP Concur unique identifier used for logging/traceability.
eventType string - statusChange for Request workflow updates.
Approved: statusChange.APPROVED
Canceled: statusChange.CANCELED
Sent Back / Recalled: statusChange.SENTBACK
TMC agent (REQ_PROCESSOR1): statusChange.PENDING.TMC
Request Manager (REQ_MANAGER): statusChange.PENDING.RequestManager
Request Auditor (REQ_PROCESSOR3): statusChange.PENDING.RequestAuditor
Cost Object Approver (CO_APPROVE): statusChange.PENDING.CostObjectApprover
Authorized Approver (AUTH_APPROVE): statusChange.PENDING.AuthorizedApprover
Budget approver/manager (BDGT_APPROVE): statusChange.PENDING.BudgetManager
Risk Manager (RISK_PROCESSOR): statusChange.PENDING.RiskManager
Request Administrator (REQ_PROCESSOR_2): statusChange.PENDING.RequestAdministrator
External validation: statusChange.PENDING.ExternalValidation
Custom status: statusChange.PENDING.role (part of workflow roles)
topic string - Topic name for subscription. Supported value: public.concur.request
subTopic string - Do not use.
timeStamp string date/time The date the event was generated in UTC.
groups string UUID travelAgencyUuid linked to the Request.
scopes string - Supported value: travelrequest.write
facts map Request Facts Key-value pairs providing the content of the event.

Status Changed Facts Schema

Name Type Format Description
href string - Hyperlink to the v4 API resource for this Request (based on datacenter).
id string - Unique identifier of the Request.
requestId string - Public key of the Request (unique per customer). This corresponds to the short ID of the Request (alphanumeric).
companyId string - Unique identifier of the company of the traveler, from the profile service.
role string - TMC agent: TMC
Request Manager: RequestManager
Request Auditor: RequestAuditor
Cost Object Approver (COA): CostObjectApprover
Authorized Approver: AuthorizedApprover
Budget approver/manager: BudgetManager
Risk Manager: RiskManager
Request Administrator: RequestAdministrator
External validation: ExternalValidation
currentApprovalStatus string - Pending TMC agent: numerical (example 002003)
Pending Request Manager: Q_PEND
Pending Request Auditor: Q_PEND
Pending Cost Object Approver: Q_PECO
Pending Authorized Approver: Q_PEND
Pending Budget approver/manager: Q_PBDG
Pending Risk Manager: Q_PEND
Pending Request Administrator: Q_PEND
Pending External validation: Q_EXTV
Pending Custom step: numerical
policyId string - Unique identifier of the policy that applies to the Request.
actingUserId string - Unique identifier of the user performing the action. This is not displayed if the action is performed by the Request owner.
userId string - Unique identifier of the owner of the Request.
recipientId string - Unique identifier of the user to whom the Request is pending approval. This is not displayed if the Request is, for example, approved or pending a generic step such as TMC step.
isClosed boolean true/false If true, the Request is at the CLOSED status.
isTest boolean true/false If true, the user is a test user.
isRecall boolean true/false Is true only if the Request is at the SENDBACK status related to a recalled action from the traveler/delegate.
status string enum Approved: APPROVED
Canceled: CANCELED
Sent Back / Recalled: SENTBACK
Pending TMC agent: PendingTMCApproval
Pending Request Manager: PendingRequestManagerApproval
Request Auditor: PendingRequestAuditorApproval
Pending Cost Object Approver: PendingCostObjectApproverApproval
Pending Authorized Approver: PendingAuthorizedApproverApproval
Pending Budget approver/manager: PendingBudgetManagerApproval
Pending Risk Manager: PendingRiskManagerApproval
Pending Request Administrator: PendingRequestAdministratorApproval
Pending External validation: PendingExternalValidation
stepCode String enum Code provided by the admin that the client can use to differentiate between the steps.
Request Submit: if the target step (the next workflow step that the request stops at) is not configured for notifications, then step code will be NULL.
Request Send Back or Request Recall - SENDBACK
Legacy External validation post submit - EXTVAL
Legacy External validation pre-extract - EXTVAL
All other cases code step code as configured by admin in workflow configuration will be populated.
entityId String alphanumeric Unique Identifier of the Concur Entity. A valid EntityID pattern is [pdt][a-zA-Z0-9] {5,31}. It starts with p - production / d - demo/ t- test. It consists of a-zA-Z0-9 with length at least 5 but no more than 31 characters.
isPaymentCardRelated boolean true/false Is true only if the Request has at least one of its expected expense entry with the field isPaymentCardRelated selected by the end user.

Sample Events


On this page