Okapi Okapi

SAP Concur API DELETE /api/v3.0/expense/entries/{id} endpoint removal

Deprecated, no dateSubscribe to SAP Concur APIShare

SAP Concur API deprecated DELETE /api/v3.0/expense/entries/{id} without giving a shutdown date yet.


Calls it hits

  • DELETE /api/v3.0/expense/entries/{id}

What to use instead of these calls

Delete the unsubmitted expense with the Expenses v4 API.

In SAP Concur API's words

Effective June 26, 2025, Expense v3 DELETE was deprecated. This has been replaced by Expense v4 Delete. Decommission will follow.

SAP Concur API, Announcement

Facts

API
SAP Concur API us.api.concursolutions.com
Kind
Endpoint removal
Announced
June 26, 2025
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against SAP Concur API's own pages

Questions

When does this change take effect?

SAP Concur API deprecated DELETE /api/v3.0/expense/entries/{id} without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: SAP Concur API has not given a shutdown date yet.

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

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

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.