Visma Net API
GET /v1/salesorder/{id} endpoint removal
Deprecated, no dateSubscribe to Visma Net APIShare
Visma Net API has deprecated GET /v1/salesorder/{id} without announcing a final shutdown date. Calls hitting this endpoint will be permanently disabled in the future and will fail. Developers relying on this call should prepare for its eventual removal.
Calls it hits
GET /v1/salesorder/{id}
What to use instead of these calls
Move to the SalesOrder V3 API (the Sales Order Service API), which covers all necessary features.
In Visma Net API's words
Final Shutdown: The deprecated endpoints will be permanently disabled in the future.
Facts
- API
- Visma Net API
api.finance.visma.net - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Visma Net API's own pages
Questions
When does this change take effect?
Visma Net API deprecated GET /v1/salesorder/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Visma Net 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 Visma Net API 10
-
GET /v1/PurchaseReceiptEndpoint removal Stopped working -
GET /v1/PurchaseReceipt/{id}Endpoint removal Stopped working -
GET /v1/PurchaseReceiptBasicEndpoint removal Stopped working -
GET /v1/PurchaseReceiptBasic/{id}Endpoint removal Stopped working -
No date
GET /v1/salesorderEndpoint removal Deprecated, no date -
No date
GET /v1/salesorder/{id}/{id}Endpoint removal Deprecated, no date -
No date
GET /v1/salesorder/{id}/{id}/commissionsEndpoint removal Deprecated, no date -
No date
GET /v1/salesorder/{id}/{id}/rotrutEndpoint removal Deprecated, no date -
No date
GET /v1/salesorderbasicEndpoint removal Deprecated, no date -
No date
GET /v1/salesorderbasic/{id}Endpoint 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.