Release Notes

Information about future and past API releases

Version releases

We are constantly adding new features to Procountor API. This page has the planned changes in future releases as well as release notes for the current ones. For anyone interested, we recommend subscribing to our mailing list to get notifications about API changes as soon as they become available.

Subscribe to our mailing list

Procountor API pricing will change starting from 1st of November.
The new pricing will take into consideration the number of integrations used by one company.
The new pricing will consist of monthly API fee 9,95 € / month and API fee per integration 1,95 € / month.
(e.g. one API integration in use -> 11,90 € / month, two API integrations in use -> 13,85 € / month)
More details behind the links in the pricing section.

Currently available API versions

Procountor API version diagram

API Path Version Release Date Support Ends
/latest monthly release with no extended support
/supported 21.08 updated to latest numbered version every three months
/v2102 21.02 2021-02-20 mid-Nov 2021
/v2105 21.05 2021-05-22 mid-Feb 2022
/v2108 21.08 2021-08-21 mid-May 2022

You can find the version update schedule from Procountor news and announcements site.

Release notes

Changes highlighted in red are not backwards compatible

Procountor API pricing will change starting from 1st of November.
The new pricing will take into consideration the number of integrations used by one company.
The new pricing will consist of monthly API fee 9,95 € / month and API fee per integration 1,95 € / month.
(e.g. one API integration in use -> 11,90 € / month, two API integrations in use -> 13,85 € / month)

Planned changes for the future

  • Support for invoice templates

Changes in version 21.10

We have removed support for weak TLS 1.2 cipher suites from our API services. This change took effect on Monday 27 September 12.00 EEST (09.00 UTC).
The following cipher suites are still supported with TLS 1.2: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256, TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, TLS_DHE_RSA_WITH_AES_256_CCM_8, TLS_DHE_RSA_WITH_AES_256_CCM, TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384, TLS_DHE_RSA_WITH_ARIA_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_CCM_8, TLS_DHE_RSA_WITH_AES_128_CCM, TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256, TLS_DHE_RSA_WITH_ARIA_128_GCM_SHA256

Other

  • We have changed the wording of "API login only" user right limitation to "Allow only M2M login to API" to better reflect the functionality behind this limitation. Enabling this limitation means that the user is allowed to log in to Procountor only using the API with M2M authentication method.

Changes in version 21.09

Other

  • We are adding a new user right restriction: API login only. When enabled for a user they will only be able to log in using the API and M2M authentication. We recommend enabling this setting for technical users created for backend API integrations.

Changes in version 21.08

Endpoints

  • In addition to type, GET /attachments results can now be filtered using referenceId. Note that the same reference id can exist for references of multiple types.
  • GET /invoices/{id} no longer incorrectly returns cashDiscount details for those invoice types where cash discount is not applicable.
  • PUT /invoices/{id} can now be used to modify invoices in RECEIVED state as well as in UNFINISHED state.
  • GET /products results can now be filtered using the active field.

Other

  • Descriptions in API reference have been clarified.

Changes in version 21.06

Endpoints

  • GET /invoices now returns correct default values for cashDiscount fields.
  • Bug affecting invoice row ordering in GET /invoices/{id} has been fixed. The invoice rows are now returned in the same order they have been given.
  • GET /products does now show correct active values for returned products for all API versions.
  • Bug with GET /products TRAVEL product date filtering has been fixed for all API versions. The endpoint returns products which have been valid at any point between given startDate and endDate.

Changes in version 21.05

Endpoints

  • GET /invoices results can now be filtered using invoiceChannel. More than one invoice channel can be given in a comma separated list.
  • Factoring information is now correctly returned for sales orders with GET /invoices/{id}.
  • Counterparty information is now correctly saved and returned when creating or modifying purchase orders with POST /invoices and PUT /invoices/{id}.

Other

  • Multiple rare error cases with the API now return a more detailed error description instead of just a generic 500 error.

Changes in version 21.04

The legacy authentication method has been removed from production.

Endpoints

  • We are introducing new GET /company/invoicecirculation/settings endpoint, which returns the company specific invoice circulation settings including default verifiers and acceptors.
  • We are introducing new GET /company/invoicecirculation/verifierlists endpoint, which returns basic data from all the invoice verifier lists configured in the company environment.
  • We are introducing new GET /company/invoicecirculation/verifierlists/{id} endpoint, which returns verifiers and acceptors connected to a specific verifier list.
  • POST /invoices and PUT /invoices/{id} now return correct error when trying to create or update an invoice with cash discounts in an environment which does not allow using cash discounts.
  • We are changing the pagination in GET /products endpoint to be in line with other endpoints supporting pagination. With this change the results are now returned in results object instead of products object, the maximum number of returned products is now controlled with size query parameter instead of limit query parameter, and meta object containing pagination related information is now returned with the results. We have also added orderById query parameter to control the order of the returned items.

Changes in version 21.03

The legacy authentication method has been removed from the API public test server.

Endpoints

  • Missing currency codes, e.g. CNH, have been added to GET /bankaccounts and other API endpoints returning currency code information.
  • GET /bankstatements results can now be filtered by bank account number using accountNumber query parameter. This filter uses exact matching.
  • POST /invoices and PUT ​/invoices​/{invoiceId} endpoints will now replace all line breaks (\n or \r) with spaces in address fields like counterPartyAddress, billingAddress and deliveryAddress. This prevents invoices being caught in an error because of forbidden characters.
  • GET /products results can now be filtered by product code using code query parameter. This filter uses substring matching.

Other

  • Issues some customers have faced on the public API test server with endpoints requiring two-factor authentication have been fixed.

Older release notes

Older release notes can be found from their own page.

Old release notes