Business Central Adds PDF APIs for 31 Sales, Inventory and Assembly Documents

Tracked under Microsoft's AI at Work roadmap ID 576792, the capability—officially titled Reporting and data analysis - Use new APIs for getting the PDF of a document report—reached general availability in June 2026 (specifically beginning June 1, 2026, according to Microsoft Learn release plan documentation) for the Web platform across Worldwide (Standard Multi-Tenant) cloud instances. The feature is enabled for end users automatically, without requiring administrators to flip a preliminary feature switch just to expose the capability.

Why does a batch of read-only PDF endpoints matter right now? Because modern back-office automation is rapidly shifting from rigid, manual exports to autonomous orchestration through Power Automate, Microsoft Copilot Studio, and the Model Context Protocol (MCP) Server for Business Central. When a warehouse bot, a vendor portal, or a finance agent needs to verify a shipment or forward an archived order, raw JSON fields are only half the story—businesses still run on formatted, human-readable PDFs.

Expanding Beyond Basic Invoices: What the New APIs Cover​

Before this expansion, Business Central was hardly a stranger to PDF retrieval, though its standard documented reach was relatively narrow. In the standard Business Central API v2.0 reference on Microsoft Learn, the pdfDocument resource type primarily highlights core accounting staples: sales invoices, sales quotes, sales credit memos, purchase invoices, and purchase credit memos.

Real-world supply chains, however, generate a lot more paperwork than final invoices. If an automated workflow needed to pull a physical inventory recording, a transfer receipt, or an archived blanket order, developers often had to build custom AL extensions or bespoke web services to render and hand off the file.

The new read-only APIs in the document report system bridge that operational gap by exposing 31 specific document types across four major functional pillars:

Key Takeaways on Scope​

• Read-Only by Design: These endpoints are strictly for querying and retrieving document report PDFs. They do not create, post, or alter the underlying ERP transactions.
• Archive and Warehouse Coverage: Including archived quotes/orders alongside posted and unposted physical inventory and transfer records makes these APIs particularly useful for compliance audits, third-party logistics (3PL) handoffs, and customer service lookups.

The Copilot Studio and MCP Server Connection​

The most telling detail in Microsoft's roadmap and release plan documentation is the explicit nod to Microsoft Copilot Studio and the MCP Server for Business Central alongside Power Automate.

In traditional ERP automation, an integration developer might build a deterministic Power Automate flow: When a sales shipment is posted, fetch the PDF and email it to the freight forwarder. That remains a primary use case.

With Copilot Studio and MCP Server in the mix, the workflow becomes conversational and agentic. Imagine an account manager asking a Copilot agent inside Microsoft Teams, "Grab the PDF for the last sales return order from Fabrikam and the matching return receipt so I can see what hit the loading dock." Instead of forcing the user to open the Business Central web client, navigate to two separate lists, and run print-to-PDF actions, an MCP-connected agent can query the read-only document report APIs, pull the rendered PDFs, and surface them directly in the chat thread.

Under the Hood: How Business Central Handles PDF and Read-Only API Calls​

While Microsoft's high-level release plan entry lists the newly supported document categories without printing the exact URL path for every single inventory or assembly object, Microsoft Learn's developer documentation for Business Central APIs establishes the foundational patterns for how PDF content and read-only requests operate in the platform.

1. The Standard pdfDocument Retrieval Pattern​

In Business Central's documented API v2.0 architecture, every resource lives within the context of a parent company, requiring the company ID in the URL. When querying a standard pdfDocument object (such as on a sales invoice), a GET call to the resource returns a JSON payload containing the document's id, parentId, parentType, and a [email][email protected][/email] URL.

To fetch the actual binary PDF file directly in the response body (returning HTTP 200 OK), Microsoft Learn's Tips for working with APIs guide illustrates calling the /content route with a bearer token and no request body:

GET businesscentralPrefix/companies({id})/salesInvoices({salesInvoiceId})/pdfDocument({salesInvoiceId})/content
Authorization: Bearer {token}
Accept-Language: en-US
Data-Access-Intent: ReadOnly

(Note: The endpoint above is Microsoft's documented example for a sales invoice; integrators should verify the exact entity route names for the newly added warehouse, archive, and assembly reports within their target environment.)

2. Controlling Report Language On the Fly​

One practical trick buried in Microsoft Learn's API developer tips is the Accept-Language HTTP header. When an external service or Copilot agent requests a rendered report PDF, passing a header like Accept-Language: en-US overrides the default language settings for that web service response. It controls both the report display language and regional formatting (such as date and time layouts), which is vital when a centralized ERP tenant generates shipping or purchasing PDFs for international suppliers and customers.

3. Understanding Data-Access-Intent: ReadOnly​

Because these document report APIs are built for read-only querying, enterprise architects should also keep in mind how Business Central handles the Data-Access-Intent: ReadOnly HTTP header. According to Microsoft Learn's developer documentation:

• Specifying ReadOnly tells the platform that the caller only intends to read records, allowing the page or query to read data from a secondary database replica (if available) and reducing load on the primary transactional database.
• However, Microsoft cautions that ReadOnly does not guarantee execution on a secondary replica in every scenario—it simply states that the request only requires read ability.
• Furthermore, in Business Central online, sending an OPTIONS request with Data-Access-Intent: ReadOnly can change the returned Allow header, excluding modification methods (POST, PATCH, PUT, DELETE) that would otherwise appear under ReadWrite.

Practical Guidance: What IT Admins and Integrators Should Check​

Even though Microsoft states this feature is enabled for end users automatically in General Availability, "enabled in the platform" does not mean an external Power Automate flow or Copilot Studio agent automatically bypasses security or knows where to look.

If you are planning to wire up these document report PDFs to external tools, keep several operational boundaries in mind:

1. Do Not Assume Invoice Routes Match Every New Document Type: The release plan confirms which 31 sales, purchasing, inventory, and assembly documents are supported, but it does not list the literal endpoint strings, licensing prerequisites, or API throttling limits for each one. Always inspect the live $metadata endpoint in your Business Central environment (GET <endpoint>/$metadata) to confirm the exact entity set names and navigation properties exposed by the document report system.
2. Watch Out for Archived Release Plan Links: If your team bookmarks Microsoft's traditional Dynamics 365 release plan pages, note that Microsoft retired those standalone release plan updates beginning in September/October 2026. Active tracking for Dynamics 365, Power Platform, and Dataverse features now lives alongside Microsoft 365 on the unified AI at Work roadmap (where this feature resides under ID 576792).
3. Verify Permissions for Service Principals and Agents: Automatic feature enablement means the APIs are present in the service, not that every Entra ID app registration or user account has permission to read warehouse, purchasing, or sales history. Ensure that the security context used by your Power Automate connection or MCP Server has appropriate read permissions for the underlying sales, purchasing, inventory, or assembly tables before troubleshooting empty or rejected PDF calls.

By bringing secondary documents—like physical inventory recordings, transfer shipments, and archived quotes—into the same programmatic PDF fold that invoices have enjoyed for years, Microsoft is removing one of the quietest friction points in ERP integration. Whether you are feeding a battle-tested Power Automate pipeline or building your first autonomous supply-chain agent in Copilot Studio, the paperwork is finally ready to travel via API.