Visma Net API
GET /v1/PurchaseReceiptBasic endpoint removal
Stopped workingSubscribe to Visma Net APIShare
On September 15, 2026, the GET /v1/PurchaseReceiptBasic endpoint was removed. Calls to this endpoint fail since that date.
Calls it hits
GET /v1/PurchaseReceiptBasic
What to use instead of these calls
Call GET /v2/PurchaseReceipt (and GET /v2/PurchaseReceipt/{receiptNumber}), which now covers PurchaseReceipt and PurchaseReceiptBasic.
In Visma Net API's words
As a result, the following endpoints will be removed on September 15th, 2026:
Facts
- API
- Visma Net API
api.finance.visma.net - Kind
- Endpoint removal
- Takes effect
- September 15, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Visma Net API's own pages
Questions
When does this change take effect?
Calls to GET /v1/PurchaseReceiptBasic on Visma Net API stopped working on September 15, 2026.
What happens to calls after September 15, 2026?
They have failed since September 15, 2026.
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/PurchaseReceiptBasic/{id}Endpoint removal Stopped working -
No date
GET /v1/salesorderEndpoint removal Deprecated, no date -
No date
GET /v1/salesorder/{id}Endpoint 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
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.