3832579 - Why Does the Travel Allowance v4 API Return No Data Even With a Valid Request ID?

The SAP Concur UI displays a short alphanumeric Request ID on the request page. Customers commonly use this short ID as the contextId parameter when calling the Travel Allowance v4 API, which results in no data being returned.

The Travel Allowance v4 API requires the requestUuid, a full UUID-format identifier that is only available through the Request v4 API response or from the URL in the browser when the request is open. These two identifiers represent the same request but are different values, and the API will silently return no results if the short UI ID is used.

When calling the Travel Allowance v4 API, customers may receive empty or no results even when providing a valid Request ID. This occurs because the Request ID visible in the Concur UI is not the same identifier required by the API. , KBA , CON-INT , Integrations , Problem