sevdesk API
GET /api/v1/Export/datevCSV endpoint removal
Stopped workingSubscribe to sevdesk APIShare
Calls to GET /api/v1/Export/datevCSV on sevdesk API stopped working on May 30, 2025.
Calls it hits
GET /api/v1/Export/datevCSV
What to use instead of these calls
Start the export with GET /api/v1/Export/createDatevCsvZipExportJob instead. Once the job finishes, download the ZIP using GET /api/v1/ExportJob/jobDownloadInfo.
In sevdesk API's words
we will remove our existing endpoint to access the DATEV export as ZIP file and introduce new endpoints to access the DATEV export via API.
Facts
- API
- sevdesk API
my.sevdesk.de - Kind
- Endpoint removal
- Announced
- March 20, 2025
- Takes effect
- May 30, 2025
- 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 GET /api/v1/Export/datevCSV on sevdesk API stopped working on May 30, 2025.
What happens to calls after May 30, 2025?
They have failed since May 30, 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 sevdesk API 4
-
POST /api/v1/CheckAccountEndpoint removal Stopped working -
/api/v1/*Behaviour change Stopped working -
No date
/api/v1/CreditNote/{id}/changeStatusEndpoint removal Deprecated, no date -
No date
/api/v1/Invoice/{id}/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.