Authenticate with the Concur v4 Authentication API using OAuth 2.0; Travel Request v4 does not accept legacy v1 tokens
POST to the Requests endpoint to create a new travel request with fields including business purpose, destination, travel dates, cost estimate, and the submitting user's login ID
Add travel segments to the request by POSTing to the request segments sub-resource, supplying transport mode, origin, destination, and estimated cost per segment
Move the request through the approval workflow by calling the workflow action endpoint; valid actions include submit, recall, and cancel depending on the current request status
Subscribe to the Concur Request status-changed event on the Event Subscription Service to receive asynchronous callbacks when a request is approved, rejected, or recalled by the traveler
Once a request is approved, use the approved request ID to link subsequent booking confirmations and expense reports, maintaining an auditable pre-trip-to-post-trip chain
Known gotchas
The Travel Request v4 API exposes five distinct resource types; creating a request header and adding segments are separate API calls, and omitting the segment POST results in an approved shell with no itinerary data
Approval workflow configuration is set at the Concur policy level by administrators; the API can submit and transition requests but cannot override the configured approver chain or spending thresholds
Status-changed events may fire for intermediate workflow states such as pending manager approval; build state-machine logic that ignores intermediate events and only acts on terminal states like approved or rejected
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp