Breaking changes Notice

The account_id filter on the List transactions endpoint has been renamed into bank_account_id for consistency with the rest of the wording used on the API.

Filter transactions by date

On the List transactions endpoint, it's now possible to filter transactions by date using the date filter.

The structure of a transaction resource has been improved

The data structure of responses related to transactions has been unified and now contains more attributes.

🎉 We are happy to announce that part of the Merge Project, it is now possible to list and upload appendices for credit notes. For more details on this initiative, please refer to our documentation.

List appendices for a customer invoice and Upload an appendix for a customer invoice endpoints previously returned a 404 response when the invoice was a credit note. There are now able to list and create appendices for credit notes, draft invoices and finalized invoices.

Deprecation Notice

The List invoice lines for a credit note and List invoice line sections for a credit note endpoints are now deprecated as part of the Merge Project. For more details on this initiative, please refer to our documentation.

List invoice lines for a customer invoice and List invoice line sections endpoints previously returned a 404 response when the invoice was a credit note. They are now able to request associated resources for credit notes, draft invoices and finalized invoices.

Breaking changes Notice

Before, when the requested invoice was a draft the response status was 404.

Now, the following response is returned

{
  status: 422,
  error: "This endpoint is not applicable for draft invoices"
}

Before, when the requested invoice was a credit note the response status was 404.

Now, the following response is returned

{
  status: 422,
  error: "This endpoint is not applicable for credit notes"
}

Breaking changes Notice

Few changes on status code rendered due to the Merge Project for Customer Invoices Matched Transactions endpoints. For more details on this initiative, please refer to our documentation.

As a reminder it is not possible to match a transaction to a draft invoice.

Before, when the requested invoice was a draft, the response status code was 404.

Now this endpoint returns a 200 with an empty array.

Before, when the requested invoice was a draft, the response status code was 404.

Now this endpoint returns a 422 with following error message: "This endpoint is not applicable for draft invoices"

Before, when the requested invoice was a draft, the response status code was 404.

Now this endpoint returns a 422 with following error message: "This endpoint is not applicable for draft invoices"