API Support

Policies and procedures for API support

About this Support Policy

This API Support Policy describes the policies and procedures under which the API Support Team provides support services for its proprietary software product(s) to its Independent Software Vendors.

What Visma Net API Support Service Covers

We provide support for:

Before contacting API Support, please first check the API documentation and Training Materials available on Visma Learning Universe and Discord API Community. Your question might have been answered already.

For help regarding Visma Net Financials ERP (UI); company configuration, setup or module usage, inform your Visma Net Financials customer to contact the market’s related Financials ERP Support or your Partner Service for further procedure guidelines.

What Is Not Covered by API Support

We don’t provide support for:

  • Assistance in writing code and general code debugging for third-party software & integrations & applications.
  • Troubleshooting & technical support for external Software & Applications written by third parties.
  • Visma Net Financials ERP (UI) related topics.

Support Methods

When seeking support, please be prepared to provide information on your attempts to debug and isolate the Visma Net API problem.

Information needed:

  • Used API Endpoint URL / Method
  • Returned HTTP Status Code
  • Returned Response Body (Error Message)
  • For POST/PUT requests, attach the Used RAW JSON script.

These details are crucial for API Support consultants to help diagnose your issue. For example, we may ask you to provide a simple test case that demonstrates the problem or replicate the problem outside of your application.

If we cannot diagnose a problem with the APIs, we may be limited to providing suggestions on how you can resolve the issue. Since API adheres to the rules of the Financials ERP, we may also suggest the use of Visma Net Support to help you locate and fix UI originated problems.

Accordingly, restoring your Financials company DB into our local environment is another option that API Support Team can ask your data owner’s approval in order to get access for the development team to perform further diagnostics on your issue occurred data at Visma side.

For more details on how to report cases, please view API incidents - Troubleshooting and reporting

Support Language & Channels

Visma Net API Support channels:

Supplementary Glossary

Term Definition
ISV Independent Software Vendors integrating their software with Visma Net Services through endpoints.
Client ISVs can have multiple clients integrating with API & Visma Net Services.
Customer An entity purchasing Visma Net application with an agreement and invoicing arrangement, can be a company, reseller, or private user.
User Individual using one or more Visma Net applications via Visma Net Integrations.
API Application Program Interface facilitating client-side software applications development.
Endpoint Connection point for API allowing software program communication.
DTO Data Transfer Object
DB Database storing Financials Company data.
HTTP Status Code Protocol response codes for Hypertext Transfer Protocol.
Financials ERP Visma.Net Financials ERP Cloud Application.
JSON Open-standard file format or data interchange format known as JavaScript Object Notation.
Client Id Unique ID for a Client, e.g., visma_test_client_1234
Client Secret Secret code linked to Client and Client ID, only known to ISV/Owner. Example: 284baba4-7a8d-4e14-2247-957812ac9ec
Redirect URI Web address for API authentication process to send Authorization Code back to the Client, can have multiple definitions per Client.
User A person having access to Visma.net ERP.

Section Content

API incidents - Troubleshooting and reporting

Steps to troubleshoot and report issues for timely resolution.
Last modified January 7, 2026