Integration Library

Business Central and B2B Portals: APIs, Webhooks and Synchronisation

Architecture recommendations for B2B portal integration using Microsoft Dynamics 365 Business Central APIs and webhooks.

Codariva ·

  1. Business CentralMaster records and commercial rules
  2. Authorised integration serviceMapping, queuing and result checks
  3. Dealer portalPermitted views and transaction requests
Example architecture: products, prices and stock move from ERP to portal; order requests move from portal to ERP. Ownership and acceptance conditions are defined separately for each data type.

In a B2B portal connected to Dynamics 365 Business Central, the issue is not simply transferring orders. Changes must be detected promptly, concurrent requests managed and data kept current without exceeding API limits.

The difference between APIs and webhooks

An API allows a portal to request specific data or actions. A webhook helps notify a subscribing system when a supported resource changes. Microsoft's Business Central documentation explains that creating a webhook subscription requires a verification handshake using validationToken .

The recommended approach is therefore to receive available events through webhooks and retrieve record details through the API when needed, rather than download every record every few seconds.

Example flow

  1. The dealer portal verifies identity and roles.
  2. The user creates an order request.
  3. The portal adds a record to the integration queue with a unique order ID.
  4. The authorised backend starts the required operation through the Business Central API.
  5. The API response is recorded; failures are not reported to users as successful.
  6. Supported changes reach the portal through webhooks or controlled synchronisation.

Why do API limits matter?

Microsoft documents limits and the 429 Too Many Requests response for Business Central APIs. This requires a cooldown and controlled retries. Processing large transfers in batches and using webhooks where appropriate can reduce load.

Priority tests

  • Is the subscription validation request answered correctly?
  • Does a repeated webhook create duplicate operations?
  • On a 429 response, does the task return to the queue without being lost?
  • Can each dealer see only their own commercial data?
  • Are waiting and error messages clear when operations take longer?

When is custom software appropriate?

Custom design may be worthwhile when you need regional price lists, approval levels, a dealer-role hierarchy and operational reports beyond a standard ordering screen.

What should you check if a subscription goes silent?

Business Central subscriptions expire unless renewed; creation and renewal require a validation response. Check webhook support for the resource and the subscription's expirationDateTime value. Notifications may be delayed or cover multiple changes; do not interpret them as a guarantee of immediate, exactly-once delivery for each record. Microsoft webhook documentation.

Example scenario: Suppose the portal's catalogue copy is stale after a price change. The receiving service first verifies the validation information, persists the task, then retrieves the required record through the API. If the same record arrives again, older data must not overwrite newer data. When a subscription is interrupted, changes since the last successful sync are compared in a controlled manner.

Check Expected result before launch
Renewal fails Alert the owner; do not silently present the data as current
Duplicate notification No second order or duplicate side effect
Incorrect dealer identity Deny access on the server, not just through a UI filter
No data for an extended period Check subscription health and data freshness separately

For API error distinctions, see the 429 guide and 504 guide.

Is access the same for online and on-premises installations?

This guide covers Business Central API v2.0 and supported webhook resources. Verify the online environment's tenant, environment and company IDs separately from an on-premises installation's version, API exposure and identity provider. For server-to-server access, the Microsoft Entra application must also be registered in Business Central with the required permission sets. Obtaining a token does not authorise access to all company data. Microsoft S2S access requirements.

Prepare before the pilot: installation type and version, a test company, relevant API resources, application permissions, webhook support, confirmation of licensing and usage eligibility by the client's responsible person, and expected daily transaction volume. Agree an authorised access method rather than sending secrets or tokens.

Example ownership decision: Products, prices, stock and account information are read from the ERP; the portal sends order requests and shows the results accepted by the ERP. Two-way transfer does not mean both systems may freely change the same field. Document which fields can be changed in the portal and which system decides conflicts. If an existing connector meets the standard dealer flow, evaluate its scope and maintenance terms first.

Sources and verification

Example flows are architectural recommendations, not claims of completed client projects or vendor partnerships. Technical sources checked: 17 October 2026. Installation version, licence and permissions must be verified separately.

Adapt it to your business workflow

ERP integration planning guide. Explore the B2B portal development scope for further reading; we can assess your current process together.

Let's discuss your needs →