Hello, we confirm that there was a temporary network issue affecting some of our clients that they've been experiencing latency or connectivity issues. We're sorry for the disruption. We have resolved the root cause and mitigated the errors at 14:13 CEST If you're still encountering any issue, please let us know. ... View more

Hello Azadeh,    Your redirect URI has been updated to https://www.vismanet. automatiseramera.se/accounts/ visma/login/callback ... View more

Status:  Issue has now been resolved. We will continue to monitor the situation. Please let us know if you encounter any problems. ... View more

Hi Florian,  the value of tags defined on each operation have been changed at the Swagger and updated to higher version. We're sorry that this has not been announced earlier and documented in the release notes.  ... View more

Hello,    those operations are not exposed via the currently available API. If you'd like to raise an improvement request for the development, please register this at the ideas section of the community by specifying the UI details / Business case. Thank you. ... View more

Hello,  currently, field selection function is not supported. We definitely agree with the idea that this would be useful to reducing data transfer size. We'll move/copy this thread to the Ideas part of the community. In this way, other community users also can vote for the idea, so that this will influence the priority of the case when the developers are deciding which features to enlarge the endpoints with. ... View more

Hello Tobisas,  LastModifiedDate parameter should always be used together with "condition".     supplierInvoice?lastModifiedDateTime=2021-06-23 &lastModifiedDateTimeCondition=>=   Here you can see supported comparative operators for LastModifiedDateTime Conditions on filtering option > < <= >= *API Response Header Returns : GMT(+0) / UTC Offset: UTC +0 besides *API&GUI: uses as a compliant DateTime format for both registering database and using in the system as of today it returns and write on database (GMT +1) In addition to that DTO include ISO 8601 Standarts for DateTime or DateTimeOffset value like following structures what API-DB accept, *"YYYY-MM-DD" *YYYY-MM-DDT00:00:00Z as of today Filtering Parameters does not accept certain characters such as W-Z These are the formats for filtering *2001-01-01 *2001-01-01 13:13:13 *2001-01-01 13:13:13.133 ... View more

Hello,  please use  Subaccount Endpoint (Get a specific) to list segmented values. GET: https://integration.visma.net/API/controller/api/v1/subaccount/102000 ... View more

Hello,    "Released" parameter from GET Supplier Invoice Endpoint is not a "DateTime" filter, but a conditional one. Parameter documentation should be modified to provide clearer information. We've informed the relevant team for that. (/controller/api/v1/supplierInvoice - Get a range of Invoices ) https://integration.visma.net/API-index/) "Release" parameter could filter the dataset to only return the "Supplier Invoices" which are released. (Invoice Status: Open/Closed. Please see the following information for details.) GET:     https://integration.visma.net/API/controller/api/v1/supplierInvoice?released=1     ------------------------------------------------------------------------------------------------------------------------------------- ℹ️ Supplier Invoice Document Statuses ℹ️ The invoice can have one of the following statuses, which tells you its stage in processing: On hold: Generally, this status is used for an invoice that is a draft. This is the default status for new documents if the Hold documents on the entry check box are selected in the Supplier ledger preferences (AP101000) window. An invoice with the On hold status can be edited. Balanced: After editing is completed, you take the invoice off hold, thus changing its status to Balanced. If the Validate document totals on entry option is selected in the Supplier ledger preferences (AP101000) window, you can take the invoice off hold only if you type the document control total. Pre-released: The status indicates that the invoice has been pre-released and requires expense reclassification. (This status is used only if the Support for expense reclassification functionality is activated.) Open: This status means that the document has been released (and approved, if required). Closed: This status reflects that the document has released and been paid. ------------------------------------------------------------------------------------------------------------------------------------- ... View more