/v1/* → version retirement
Visma eAccounting APIStopped working
On June 30, 2023, Visma eAccounting API retired version 1. Calls to /v1/* endpoints stopped working and fail after that date. The provider deprecated the version to make room for technical improvements and future API releases.
Calls it hits
/v1/*
What to use instead of these calls
Call the corresponding V2 endpoint under /v2/. Every V1 endpoint has an equivalent in V2, such as GET /v2/accountbalances/{date} replacing GET /v1/accountbalances/{date}.
In Visma eAccounting API's words
Visma eAccounting API V1 has been publicly available for many years, but from 30th of June 2023 it’s time to say goodbye. It’s been more than four years since we released V2 and the vast majority of users consume the latest version of the API. In order to make room for technical improvements and future versions of the API, we are deprecating V1.
Facts
- API
- Visma eAccounting API
eaccountingapi.vismaonline.com - Kind
- Version retirement
- Announced
- December 12, 2022
- Takes effect
- June 30, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Visma eAccounting API's own pages
Questions
When does this change take effect?
Calls to /v1/* on Visma eAccounting API stopped working on June 30, 2023.
What happens to calls after June 30, 2023?
They have failed since June 30, 2023.
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.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.