/api/v1/* → behaviour change
sevdesk API
Stopped working
On April 29, 2025, sevdesk API will disable authentication using the query parameter token across all /api/v1/* endpoints. The provider announced it will remove the mechanism to pass this credential in the URL. Requests that rely on this parameter after this date will fail.
Calls it hits
/api/v1/*query parameter token
What to use instead of these calls
Send the API token in the Authorization header instead of the token query parameter.
In sevdesk API's words
we will remove the mechanism to pass the API token as a URL request parameter to authenticate at any sevDesk API endpoint.
Facts
- API
- sevdesk API
my.sevdesk.de - Kind
- Behaviour change
- Announced
- February 6, 2025
- Takes effect
- April 29, 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 /api/v1/*, query parameter token on sevdesk API stopped working on April 29, 2025.
What happens to calls after April 29, 2025?
They have failed since April 29, 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 -
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.