Okapi Okapi
Add to GitHub

/api/v1/Invoice/{}/changeStatus → endpoint removal

sevdesk API

Deprecated, no date

The sevdesk API endpoint /api/v1/Invoice/{}/changeStatus is deprecated without an announced shutdown date. The provider announced on April 4, 2024, that the endpoint will be removed. Once removed, requests sent to /api/v1/Invoice/{}/changeStatus will fail.

Calls it hits

  • /api/v1/Invoice/{}/changeStatus

What to use instead of these calls

Update status transitions by using PUT /api/v1/Invoice/{invoiceId}/sendBy, bookAmount, resetToDraft, or resetToOpen instead.

In sevdesk API's words

/api/v1/Invoice/{invoiceId}/changeStatus (will be removed)

sevdesk API, Announcement

Facts

API
sevdesk API my.sevdesk.de
Kind
Endpoint removal
Announced
April 4, 2024
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against sevdesk API's own pages

Questions

When does this change take effect?

sevdesk API deprecated /api/v1/Invoice/{}/changeStatus without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: sevdesk 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 sevdesk API 4

  1. POST /api/v1/CheckAccountEndpoint removal Stopped working
  2. /api/v1/*Behaviour change Stopped working
  3. GET /api/v1/Export/datevCSVEndpoint removal Stopped working
  4. No date /api/v1/CreditNote/{}/changeStatusEndpoint 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.

Add to GitHub