Okapi Okapi
Add to GitHub

SAP Concur API /api/v3.0/travelrequest/* version retirement

Stopped workingSubscribe to SAP Concur APIShare

On November 3, 2026, the Request v3 API was retired and became no longer accessible. This change affects calls to the /api/v3.0/travelrequest/* endpoints. Requests to these paths fail since that date.

Calls it hits

  • /api/v3.0/travelrequest/*

What to use instead of these calls

Call the Request v4 API (/travelrequest/v4/requests) instead.

In SAP Concur API's words

As previously announced, the Concur Request APIs v1.0, v3.0, and v3.1 have been decommissioned. These versions will be retired and no longer accessible as of November 3, 2026.

SAP Concur API, Announcement

Facts

API
SAP Concur API us.api.concursolutions.com
Kind
Version retirement
Announced
February 4, 2026
Takes effect
November 3, 2026
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against SAP Concur API's own pages

Questions

When does this change take effect?

Calls to /api/v3.0/travelrequest/* on SAP Concur API stopped working on November 3, 2026.

What happens to calls after November 3, 2026?

They have failed since November 3, 2026.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

More from SAP Concur API 10

  1. /api/v3.0/common/users*Version retirement Stopped working
  2. /api/travelrequest/v1.0/*Version retirement Stopped working
  3. No date DELETE /api/v3.0/expense/entries/{id}Endpoint removal Deprecated, no date
  4. No date /api/v3.0/expense/attendeetypes*Removal Deprecated, no date
  5. No date /api/v3.0/expense/attendees/*Removal Deprecated, no date
  6. No date /api/expense/expensereport/v1.1/CardCharges*Removal Deprecated, no date
  7. No date /api/v3.0/expense/expensegroupconfigurations*Removal Deprecated, no date
  8. No date GET /api/v3.0/insights/latestbookings*Removal Deprecated, no date
  9. No date /api/v3.0/common/locations*Removal Deprecated, no date
  10. No date GET /api/v3.0/insights/opportunities*Removal Deprecated, no date

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub

Get notifications

Subscribe to SAP Concur API

Hear about each breaking change SAP Concur API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • SAP Concur API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.