![]()
us.api.concursolutions.com · FinanceSubscribeShare
SAP Concur API breaking changes
The breaking changes SAP Concur API announced that Okapi tracks: 11 in all.
Do you run the SAP Concur API? Make sure your users call it right →
At a glance
- API host
us.api.concursolutions.com- Kind
- Finance
- Versions with breaking changes
- v3.0 (9), v1.0 (1), v1.1 (1)
- Breaking changes tracked
- 8 breaking changes with no date yet and 3 already in effect
- Last updated
Deprecated, no date yet 8
-
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/v3.0/expense/attendees/*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
Already in effect 3
-
/api/travelrequest/v1.0/*Version retirement Stopped working -
/api/v3.0/travelrequest/*Version retirement Stopped working -
/api/v3.0/common/users*Version retirement Stopped working
Where Okapi reads it
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub