Reference · built on requestConnectorERP & finance

Microsoft Dynamics 365 Business Central

Customers, sales orders, invoices, items, journals, and ledger entries from Business Central through API v2.0 and webhooks.

Request accessPricing ↗

About

Dynamics 365 Business Central is Microsoft's ERP for small and midsize companies. API v2.0 is an OData REST endpoint at api.businesscentral.dynamics.com, enabled by default online, with one path per environment and company. Webhook subscriptions notify a URL when customers, items, sales orders, invoices, journals, and other entities change.

An operator on Fibric reads a sales order, its lines, and the customer behind it, watches created, updated, and deleted notifications, and proposes edits or a shipAndInvoice action for your approval. Every proposal leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Microsoft Dynamics 365 Business Central and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • customers, vendors, items, and itemCategories
  • salesOrders with salesOrderLines, salesQuotes, salesInvoices, salesCreditMemos, and purchaseInvoices
  • journals, customerPaymentJournals, generalLedgerEntries, and accounts
  • Webhook notifications with changeType created, updated, deleted, or collection, delivered to a notificationUrl
  • lastModifiedDateTime on documents for incremental reads

Proposed actions

  • Target capability: propose creating or updating a sales order with POST or PATCH salesOrder
  • Target capability: propose shipping and invoicing an order through the shipAndInvoice bound action
  • Target capability: propose deleting a draft sales order with DELETE salesOrder

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Ship and invoice on a schedule you approve

    Read open salesOrders, check stock and credit, and propose shipAndInvoice for each order the reviewer ticks.

    With Order Risk, Unbilled Shipment

  • Catch a customer edit before it breaks billing

    Subscribe to customers and salesInvoices webhooks and flag address or payment-term changes against open documents.

    With Address Repair, Dunning Cadence

  • Reconcile ledger entries to the board pack

    Read generalLedgerEntries and journals nightly and compare totals with the numbers on your reports.

    With Metric Reconciliation, Month-End Cutoff

Requirements

  • A Business Central online environment; APIs are enabled by default
  • A Microsoft Entra ID app registration and a Business Central user whose permissions bound what the API can read and write
  • The environment name in the endpoint URL, for example https://api.businesscentral.dynamics.com/v2.0/<environment name>/api/v2.0
  • A public HTTPS notificationUrl that answers the validationToken handshake for webhook subscriptions
Authentication
Microsoft Entra ID (OAuth 2.0) for Business Central online; on-premises uses basic authentication with a web service access key as the password.

Limits

  • OData requests are limited per user: 6,000 in a 5-minute sliding window and 5 concurrent, with 429 when exceeded
  • A $batch request holds at most 100 operations; one page returns at most 20,000 entities
  • Webhook subscriptions expire after three days unless renewed; at most 200 per environment
  • Notifications wait 30 seconds; more than 1,000 changes in that window collapse into one collection notice

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Microsoft Dynamics 365 Business Central ↗

Questions and answers

Does Business Central push changes, or must the connector poll?
Both work. A POST to /api/v2.0/subscriptions registers a webhook after a validationToken handshake. Notifications carry the resource path and changeType. Polling with $filter on lastModifiedDateTime is the fallback.
What happens when the webhook endpoint is down?
Business Central retries over the next 36 hours if the subscriber returns 408, 429, or a 5xx code. Any other code stops retries and deletes the subscription.
Are per-user rate limits different for a service principal?
No. Microsoft applies the same operational limits to application users. Throughput rises by spreading requests across more users or service principals.
Ask about Microsoft Dynamics 365 Business Central

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Microsoft Dynamics 365 Business Central through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy