SAP Concur API
Attendees v3 API removal
Deprecated, no dateSubscribe to SAP Concur APIShare
SAP Concur API deprecated /api/v3.0/expense/attendees/*, /api/v3.0/expense/attendees without giving a shutdown date yet.
Calls it hits
/api/v3.0/expense/attendees/*/api/v3.0/expense/attendees
What to use instead of these calls
Manage attendees with the Attendees v4 API.
In SAP Concur API's words
Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
Facts
- API
- SAP Concur API
us.api.concursolutions.com - Kind
- Removal
- Announced
- July 1, 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 /api/v3.0/expense/attendees/*, /api/v3.0/expense/attendees 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
-
/api/v3.0/common/users*Version retirement Stopped working -
/api/travelrequest/v1.0/*Version retirement Stopped working -
/api/v3.0/travelrequest/*Version retirement Stopped working -
No date
DELETE /api/v3.0/expense/entries/{id}Endpoint removal Deprecated, no date -
No date
/api/v3.0/expense/attendeetypes*Removal Deprecated, no date -
No date
/api/expense/expensereport/v1.1/CardCharges*Removal Deprecated, no date -
No date
/api/v3.0/expense/expensegroupconfigurations*Removal Deprecated, no date -
No date
GET /api/v3.0/insights/latestbookings*Removal Deprecated, no date -
No date
/api/v3.0/common/locations*Removal Deprecated, no date -
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.