Visma eAccounting API - New Bugfix - ShippedDateTime
by Daniel JonssonVisma eAccounting API - New Properties on Articles and Vouchers
by Daniel Jonsson
New propertiesWe added currency fields in the API for Articles.
We also added VoucherId on AllocationPeriods.
Properties added:
CurrencyCode, PurchasePriceWithCurrency and FreightCostWithCurrency
Endpoints affected:
v2/articles
v2/articles/{articleid}
Properties added
VoucherId
Endpoints affected:
V2/AllocationPeriods
Visma eAccounting API - New filter
by Daniel Jonsson
Several new filtersWe have added many new filters, see below
Added the possibility to filter by negative amounts
Properties: -TotalAmount, -TotalVatAmount, -TotalRoundings, -RemainingAmount
Affected endpoints:
v2/customerinvoices
v2/customerinvoices/statistics
Possibility to filter by customer ID on quotes
We have made it possible to filter by customer ID when fetching quotes.
Affected endpoint:
GET v2/quotes
Added the possibility to filter on Row/Text
Affected endpoints:
GET /v2/customerinvoices
Added the possibility to filter on Row/ArticleNumber
Affected endpoints:
GET /v2/customerinvoicedrafts
Filtering by properties 'HasAutoInvoiceError' and 'TotalAmountInvoiceCurrency'
In the v2/customerinvoices and v2/customerinvoices/statistics endpoints we are missing properties 'HasAutoInvoiceError' and 'TotalAmountInvoiceCurrency'. Those have been added and the filtering is now possible, the same as in the web.
Affected endpoints:
GET /v2/customerinvoices?$filter=HasAutoInvoiceError eq true
GET /v2/customerinvoices/statistics?$filter=HasAutoInvoiceError eq true
GET v2/customerinvoices?$filter=RemainingAmountInvoiceCurrency eq -TotalAmountInvoiceCurrency or RemainingAmountInvoiceCurrency eq TotalAmountInvoiceCurrency
GET v2/customerinvoices/statistics?$filter=RemainingAmountInvoiceCurrency eq -TotalAmountInvoiceCurrency or RemainingAmountInvoiceCurrency eq TotalAmountInvoiceCurrency
Filter customer invoices by text row
Search for invoices with tex rows that contain a specific text.
New endpoints:
GET v2/customerinvoices?$filter=Rows/any(c: contains(c/Text,'anytext'))
Visma eAccounting API - New Properties
by Daniel Jonsson
We have added many new properties that we see add value for you developersWe added new properties wich affects PeppolID, CustomerNumber in orders and qoutes, settings for email for qoutes & orders and so on.
Expose CustomerNumber in quotedrafts, quotes and orders
New endpoints have been added to the quotedrafts, quotes and orders to expose the customerNumber in the same way as customerInvoices.
Affected endpoints:
GET v2/quotedrafts
GET v2/quotes
GET v2/orders
New property "PeppolId" added
PeppolID is now exposed in the API. The property is readonly.
Effected endpoint:
GET v2/companysettings
New properties "MessageThreads" and "Notes"
The following properties "MessageThreads" and "Notes" has been ** added to the customerinvoicedrafts endpoints. The new properties can be used to get a message thread or note by id.
Effected endpoints:
GET v2/customerinvoicedrafts
GET v2/customerinvoicedrafts/{id}
New properties EmailAddressQuote and EmailAddressOrder
These new properties will allow the user to add different recipients for quotes and orders.
Affected endpoints:
GET v2/customers
GET v2/customers/{id}
POST v2/customers
PUT v2/customers/{id}
The logic of the new endpoints below is that if the email property in the request body is empty, then the document should be sent to the default email, which comes from the email Order/Quote field. If this field is empty then the default email is the email from the email invoice field. If the email invoice field is empty you get an exception that the email was not sent.
Affected endpoints:
POST v2/quotes/{id}/email
POST v2/orders/{id}/email
Visma eAccounting API - New bugfixes
by Daniel Jonsson
Here is a list of the latest bugfixes we've doneThe parts we have solved affects both green technology, correct VAT numbers and so on.
Create a green tech invoice with 20 percentage for solar panel installation
This update makes it possible to create invoices with 20% and not only 15% as before, which are the only allowed values. The user has the option to change this by opening company settings and then invoice settings.
Affected endpoints:
POST v2/quotes
POST v2/orders
POST v2/customerinvoices
POST v2/quotedraft
POST v2/customerinvoicedrafts
Fix the e-mail layout formatting for quotes/orders/invoices
The formatting of the e-mail is now fixed so that it matches the one sent from the web.
Affected endpoints:
v2/quotes/{id}/email
v2/orders/{id}/email
v2/customerinvoices/{id}/email
Validate VAT number on customers
If a VAT number is added to a customer it needs to be valid according to VIES. This change will apply when creating new customers or changing existing ones. This behaviour will align with the current validation in the web application.
Affected endpoints:
POST v2/customers
PUT v2/customers/{id}
Invoice date on sales invoice drats
Today we always show the original invoice date, regardless of the company setting for βKeepOriginalDraftDateβ.
This update will change the behavior to:
Keep today's date if the setting is OFF or NULL
Use the original draft date if the setting is ON
Affected endpoints:
GET v2/customerinvoicedrafts
GET v2/customerinvoicedrafts/{id}
New endpoints for SalesPriceList and DiscountAgreementWe now, in eAccounting, support creating several price lists, therefore you can have specific sales prices for an article to specific customers. Also, we support creating multiple discount agreements that could be linked to a customer. These endpoints are available only for PRO variants.
Existing salespricelists and discountagreements can now be fetched in the API.
Changelog
- Affected endpoints:
GET /v2/salespricelists
GET /v2/salespricelists/{salesPriceListId}
GET /v2/salespricelists/prices
GET /v2/salespricelists/prices/{salesPriceListId}/{articleId}
GET /v2/discountagreements
GET /v2/discountagreements/{discountAgreementId}