# Visma eAccounting — Accounting API: connection > Canonical URL: https://developers.apideck.com/apis/accounting/visma-eaccounting/connection # How to connect to Visma eAccounting Visma eAccounting connects over **OAuth 2.0**: you sign in with your normal Visma Online login, choose the company you want to share, and approve access. There is nothing to copy and paste: **no API key, no client id, no company id** to look up beforehand. The whole connection takes a minute. Visma has rebranded the product to **Spiris**, so you may see either name on the sign-in and consent screens. It is the same service and the same login. --- ## Prerequisites - An **active eAccounting subscription** (Norway, the Netherlands) or **Bokföring & Fakturering** (Sweden). - Your **Visma Online** login, the same email and password you use at [eaccounting.vismaonline.com](https://eaccounting.vismaonline.com). - Access to the company you want to connect. No specific administrator role is documented for this authorization, but the login you use must be able to open the company in Visma Online, and the connection can only reach the data that login can reach. If your login opens more than one company, decide up front which one you are connecting: you pick it during the authorization step, and each company needs its own connection. --- ## Steps 1. Open the integration settings in the application you are connecting from and start the **Visma eAccounting** connection. This opens Apideck Vault. 2. Click **Authorize**. Vault redirects you to the Visma sign-in page at `identity.vismaonline.com`. 3. **Sign in** with your Visma Online email and password, and complete two-factor verification if your account uses it. 4. **Select the company** you want to grant access to. If your login only has one company, Visma may skip this screen. 5. Review the access being requested and **approve** it. Visma asks for permission to read and write your sales (invoices, customers), purchase (supplier invoices) and accounting (vouchers, accounts) data, and to keep the connection authorized so it does not have to ask you again every hour. 6. Visma sends you back to Apideck. The connection status changes to **Connected** and you are done. There are no fields to fill in afterwards. Everything the connection needs, including which company it points at, comes from the authorization you just completed. --- ## Notes - **One connection per company.** The authorization is scoped to the single company you selected. To sync a second company, create a second connection and select that company when you authorize. - **Changing your Visma Online password breaks the connection.** See Troubleshooting below: this is the single most common cause of a connection that "was working yesterday". - **The consent screen shows the application you are connecting from**, or "Apideck" if the application is still using Apideck's shared test credentials. Either is expected. - **You can revoke access from Visma at any time.** Disconnecting the application on the Visma side invalidates the stored token, but Apideck is not notified when you do it: like a password change, the connection keeps looking healthy until the next data sync fails. Authorize again from Vault when you want to restore it. --- ## Troubleshooting ### The connection worked and then suddenly started failing **Check whether your Visma Online password was changed recently, including by a routine reset or a password-policy expiry.** Changing the password on the Visma Online account that authorized the connection **silently invalidates** the stored refresh token. Visma gives no notification and the connection keeps looking healthy in the meantime; the failure only surfaces on the next data sync. Fix: open the connection in Vault and click **Reauthorize** (or disconnect and connect again), sign in with the new password, and select the same company. Nothing else needs to be reset. If you rotate that password on a schedule, expect to reauthorize each time, or authorize with an account whose password is more stable. ### Sign-in fails, or Visma says the page cannot redirect back You see an error about the redirect URI, or the browser stalls on the Visma screen instead of returning to Apideck. This is a configuration issue on the application side, not something you can fix from your account: the application's callback URL has not been registered with Visma yet. Report it to the team whose application you are connecting from. ### "Access denied" or a permissions error right after approving The authorization was declined, or the login you used cannot reach the company you selected. Retry and make sure you click through the approval screen fully, and that you are signed in with a login that can open that company in Visma Online. ### You connected the wrong company Disconnect the connection in Vault and authorize again. On the Visma screen, sign out or use the account switcher first if it goes straight through with the previous choice, then pick the correct company. ### The connection succeeds but no data appears Confirm you selected the company that actually holds the data: an empty or newly created company in Visma will return empty lists. Also check that your subscription is active: eAccounting / Bokföring & Fakturering access has to be live for API calls to succeed. ### Still stuck For problems with your Visma Online login, subscription or company access, contact Visma/Spiris support through your eAccounting account. For anything on the Apideck side of the connection, contact [Apideck Support](https://help.apideck.com/en/articles/7774658). --- ## Reference - [Visma eAccounting](https://eaccounting.vismaonline.com): sign in and check your subscription - [Visma eAccounting developer documentation](https://developer.vismaonline.com/docs): technical reference for the API behind this connection [API reference](https://developers.apideck.com/apis/accounting/reference.md) · [Coverage matrix](https://developers.apideck.com/apis/accounting/coverage)