# API v1 stops working

Calls to /v1/* on Visma eAccounting API stopped working on June 30, 2023.

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.

## What to use instead

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}.

- API: Visma eAccounting API (eaccountingapi.vismaonline.com)
- Kind: Version retirement
- Announced: December 12, 2022
- Takes effect: June 30, 2023
- Calls after that day: fail
- Calls it hits: `/v1/*`
- Source: [Announcement](https://developer.vismaonline.com/docs/v2-migration-guide)
- Verified: October 26, 2026, against Visma eAccounting API's own pages
- Page: https://www.okapi.bot/providers/visma-eaccounting-api/breaking-changes/api-v1-stops-working/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent