POST /api/v1/CheckAccount → endpoint removal
sevdesk API
Stopped working
On September 17, 2024, the sevdesk API removed the POST /api/v1/CheckAccount endpoint. Calls made to this endpoint fail following this removal. The change was announced on July 4, 2024, planning the endpoint's removal for version 4.188.
Calls it hits
POST /api/v1/CheckAccount
What to use instead of these calls
Create check accounts with POST /api/v1/CheckAccount/Factory/fileImportAccount or POST /api/v1/CheckAccount/Factory/clearingAccount instead.
In sevdesk API's words
The old endpoint is marked deprecated and removal is planned for 17.09.2024 (4.188)
Facts
- API
- sevdesk API
my.sevdesk.de - Kind
- Endpoint removal
- Announced
- July 4, 2024
- Takes effect
- September 17, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against sevdesk API's own pages
Questions
When does this change take effect?
Calls to POST /api/v1/CheckAccount on sevdesk API stopped working on September 17, 2024.
What happens to calls after September 17, 2024?
They have failed since September 17, 2024.
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 sevdesk API 4
-
/api/v1/*Behaviour change Stopped working -
GET /api/v1/Export/datevCSVEndpoint removal Stopped working -
No date
/api/v1/CreditNote/{}/changeStatusEndpoint removal Deprecated, no date -
No date
/api/v1/Invoice/{}/changeStatusEndpoint 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.