My Areas

Sign in to follow product and topic areas and get a shortcut in this menu
Visma eAccounting API
cancel
Showing results for 
Search instead for 
Did you mean: 
Labels
Sort by:
updated by Anour Hannouch VISMA ‎06-06-2019 12:08
When you receive an error code in the API, you should also find a message in the HTTP response. This will inform you as to the general error that has occurred.   When debugging the API request, we recommend using Fiddler.   If you need to contact support, please attach both the HTTP request and the response retrieved from Fiddler.
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:34
We are launching this community with the prospect of spreading more of the knowledge surrounding eAccounting API.   What will you be able to find here? Knowledge base: A collection of common problems and how to solve them. Forum:  A place where you can read and answer topics from other users. Ideas  tab: A place where you can suggest improvements   For Bugs, do not hesitate to contact us. Thanks!   About the community : The articles should help in most cases When posting on the forum, please avoid posting Access Tokens. When posting on the forum, show understanding towards others and avoid demeaning language.
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:30
As of today, you need to authorize using OAuth2 ( Read more about the OAuth2 Framework ). There are several different flows when using the OAuth2 to authenticate, of which we support: “ Authorization code flow ” The Authorization process can be summarized as seen below:   Redirect the user to the authorization endpoint. The user logs in with his/her credentials. These are the same credentials used for logging into eAccounting (VismaOnline). After successfully logging in, the user gets the choice to Allow or Deny your application access to the API. After allowing your application access, the user will be redirected back to your redirect URI. A code will be added as a parameter to the URL. Use the code from the URL in the POST request to the Token endpoint (see below for details about the POST request). If successful, you will receive an access token and a refresh token from the endpoint.   You are now ready to call the API. Include the access token in the header of each subsequent request to the API endpoints.   Some useful terminology Redirect URI : the redirect URI is where you will be redirected after successful authorization Callback URI : another name for “redirect URI” Identity server : the server which handles the identification of your client Authorization URL : this is the first endpoint on the identity server, which provides you with an authorization code Token URL : the second endpoint on the identity server, which provides you with an access token and refresh token Scope : the scopes for the functionalities you plan to use Client ID : identifies you on the server Client secret : a key that confirms that you are you Useful link: https://developer.vismaonline.com/docs/environments
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:25
For more information regarding error messages when authenticating, see HERE For more information regarding error messages from the API server, see HERE
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:21
While the access tokens have short (1 hour) expiry time, the refresh tokens have an expiry of 50 years. When the Access token expires, you are able to use the latest Refresh token acquired to get a new set of access and refresh tokens. Every new refresh token cancels the previous one.   Store the Refresh tokens safely, for example in a database or in the filesystem. Due to its long-lived nature, refresh tokens should always be stored safely. By saving them to permanent storage, you will also avoid having to enter your eAccounting user credentials, after for example a server reboot.
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:20
The endpoint " v2/customerinvoicedrafts/{customerInvoiceDraftId}/convert " unfortunately does not support sending invoices as an Autoinvoice.   A workaround to this is to do the following: Make sure the invoice is still a draft. Create " customerinvoicedraft " > add an attachment using " salesdocumentattachment " endpoint > convert the draft to an invoice using the " customerinvoice " endpoint with the properties "CreatedFromDraftId" and "sendtype".   Please see below example on what it can look like:   { "CustomerId": "2bab59cd-0e03-407e-bb59-9a1d1ca9bb02", "IsCreditInvoice": false, "RotReducedInvoicingType": 0, "RotReducedInvoicingPropertyName": null, "RotReducedInvoicingAmount": 0, "RotReducedInvoicingAutomaticDistribution": false, "Rows": [ {     "LineNumber": 0,     "ArticleId": "991d82e9-fdf6-4f4c-884b-517c2fa67adf",     "Text": "Lemon | 29,75 kr/kg",     "UnitPrice": 3.57,     "DiscountPercentage": 0,     "Quantity": 1 }, {     "LineNumber": 1,     "ArticleId": "991d82e9-fdf6-4f4c-884b-517c2fa67adf",     "Text": "Delivery org",     "UnitPrice": 22,     "DiscountPercentage": 0,     "Quantity": 1 } ], "YourReference": null, "OurReference": "", "EuThirdParty": false, "InvoiceDate": "2019-03-07", "DeliveryDate": "2019-03-07", "TermsOfPaymentId": "0f7c3ab0-0c02-46fe-b291-d8cd5ab445f7", "CreatedFromDraftId": "aa2902a2-118f-4505-b22e-ef38fc570dbe", "SendType": 2 }  
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:15
If you have several companies available in eAccounting, you will be able to select which company to Authorize for the Auth endpoint. The list of companies is available from a dropdown menu in eAccounting after logging in. If this menu is missing, the Default company setting might be turned on.   After logging in to eAccounting, go to the menu in the top right corner.   Press "Choose default company"     press the blue star (the default company) to remove it as default. And save!
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:14
Go to “Apps and extensions” under the settings tab, and make sure that the API is activated. Another reason can be that you are trying to login to an account without a valid eAccounting license. Check again what company you are logging into and make sure it is not set to “Default company”.  
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:13
A step-by-step guide how to complete the startup guide in order to resolve  "Error: the startup guide has not been completed" 
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:07
Read about the two different ways of creating invoices; t he “CustomerInvoices” endpoint and the “CustomerLedgerItems” endpoint.
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 11:01
Watch this tutorial on POSTMAN; a free API client that will help you with testing endpoints.
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 10:59
To be able to use eAccounting via the UI or the API, you will have to activate the company and complete the Startup Wizard.
View full article
updated by Anour Hannouch VISMA ‎06-06-2019 10:56
A token can become  invalid when its lifecycle has expired or when you change the password (changing password invalidates tokens).
View full article
updated by Anour Hannouch VISMA ‎04-06-2019 09:18
Read about HTTP that the POST request should contain for access tokens
View full article
by Anour Hannouch VISMA
Support information You can contact our API support at   eAccountingAPI@visma.com. We will make sure you get the help you need. Are you a Norwegian or Dutch partner? Send your questions to   API_eAccounting@visma.com    RELEVANT LINKS Developers Documentation Login eAccounting (Sandbox) Swagger (Sandbox) Login eAccounting (Production) Swagger (Production) System Status (Production)     Available integrations with eAccounting (some are country specific) Netherlands Norway Sweden    
View full article
Useful links

List of current integrations in: