Changelog

Version 9 (2022-05-03)

BREAKING CHANGE - The default behavior for endpoint /log/event/ is now to exclude relatedIdMsgs. The relatedIdMsgs can be included in the response by using the new query parameter fetchRelIdMsgs=true.

Version 8 (2021-11-16)

Added support for commodityCode and countryOfOrigin for products. For more info see Swagger API reference

Version 7 (2021-04-13)

Added new endpoints for Product prices. For more info see Swagger API reference

New endpoints are:

  • product/{localId}/price
  • product/by-remote-id/price
  • product/{localId}/price/{pricelistLocalId}
  • product/by-remote-id/price/by-remote-Id

Version 6 (2021-03-23)

Settlement Report

  • Settlement uses a new Tax Model. All vat fields have been removed.
  • BREAKING CHANGE All Vat-fields have been removed from Settlement endpoints.
  • BREAKING CHANGE The Tax-fields should be used instead. These fields use the new Tax Model.

Z-Report

  • Z-Reports uses a new tax model. All vat fields have been removed.
  • BREAKING CHANGE All Vat-fields have been removed. The Tax-fields should be used instead. These fields use the new Tax Model.

Payment Transaction Event

  • Payment transaction event uses the new Tax Model. All Vat-fields are deprecated, and it is highly recommended to start using the Tax-fields.

Invoice

  • Invoice uses the new Tax Model. All Vat-fields are deprecated, and it is highly recommended to start using the new Tax-fields instead.
  • BREAKING CHANGE Fields specifiedVatPerUnit and specifiedRowDiscountVat have been removed.

Order

  • Order uses the new Tax Model. All Vat-fields are deprecated, and it is highly recommended to start using the Tax-fields.
  • BREAKING CHANGE Fields specifiedVatPerUnit and specifiedRowDiscountVat have been removed.

Version 5 (2019-06-05)

  • Added lots of information to error response.

Version 4 (2019-05-06)

  • Added rounding row type.

Version 3 (2019-04-25)

  • Added orderType for orders.

Version 2 (2019-03-21)

Version 1 (2018-12-07)

First public version.

Future changes should remain backwards compatible enough so clients written against older versions should work with no changes as long as the client ignores any new fields in responses.