Connect Visma eAccounting to OttoKit

To connect any application with Visma eAccounting through the API, you need OAuth 2.0 credentials. These are issued through the Visma Developer Self-Service portal. The process is free and self-service for sandbox access. Production access requires a separate request to Visma API support after sandbox testing is complete.

This guide covers the sandbox setup, which is where all development should happen first.

Step 1: Sign Up for the Developer Portal

Open the Visma Developer Self-Service portal in your browser:

https://selfservice.developer.vismaonline.com

Click the registration option and fill in the form. Visma will send your sandbox credentials to the email address you provide. Use a business email rather than a personal one, since this becomes the contact address for your developer account.

During the form, you will be asked to provide:

• Application name (what users see during the OAuth consent screen)
• Purpose of the integration (Private, Internal, or Public)
• Contact information
• Initial redirect URI (a placeholder is fine, you can update this later)

Step 2: Receive Your Credentials

Once your form is processed, Visma will send a confirmation email containing:

• Client ID – a public identifier for your application
• Client Secret – a private credential that authenticates your app to Visma
• Scopes – the list of scopes granted to your app
• Sandbox company access – a test eAccounting company you can use for development
• Placeholder redirect URI – typically https://localhost:44300/callback, which you will update in the next step

Important: Never share your Client Secret with anyone, including Visma API support. Visma explicitly states they will never ask for it. Store it as an environment variable or in an encrypted secrets manager, not in your source code or version control.

Step 3: Reply to Update Your Redirect URI

The redirect URI provided in the confirmation email is a temporary placeholder. You need to reply to the same email and ask Visma to register your actual redirect URI. The redirect URI must use HTTPS.

What to send

Reply to the confirmation email with your Client ID and the redirect URI you want registered. The redirect URI for the OttoKit integration is:

https://api.ottokit.com/visma_eaccounting/connection

Sample reply

Subject: Update redirect URI for Client ID <your_client_id>

Hello,

Thank you for the credentials. Please update the redirect URI for the following Client ID:

Client ID: <your_client_id>

New redirect URI: https://api.ottokit.com/visma_eaccounting/connection

Kind regards,

<your name>

Note: Visma will reply once the redirect URI has been updated. You will not be able to complete the OAuth flow against this URI until they confirm the update.

When contacting Visma API support, always include your Client ID. Never share your Client Secret. Visma explicitly states they will never ask for it.