PUT /v1/salesorderbasic/{} → endpoint removal
Deprecated, no date
The provider has deprecated PUT /v1/salesorderbasic/{} without a shutdown date. Calls to this endpoint will eventually fail, as the provider plans that the deprecated endpoints will be permanently disabled in the future.
Calls it hits
PUT /v1/salesorderbasic/{}
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 PUT /v1/salesorderbasic/{} 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 6
-
GET /v1/PurchaseReceiptEndpoint removal Stopped working -
GET /v1/PurchaseReceipt/{}Endpoint removal Stopped working -
GET /v1/PurchaseReceiptBasicEndpoint removal Stopped working -
GET /v1/PurchaseReceiptBasic/{}Endpoint removal Stopped working -
No date
GET /v1/salesorderEndpoint removal Deprecated, no date -
No date
GET /v1/salesorder/{}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.