What’s new in v2024-05-25
Stay up to date with the latest features, improvements, and breaking changes in the current version of Monite API.
Overview
Monite API version 2024-05-25 includes improvements to recurring invoices, accounts payable OCR, and entity management.
In future updates of the API version 2024-05-25, we plan to add more features and improvements to our product offering. We’ll add these new features to the current API version unless they introduce new breaking changes. In such cases, we will introduce them in subsequent API versions.
Breaking changes
Version 2024-05-25 includes some breaking changes that you should consider when upgrading from previous API versions.
For more information on which changes we consider breaking and non-breaking, refer to our Versioning policy.
Removed fields
-
Removed deprecated
accounting
settings from partner settings.Example
Removed fields are highlighted.
-
Removed the deprecated
language
field from the request body ofPOST /receivables/{receivable_id}/send
. Instead, use the counterpart fieldlanguage
to specify the language to be used to localize the emails and PDFs sent to this counterpart. -
Removed some deprecated, duplicate, and rarely used fields from the response payload of invoices, quotes, and credit notes.
Example
Removed fields are highlighted.
HTTP status code changes
We’ve changed some response status codes to be more compliant with the HTTP specification.
-
Changed the status code from 403 to 401 for API calls made with an expired access token.
-
Changed the success status code from 200 to 201 for the following endpoints:
POST /mailboxes
POST /mailbox_domains
POST /roles
New features and improvements
The following features exist only in Monite API version 2024-05-25 and are not available in earlier versions.
Entity deactivation
Monite partners can now deactivate (disable) their entities, for example, if those entities are no longer active clients. Monite API includes the following new endpoints for this purpose:
POST /entities/{entity_id}/deactivate
POST /entities/{entity_id}/activate
- to reactivate an inactive entity.
Entity field status
indicates whether this entity is active
or inactive
.
status
="deleted"
instead, but are still considered inactive for all other purposes.Auto-sending of recurring invoices
Recurring accounts receivable invoices can now be configured to be sent automatically. To support this behavior, the recurrence configuration includes new optional fields:
recipients
- the list of invoice recipients (To, CC, BCC),subject_text
- the email subject text,body_text
- the text inserted in the email body.
Also, the iterations[].status
field in recurrence configurations has a new possible value "send_failed"
.
For more information, see Auto-sending of recurring invoices.
Canceling OCR on demand
New endpoint POST /payables/{payable_id}/cancel_ocr
allows users to cancel an ongoing OCR process for an uploaded payable, for example, if it takes too long.
The ocr_status
field of payables has a new possible value "canceled"
to indicate that OCR has been canceled.
In case of canceled OCR, users can still fill in the missing data for a payable manually.