--- id: video/S5Xw-b8YF-c type: video title: "What's New: APIs in E-Documents (2025 release wave 2)" summary: 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. tier: official language: en tags: - e-documents - apis - power automate - business events - integration - code-free - sharepoint - odata - external sources - custom agents system: integration review: state: reviewed by: opus at: "2026-10-07T22:54:19.726Z" flags: [] generated: at: "2026-10-07T22:54:19.775Z" pipeline: 0.2.0 prompts: extract-video: 1 summarize-video: 2 input_hash: 7934cdacde0294d766e5651a2f970e5feeda5d2dfbf62f1123e68e3fe2f506be evidence: - kind: video url: https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=30s title: "What's New: APIs in E-Documents (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 30 quote: So first we wanted to enable flexible and codefree integration. - kind: video url: https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=41s title: "What's New: APIs in E-Documents (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 41 quote: It doesn't mean that it should be first channel of communication. It can be but this is not intended for that. - kind: video url: https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=98s title: "What's New: APIs in E-Documents (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 98 quote: it enable your usage and creation of new custom agent using copilot studio because now this is available with APIs - kind: video url: https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=174s title: "What's New: APIs in E-Documents (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 174 quote: We deliver five APIs and two business events. - kind: video url: https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=255s title: "What's New: APIs in E-Documents (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 255 quote: Important to note is that we expect the contents of a of an electronic document in B 64. - kind: video url: https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=447s title: "What's New: APIs in E-Documents (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 447 quote: this is one of these business events that we have added that's called e document service status changed. - kind: video url: https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=457s title: "What's New: APIs in E-Documents (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 457 quote: the condition I have set is that the e document service status has to be exported for us to actually move forward. links: learn: [] objects: [] features: [] topics: [] localizations: [] videos: [] posts: [] guidelines: [] video_id: S5Xw-b8YF-c channel: yt-microsoft source_name: Microsoft Dynamics 365 Business Central (YouTube) url: https://www.youtube.com/watch?v=S5Xw-b8YF-c published_at: "2025-10-01T00:00:00Z" duration_s: 693 captions: full audience: - developer - functional consultant - administrator chapters: - t: 0 title: Introduction and overview - t: 30 title: "Why APIs for e-documents: flexibility and integration" - t: 113 title: "What is delivered: five APIs and two business events" - t: 174 title: "Demo setup: create e-document from SharePoint" - t: 228 title: "Demo execution: SharePoint to Business Central flow" - t: 368 title: "Demo setup: business event for e-document export" - t: 433 title: "Demo execution: e-document business event and APIs" - t: 626 title: Resources and closing remarks features: - name: E-Documents APIs status: unclear t: 5 verified: false status_source: video - name: E-Document Business Events status: unclear t: 113 verified: false status_source: video - name: Create E-Document from External Sources status: unclear t: 113 verified: false status_source: video - name: E-Document Export via Business Events status: unclear t: 385 verified: false status_source: video - name: Custom Agents with Copilot Studio Integration status: unclear t: 98 verified: false status_source: video objects_mentioned: - table E documents - table E document service - table E document service status quotes: - t: 30 text: So first we wanted to enable flexible and codefree integration. check: exact - t: 41 text: It doesn't mean that it should be first channel of communication. It can be but this is not intended for that. check: exact - t: 98 text: it enable your usage and creation of new custom agent using copilot studio because now this is available with APIs check: exact - t: 174 text: We deliver five APIs and two business events. check: exact - t: 255 text: Important to note is that we expect the contents of a of an electronic document in B 64. check: exact - t: 447 text: this is one of these business events that we have added that's called e document service status changed. check: exact - t: 457 text: the condition I have set is that the e document service status has to be exported for us to actually move forward. check: exact --- # 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. [Watch on YouTube](https://www.youtube.com/watch?v=S5Xw-b8YF-c) · Microsoft Dynamics 365 Business Central (YouTube) · 2025-10-01 · 11:33 · tier official · reviewed (checked by Opus) ## 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. ## Chapters - [0:00](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=0s) Introduction and overview - [0:30](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=30s) Why APIs for e-documents: flexibility and integration - [1:53](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=113s) What is delivered: five APIs and two business events - [2:54](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=174s) Demo setup: create e-document from SharePoint - [3:48](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=228s) Demo execution: SharePoint to Business Central flow - [6:08](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=368s) Demo setup: business event for e-document export - [7:13](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=433s) Demo execution: e-document business event and APIs - [10:26](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=626s) Resources and closing remarks ## Features | Feature | Status | At | |---|---|---| | E-Documents APIs | status not stated, demoed | [0:05](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=5s) | | E-Document Business Events | status not stated, demoed | [1:53](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=113s) | | Create E-Document from External Sources | status not stated, demoed | [1:53](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=113s) | | E-Document Export via Business Events | status not stated, demoed | [6:25](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=385s) | | Custom Agents with Copilot Studio Integration | status not stated | [1:38](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=98s) | ## 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](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=285s) - table "E document service" at [8:22](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=502s) - table "E document service status" at [8:35](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=515s) Not found in BC28-30: table "E documents", table "E document service", table "E document service status". ## Quotes - [0:30](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=30s) "So first we wanted to enable flexible and codefree integration." - [0:41](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=41s) "It doesn't mean that it should be first channel of communication. It can be but this is not intended for that." - [1:38](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=98s) "it enable your usage and creation of new custom agent using copilot studio because now this is available with APIs" - [2:54](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=174s) "We deliver five APIs and two business events." - [4:15](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=255s) "Important to note is that we expect the contents of a of an electronic document in B 64." - [7:27](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=447s) "this is one of these business events that we have added that's called e document service status changed." - [7:37](https://www.youtube.com/watch?v=S5Xw-b8YF-c&t=457s) "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.