- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Visma.net ERP API International Support Policy
About this support policy
This API Support Policy describes the policies and procedures under which Visma.Net API International 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,
- Endpoints are available on https://integration.visma.net/API-index
- API Endpoint Usage
- API Endpoint Functionality
- JSON Syntax
- Addressing API Feature requests & Bug Reports
- Providing code examples& Documentation for API Endpoint Usage
- API Troubleshooting
- Before contacting Visma.Net API Support,
please first check the API documentation and Training Materials available on Visma Academy(Visma.net Integrations, Foundation Training) and Visma.net API Developer Forum. Your question might have been answered already. - If you need help regarding the following topics,
- Token Generation(oAuth)
- API CLIENT_ID
- REDIRECT_URI
please contact VNI-Support@visma.com
- If you need assistance with obtaining a new API Client ID or would like to get Production Type Client upon completion of your integration test phase, please contact your Partner Service at your related market.
- If you need help regarding Visma.Net Financials ERP (UI); company configuration, setting up or module usage, please inform your Visma.net Financials customer to contact the market’s related Financials ERP Support or contact your Partner Service to get further information regarding the procedure that should be followed. (ERP Support)
What Visma.Net API support service does not cover
We don’t provide support for,
- Assistance in writing code and general code debugging for 3rd parties software & integrations & applications.
- Troubleshooting & technical support for external Software&Applications written by 3rd parties.
- Visma.Net Financials ERP (UI) related topics.
Support methods
When asking for support, please be prepared to provide information on your attempts to debug and isolate the Visma.net API problem.
You should share clarified information that belongs to your API Transaction/s.
- Used API Endpoint URL / Method
- Returned Http Status Code
- Returned Response Body (Error Message)
- If this is a POST/PUT request then Used RAW JSON script has to be attached to your inquiry.
These pieces of information are crucial for API Support consultants to be able to help you, diagnose the case.
For example, we may ask you to provide a simple test case that demonstrates the problem or ask you to 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 Financials ERP Support to help you to 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.
Support Hours
- Monday to Friday 8:30 - 16:30
Support Channels & Language
- Support is only available in English.
Visma.Net API Support is available through the following channels:
- Developers Visma.Net Community(Open public for read-only. Only Visma.Net API Certified users are allowed to raise inquiries.)
- Community support is free. If you need one-to-one support, you can ask for consulting and will be charged by the hour, requests can be sent to DeveloperSupport@visma.com
Supplementary Glossary
Term |
Definition |
ISV |
Independent Software Vendors (ISV) who integrate their software with Visma.net Services through endpoints. |
Client |
Each ISV can have one or more clients who will integrate with API & Visma.net Services. |
Customer |
A customer is someone who buys a Visma.net application. The one Visma has an agreement with, and the one to which the invoice will be issued. Normally it is a company, but it can also be a reseller or a private user. |
User |
A user is a person who uses one or more Visma.net applications exposed via Visma.net Integrations. |
API |
An Application Program Interface (API) is a set of routines, protocols, and tools for building client-side software applications. |
Endpoint |
An Endpoint is a point at which an application program interface (API) - the code that allows two software programs to communicate with each other -connects with the software program |
DTO |
A data transfer object (DTO) |
DB |
A database where Financials Company data is stored |
HTTP Status Code |
Hypertext Transfer Protocol response status codes |
Financials ERP |
Visma.Net Financials ERP Cloud Application |
JSON |
JavaScript Object Notation is an open-standard file format or data interchange format |
Client Id |
A unique ID dedicated to a Client. Example: visma_test_client_1234 |
Client Secret |
A secret code connected to the Client and Client ID. Should only be known to the ISV/Owner of the Client. Example: 284baba4-7a8d-4e14-2247-957812ac9ec |
Redirect URI |
A URI (web address) used in the authentication-process by the API to send the Authorization Code back to the Client. Each Client can have multiple Redirect URIs defined |
User |
A user (most often a person) that has access to Visma.net ERP. |
