Api identifiers are one part of Netvisor's interface authentication. They ensure that the integration has permission to use the company's software interface service. The identifiers are used in software integrations and when importing Finvoice-formatted invoice material. Separate Excel identifiers are created for Smart Excel sheets according to the Smart Excel help, which can be found here.

Api identifiers

Api identifiers are always user-specific, and you can create identifiers only for yourself. The identifiers are not directly tied to any company but to the user themselves and through them to the companies the user has rights to. To create these identifiers, the user only needs their own login credentials to the company and editing rights to at least one function. One user can have multiple api identifiers. There is no limit to the number of created api identifiers, and no separate charge is formed for the created identifiers.

Api identifiers are created as follows:

  1. Log in to Netvisor
  2. Navigate to create identifiers via Company menu > Api identifiers.
  3. Create identifiers from the button at the top right of the page "Create new api identifier"
  4. The identifier appears first in the list. User ID and Key are updated in the integration settings / provided to the software partner.

In the Api identifiers section, the user-created user IDs and keys are displayed (image above). In the help image, the identifiers are censored.

When handing over api identifiers to the software integration implementer, it should be noted that the software integration implementer and the customer using the software integration are responsible for the materials transferred to Netvisor. The creator of the materials transferred via the interface is the user in whose name the api identifiers were created. Technically, the same api identifiers can be used in multiple integration interfaces if necessary. However, we recommend using user-specific api identifiers for each integration interface to monitor traffic as accurately as possible, mainly for security reasons.

The customer must keep track of which identifiers are used for which integration interface.

The column "Purpose" (image below, point 1) shows the purposes of the identifiers. If the purpose is the Netvisor mobile application, these identifiers should not be used for interface authentication. The "Validity" column (2) shows whether a validity period has been set for the identifier. The api identifier can be deactivated by clicking the "Deactivate api identifier" column's "X" icon (3), after which the identifiers turn gray. Please note that deactivated identifiers cannot be restored.


This article has been translated using an AI-based translation tool. The contents or wording of these instructions may differ from those in other instructions or in the software.


Did you find it helpful? Yes No

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