Article from
API Summer 2026: New Webhooks for Bookkeeping Exports and More
Webhooks help you respond to events in real time. New additions include project groups, time balance, planned purchases and – most exciting of all – bookkeeping exports.
(English image not yet available)MOCO webhooks let you react to events in MOCO, such as a project update, a new time entry or the deletion of a contact. They are an alternative to solutions like Zapier and Make, and allow you to implement these workflows on your own infrastructure.
More on Webhooks in MOCO
New Webhooks
Project Groups
If a project group changes, the new webhook is triggered – handy for anyone who wants to keep groupings up to date in an external system without having to poll regularly.
Time Balance
If the time balance (User Work Time Adjustments) is adjusted manually, the new webhook notifies you straight away – for example, so you can automatically pass the change on to another system.
Planned Purchases
If a planned purchase is created, updated or deleted, the new webhook notifies you in real time – useful if you track planned purchases in your own overview or planning.
Bookkeeping Export
If you use one of the bookkeeping systems supported directly, you already have suitable export options available (direct transfer or export in the target format). For all other bookkeeping systems, the only option so far has been to download the CSV file via the neutral bookkeeping export, adjust it to your system’s requirements if needed, and then import it manually.
The new webhook for bookkeeping exports changes that. As soon as a new export for Invoices or Purchases is created in MOCO, you receive an immediate notification – you can then fetch the export data directly via the API, removing the need for a manual CSV download.
This webhook lays the groundwork for building your own integrations with bookkeeping systems that MOCO does not support directly. The export is still initiated in MOCO. After that, notification, data retrieval, and generating the right import file can run automatically in the background. The actual transfer to the target system then happens – depending on what it supports – either via an interface or by importing the generated file.





