Okapi Okapi

SAP Concur API /api/v3.0/common/users* version retirement

Stopped workingSubscribe to SAP Concur APIShare

Calls to /api/v3.0/common/users* on SAP Concur API stopped working on January 21, 2025.


Calls it hits

  • /api/v3.0/common/users*

What to use instead of these calls

Read and provision users with the User Provisioning Service v4 (/profile/v4/Users) or Identity v4.1.

In SAP Concur API's words

Decommissioned: User v1 and V3 APIs Effective Date: January 21, 2025 The User v1 API has been officially decommissioned and is no longer supported.

SAP Concur API, Announcement

Facts

API
SAP Concur API us.api.concursolutions.com
Kind
Version retirement
Announced
January 9, 2025
Takes effect
January 21, 2025
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/common/users* on SAP Concur API stopped working on January 21, 2025.

What happens to calls after January 21, 2025?

They have failed since January 21, 2025.

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/travelrequest/v1.0/*Version retirement Stopped working
  2. /api/v3.0/travelrequest/*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.