What's New: APIs in E-Documents (2025 release wave 2)
E-Documents APIs in Business Central 2025 release wave 2 add five APIs and two business events for flexible, code-free integration through Power Automate or similar tools. The demos show two flows. The first creates and processes an inbound e-document from a file uploaded to SharePoint. The second uses the 'e document service status changed' business event, filtered in the flow to the exported status, then reads the e-document, its service, the service status and the file content, and emails the result.
- Introduction and overview
- Why APIs for e-documents: flexibility and integration
- What is delivered: five APIs and two business events
- Demo setup: create e-document from SharePoint
- Demo execution: SharePoint to Business Central flow
- Demo setup: business event for e-document export
- Demo execution: e-document business event and APIs
- Resources and closing remarks
Overview
The video explains why APIs were added to e-documents: to allow flexible, code-free integration. The delivery is five APIs and two business events. They can trigger processes from e-documents and create e-documents from external sources such as SharePoint, OneDrive or other XML sources.
Two demos follow. In the first, a flow creates an e-document in Business Central from a file in SharePoint. In the second, the business event “e document service status changed” starts a flow when the status becomes exported. The flow then retrieves the e-document through the APIs, including OData filtering on e-document and service data. The presenter says the APIs are not meant to be the first channel of communication, but a parallel or additional one.
Key points
- Delivered: five e-document APIs and two business events, aimed at flexible, code-free integration such as Power Automate.
- The APIs are not intended as the first channel of communication. They are meant as a parallel or additional channel, for example SharePoint, OneDrive or a different mail service for specific customers.
- When creating an e-document through the API, the file contents must be base 64 encoded and the selected e-document service must already exist. You can choose whether to process the document right away or leave it for manual processing.
- The ‘e document service status changed’ business event fires when an e-document service status changes. The demo flow uses a condition so that it continues only when the status is exported.
- The demoed APIs read the e-document, the e-document service, the specific service status (with an OData filter query on entry number and service code) and the file content (decoded from base 64).
- The video says the APIs also make it possible to build new custom agents with Copilot Studio. This was not demonstrated.
Features
| Feature | Status | At |
|---|---|---|
| E-Documents APIs | status not stated, demoed | 0:05 |
| E-Document Business Events | status not stated, demoed | 1:53 |
| Create E-Document from External Sources | status not stated, demoed | 1:53 |
| E-Document Export via Business Events | status not stated, demoed | 6:25 |
| Custom Agents with Copilot Studio Integration | status not stated | 1:38 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- table “E documents” at 4:45
- table “E document service” at 8:22
- table “E document service status” at 8:35
Not found in BC28-30: table “E documents”, table “E document service”, table “E document service status”.
Quotes
- 0:30 “So first we wanted to enable flexible and codefree integration.”
- 0:41 “It doesn’t mean that it should be first channel of communication. It can be but this is not intended for that.”
- 1:38 “it enable your usage and creation of new custom agent using copilot studio because now this is available with APIs”
- 2:54 “We deliver five APIs and two business events.”
- 4:15 “Important to note is that we expect the contents of a of an electronic document in B 64.”
- 7:27 “this is one of these business events that we have added that’s called e document service status changed.”
- 7:37 “the condition I have set is that the e document service status has to be exported for us to actually move forward.”
Presenters (as heard): Alexander Totovich, Manos, Magnus.