Impelmenting new integration

When you want to integrate your services to work together with Netvisor or want to develop a new business based on them, follow these steps:

  1. Getting to know the API documentation: Explore the possibilities of the Netvisor interface from the API documentation and the Postman example
  2. Test environment and test partner credentials: Subscribe to the test environment by registering as a partner using the form below. You will receive partner credentials to the test environment and an information pack to implement the integration
  3. Deployment of the test environment: Implementation and testing of the integration in the test environment, with partner support as technical support
  4. Review of the implementation: Voluntary consultation with a technical expert
  5. Validation of integration: Partner notifies the completion of the integration with a form, we validate the implementation and then deliver the partner IDs to the production environment
  6. Production partner credentials: Integration is complete, the integration can be deployed in the Netvisor production environment

If you have any questions about the content of the software partnership or how to become a partner, please send an email to [email protected]

If you have any technical questions or you run into problems with your integration, contact Netvisor partner support by email [email protected]

Software Partnership

External application / service can be integrated to Netvisor by using our Web Service Interface. It enables bidirectional data transfer between two systems. When using our Web Service Interface, data transfer to and from Netvisor must be done by an active software component. Data is transferred in XML format. Web Service Interface uses REST style communication over HTTP:

  •  Request is sent by POSTing (in some rare cases only query string parameters are used) data to service address
  •  Service replies with a response containing result data for request. 

Depending on used integration resource, request and response can contain various amount of data. Communication is always done by XML payloads

Integrating external application to Netvisor and joining our ISV partner program we offer e.g. the following benefits:

  • Free partner program and freedom of business
  • Well documented API and instructions
  • Visibility on market place
  • Community to support your development and marketing
  • Growing and stable customer base

Netvisor integration partners get to join Netvisor Community, our cooperation and communication channel, that is used by our customers, our employees, and everyone interested in Netvisor. In Community, there is own discussion section also for integration related topics. We inform all updates to Netvisor API and other relevant news in Community, so we recommend following the discussions there. 

Checklist for new integration partner

In the list below you can find things that should be noted when you want to get started on your implementation quick and easy and efficiently get the implementation to production. If you run into problems with your integration, contact Netvisor partner support by email [email protected].

  1. Find out what you are doing and check if our web service interface has the opportunity to implement that. If you need support, contact our partner support in [email protected]
  2. Fill in this form https://netvisor.fi/isv-materiaalipankki/isv-yhteydenotto/ to register as ISV-Partner. With the same form you can order the testing environment, needed credentials and info package. 
  3. Login to Netvisor and get to know the test environment. You can change default settings and services.
  4. Create API identifiers: API identifiers
  5. Read the "Netvisor API Security and authentication.pdf" that you received in the email with the test credentials.
  6. Send a request to get customerlist -resource (customerlist.nv) to make sure the MAC-calculation and authentication is succesfull.
  7. If you need test material for Netvisor, send email to our support [email protected]
  8. When you are ready, please test your implementation thoroughly.
  9. When you have tested the implementation, send an email to our partner support ([email protected]) to inform that the integration is ready. Describe how different resoruces are used in the integration.
  10. After sending the email, our partner support will validate your integration and send the needed partner credentials to be used in production environment.
  11. To be able to get the implementation deployed you need the customer's Netvisor API credentials that the customer can create following this instruction: API identifiers. In addition Netvisor customer needs to activate web service interface in Netvisor and enable the integration in Rights of interface resources page. Please read more in Rights of interface resources

Test enviroment

Production environment is not meant for testing and that is why all implementations and changes should be tested in test enviroment before moving to production environment. We do not recommend testing with real or sensitive material. In testing phase performance control and information security should be paid extra attention.

When you receive the credentials for test environment, the environment doesn't have any data. You can create data manually in UI or import customers, products and vouchers in csv format using Netvisor's internal tools.

Partner support also has a general script to generate test material. To have this general data send email [email protected]. The script generates:

  • Few products, customers and vendors (10 each). Account number for vendors 
  • Sales invoices and their vouchers (10 each month * 12 months)
  • Purchase invoices and their vouchers (10 each month * 12 months) + some PDF attachment
  • Vouchers for multiple cost accounts, entry = cost account Debet AN 1910 Bank account Credit using accounts between 7000-7999. So 7000 debet vat 10-24 and 1910 credit




Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.