E-invoices import - Add invoice ID to response
The POST /e-invoices/imports endpoint now returns the invoice id directly in the response body, making it easier to retrieve and track imported invoices.
The POST /e-invoices/imports endpoint now returns the invoice id directly in the response body, making it easier to retrieve and track imported invoices.
We've introduced new filtering capabilities on the List supplier invoices endpoint. You can now filter by payment_status using the eq, not_eq, in, not_in operators.
When creating or updating customer invoices (both draft and finalized), you can now provide only the product_id and quantity fields for invoice lines. The API will automatically populate label, description, ledger_account_id, raw_currency_unit_price, unit, and vat_rate from the associated product. You can still override any of these fields by providing them explicitly in your request.
You can now specify a due_date (optional field) when creating ledger entries via the API.
The ledger_attachment_id is deprecated from the request body params in favour of file_attachment_id.
You can now specify your own piece_number (optional field) when creating or updating ledger entries via the API, allowing you to use custom numbering systems for better tracking across your organization.
We're now returning the interbank_code attribute in the response of the Transactions endpoints, offering more context about transaction types and origins.
We've updated 404 not found error messages for the following endpoints:
We are happy to announce the introduction of the Update a ledger account endpoint.
The ledger OAuth scope has been deprecated across all ledger-related API endpoints. We have introduced more granular scopes that provide better control over API access permissions.