Integrating Business Central: APIs, Webhooks, Events and When to Use Each

Almost every Business Central implementation includes integrations: an e-commerce platform, a shipping system, EDI, a CRM, payroll, a WMS or a data warehouse. Business Central is well suited to this because it is cloud-first and API-first, but the platform offers several patterns, and choosing the wrong one is how integrations end up slow, chatty or fragile. Here is how the options compare.
The main patterns
| Pattern | Direction | Best for |
|---|---|---|
| Standard APIs (v2.0) | External system reads or writes BC | Common entities: customers, vendors, items, sales and purchase documents, journals, G/L entries. |
| Custom API pages and queries | External system reads or writes BC | Entities or fields the standard APIs do not cover, including your own extension tables. |
| Webhooks | BC notifies an external system of changes | Near-real-time sync without polling, such as reacting to new or changed customers or items. |
| Business events | BC raises meaningful business moments | Process triggers such as a sales order released or a document posted, consumed by Power Automate or other subscribers. |
| Power Automate connector | Both | Light workflows, approvals and notifications built by power users. |
| Middleware (Azure Integration Services, iPaaS) | Both | High volume, many systems, transformations, retries and monitoring in one place. |
Standard APIs first
The standard API set covers most master data and documents and is maintained by Microsoft across updates. Start there.
Custom APIs when you need them
When an integration needs fields or entities that the standard APIs do not expose, build custom API pages (PageType = API) or API queries in an extension. Good custom APIs follow the same conventions as the standard ones:
- their own publisher, group and version;
- plural entity set names;
- SystemId as the key, so external systems never depend on internal record numbers.
Push instead of poll
Polling Business Central every few minutes for changes wastes capacity and runs into throttling. Two better options:
- Webhooks: an external service subscribes through the subscriptions API and is notified when records of an entity change. Subscriptions expire and must be renewed, so the subscriber needs to handle that.
- Business events: higher-level signals such as "sales order released", which carry business meaning rather than just "a record changed". Extensions can define their own.
Batch, don't chatter
Creating a sales order with fifty lines through fifty separate calls is slow and fragile. Three tools keep traffic down:
- $batch requests group many operations into one HTTP call.
- Deep inserts create a document with its lines in one request.
- A bound action on a custom API keeps complex processes such as posting in Business Central and gives the caller one clear call to make.
Reliability by design
- Idempotency: store an external reference or correlation ID on documents, and check it before creating, so a retried call never creates a duplicate order or payment.
- Staging tables: for inbound data, land the payload in a staging table, validate it, then create the business document. Errors become visible records instead of lost calls.
- Throttling: Business Central online enforces request limits per environment. Design for backoff and retry, and spread heavy loads outside working hours.
- Monitoring: enable telemetry to Azure Application Insights so failed and slow calls are visible before users notice.
Authentication
Service-to-service integrations should use OAuth 2.0 client credentials with a Microsoft Entra ID app registration. The app is registered in Business Central on the Microsoft Entra Applications page and given only the permission sets it needs.
Choosing the right pattern
- Use standard APIs wherever they cover the data.
- Add custom APIs for gaps, following API conventions.
- Use webhooks or business events instead of polling.
- Use Power Automate for light, user-owned workflows, not for high-volume order traffic.
- Bring in middleware when several systems, transformations and monitoring need one home.
Integration architecture is a core part of our implementations, and fragile integrations are a common reason clients call us for an implementation rescue. If you are planning a Shopify, EDI, WMS or CRM integration, talk to an architect.
Moving from NAV? Old file and database integrations usually need rebuilding, see NAV to Business Central upgrade options.
Frequently asked questions
Should new integrations use OData web services or API pages?
API pages. OData web services published from UI pages still work, but they inherit page logic and change when pages change.
Do webhook subscriptions expire?
Yes. Subscriptions expire and must be renewed, so the subscribing service needs to handle renewal.
How should another system authenticate to Business Central online?
With OAuth 2.0 client credentials and a Microsoft Entra ID app registration, registered on the Microsoft Entra Applications page with only the permission sets it needs. Basic authentication with web service access keys is no longer supported online.
How do we stop a retried call from creating a duplicate order?
Store an external reference or correlation ID on the document and check it before creating, so the same request can be retried safely.


