Key Takeaways:
- Business Central API integration connects Microsoft Dynamics 365 Business Central to other systems using REST endpoints and OAuth 2.0.
- Six integration types cover most SMB needs: finance sync, CRM to ERP, e-commerce, Power Platform, custom AL extensions, and AppSource apps.
- Standard REST fits most cases. Custom AL is for unique data. Power Automate handles simple no-code flows.
- Most failed projects fail on five avoidable mistakes, not on bad tools.
Business Central API integration connects Microsoft Dynamics 365 Business Central to your CRM, online store, bank, and custom apps so data moves automatically instead of by hand. Done well, it saves days of manual work every month... Done wrong, it stalls at OAuth and never ships.
Whether you are the decision-maker approving the Business Central API integration budget or the IT lead figuring out build versus buy, this guide walks through what actually matters.
Turn Business Central Into a Connected System
Talk to a Canadian Microsoft Solutions Partner about scoping the right integration path for your setup.
Free discovery call
What Is Business Central API Integration, and Why Should Your Business Care?
Business Central API integration is the process of connecting Microsoft Dynamics 365 Business Central to other software using its built-in REST APIs. It lets data move automatically between your ERP and the systems around it… without spreadsheet exports or manual copy-paste.
For a Canadian SMB running Business Central, the payoff is practical. Sales orders from your Shopify store land in the ERP without a human touching them. Customer records stay in sync between Dynamics 365 CRM and Business Central. Bank feeds and EFT payments reconcile in the background. Power BI dashboards refresh from live ERP data instead of yesterday's export.
The reason it matters right now: Microsoft has locked down the old cloud shortcuts. For Business Central SaaS, basic authentication is completely gone. If you want any third-party tool to interact with Business Central Online, it must authenticate via OAuth 2.0 and route through the API layer. Legacy back doors are closed.
What Does a Business Central API Integration Actually Let You Do?
At a practical level, a Business Central API integration lets you read, create, update, and delete records inside the ERP from an outside system. That covers most day-to-day operations:
- Sync customers, vendors, items, and pricing between systems.
- Push sales orders, invoices, and journal entries into the ERP automatically.
- Pull inventory levels, financial data, or job status into another platform.
- Trigger workflows in Power Automate, Teams, or a custom app when something changes.
- Feed live data into Power BI, Excel, or a reporting tool.
If you can describe the outcome in a sentence, there is almost always an API path to get there.
How Does Business Central API Integration Actually Work Under the Hood?
At the highest level, a Business Central API integration runs on a REST API built on the OData v4 standard. Your app sends an HTTPS request to a Business Central endpoint. Business Central checks your identity, runs the request, and sends back a JSON response. That is the whole model.
The two moving parts you need to understand before scoping any project are the endpoints and the authentication layer. Everything else is detail.
What Endpoints Will You Actually Use?
The standard endpoint structure looks like this: https://api.businesscentral.dynamics.com/v2.0/{tenant}/{environment}/api/v2.0. From there, you work with standard entities. /companies returns the list of companies in your tenant.
Because data lives inside a company, you append the company ID to query records: /companies({id})/customers or /companies({id})/items. Custom entities built by your developers show up under their own dedicated publisher routing paths (e.g., /api/{publisher}/{group}/{version}). Standard OData queries like $filter and $select let you narrow the response.
How Does Authentication Work Now That Basic Auth Is Gone?
Every call to a Business Central API uses OAuth 2.0 through Microsoft Entra ID. In plain English: you register your app in Entra ID, grant it permission to talk to Business Central, and use a client ID and secret to request a short-lived access token. That token rides along with every API call.
For server-to-server integrations that run without a user signed in, you use a service principal with the client credentials flow. This is the pattern for scheduled syncs, webhooks, and background automation. For anything customer-facing, you use delegated permissions so the API acts on behalf of a signed-in user.
Tokens expire. Refresh logic is not optional. If your integration hangs at 3 a.m. on a Sunday, it is almost always a token issue.
What Are the 6 Most Common Business Central API Integration Types You Can Build?
Not every Business Central API integration is a custom build. Most Canadian SMBs land on one of six patterns. Knowing which pattern you are in shapes the scope, the timeline, and the budget before a single line of code is written.
1. Finance and Accounting Sync (Bank Feeds, EFT, Accounts Payable)
This connects Business Central to your bank, your payment processor, or an AP automation tool like Continia. Bank transactions flow in for reconciliation. Vendor payments flow out through EFT. Invoices from a capture tool become purchase invoices without rekeying, and month-end close cycles shrink from weeks to days once the loop is closed.
Best fit: Finance teams closing the month faster.
Effort: Low to medium with existing connectors. Higher for custom bank formats.
2. CRM-to-ERP Data Flow (Dynamics 365, HubSpot, Salesforce)
Sales opportunities close in the CRM and turn into sales orders in Business Central. Customer records stay in sync so finance and sales stop arguing about the address. If you run Dynamics 365 CRM, the connector is native. For HubSpot, a scoped HubSpot Dynamics 365 integration handles it.
Best fit: Teams where sales and finance run on separate systems.
Effort: Low with native connectors. Medium with custom field mapping.
3. E-Commerce Order Sync (Shopify, WooCommerce, Magento)
Every online order becomes a Business Central sales order. Inventory levels push back to the store so you do not oversell. Customer and product data stays consistent across channels. Most Canadian SMBs use a middleware app for this, but a direct API build is possible for higher volumes.
Best fit: Retailers running one ERP behind multiple sales channels.
Effort: Low with a pre-built middleware. High for direct custom integration.
4. Power Platform Automation (Power Automate, Power BI, SharePoint)
This is the no-code and low-code lane of Business Central API integration. Power Automate flows can create records when a form is submitted, an email arrives, or a Teams message posts. Power BI reads live financial data for dashboards. SharePoint stores related documents through the SharePoint connector for Business Central.
Best fit: Teams with a citizen developer or a Power Platform license already.
Effort: Low for simple flows. Medium for anything with error handling.
5. Custom AL Extensions Published as Business Central API Integration Endpoints
When your business logic or data model does not match a standard entity, you build a custom API in AL, the Business Central programming language, and publish it as an extension. Your app calls that custom endpoint the same way it calls a standard one. Modern features like AI in ERP often live at this layer.
Best fit: Unique data, industry-specific processes, or logic that must live in the ERP.
Effort: High. Developer project with versioning discipline required.
6. Third-Party ISV Add-Ons From Microsoft AppSource
You skip the build entirely and install a certified app from Microsoft AppSource. The ISV has already done the API work, passed Microsoft's certification, and maintains compatibility across updates. You handle the configuration and pay a subscription.
Best fit: Common problems that already have a market solution, like document capture, EDI, or payroll.
Effort: Low. Configuration only.
Most of these types touch page customization or extensions at some point. If you want to see what that looks like inside the product before scoping a project, this quick walkthrough helps.
Which Business Central API Integration Path Fits Your Business?
Three paths cover almost every project. Picking the wrong one is the most expensive mistake in this space, and it usually happens before anyone writes code.
If you are still evaluating options, our overviews of what a Business Central Partner does and how a Business Central Consultant scopes a project both cover what to look for before signing anything.
When Should You Use the Standard Business Central API Integration Approach?
The standard REST API is the right choice when the data you want to move already lives in a standard Business Central entity: customers, vendors, items, sales orders, purchase invoices, journals. If a standard endpoint exists for what you need, use it.
You get faster delivery, less code to maintain, and no risk of your integration breaking when Microsoft updates the platform. Most SMB projects fit here and never need anything more.
When Does a Custom Business Central API Integration Make More Sense?
You need a custom Business Central API integration when your data or logic does not fit the standard model.
Common triggers: an industry-specific field no standard entity carries, or a calculation that must run inside the ERP before data leaves. Another one: a workflow that touches five entities at once when you do not want five separate calls.
Custom means AL. AL means a developer. It also means versioning your API from day one so future changes do not break the systems calling it.
When Is Power Automate the Right Choice Instead?
Power Automate wins when the workflow is simple, the volume is low, and you want the business team to own it. Approvals, notifications, moving a record from a form into Business Central, sending a Teams message when an invoice is posted. These fit inside a flow you can build in an afternoon.
The limits show up fast at scale. If you are processing thousands of records an hour, Power Automate will throttle you and the flow will queue. That is a signal to move to a real Business Central API integration.
Get a Second Opinion Before You Build
A short call with a Gestisoft consultant can save weeks of trial-and-error on the wrong integration path.
Book a free consultation
What Do You Need Before Starting a Business Central API Integration?
Every project that ships on time starts with the boring prep. Every project that misses a deadline skipped it. Here is the checklist for a Business Central API integration you will not regret.
Licenses, Permissions, and Roles You Will Need
You need a Business Central subscription that includes API access, which every current online SKU does. You need admin rights to register an app in Microsoft Entra ID. Inside Business Central, you need a permission set assigned to the service account that will run the integration. The built-in "D365 AUTOMATION" set covers most cases.
Create a dedicated service account. Do not run production integrations under a real user. If that user leaves the company, your integration dies with their license.
Setting Up Your Sandbox Before You Touch Production
Provision a sandbox environment from the Business Central admin center. Rate limits and throttling behave differently in sandbox, which matters when you test load. Deploy every custom AL extension to sandbox first, test the full flow, and only then promote to production.
Sandbox is free. Downtime in production is not.
If you want to see how far you can go without touching code, our guide on how to customize Business Central walks through page personalization for users and profile-based customization for admins. A lot of what teams think needs a custom API can be solved by adjusting the right role profile first.
Is Your ERP Even the Right Fit to Integrate?
Download our free guide to the 10 key criteria that matter most when choosing the right ERP for your business.

What Are the Biggest Business Central API Integration Mistakes That Cost SMBs Time and Money?
Most failed integrations are not killed by hard problems. They are killed by five small ones nobody catches until production. All five are avoidable.
Ignoring Sandbox Rate Limits Until You Hit Production
Sandbox limits are lower than production limits on purpose. Teams that only load-test in sandbox assume the throttling they see is what production will do. Then production sends double the volume without warning and floods the queue. Test at expected peak volume in production before go-live, not just in sandbox.
Skipping Client Secret Rotation Until Auth Breaks at 2 A.M.
OAuth client secrets expire. Teams create a secret, ship the integration, and forget it exists. Twelve months later the secret expires, every API call returns 401, and the integration is dark until someone with admin rights logs in. Rotate secrets on a schedule and use dual-secret rotation so you never have downtime.
Hardcoding Company IDs and Environment Names
Every Business Central tenant assigns a unique company ID. Environments are named "Production," "Sandbox," or whatever the admin picked. Hardcoding these values in your integration code means every new company, every environment rename, and every tenant migration breaks the build. Store them in configuration, not source code.
Forgetting to Version Your Custom APIs
If you publish a custom API and later change a field name or add a required parameter, every system calling the old shape breaks silently. Version your APIs from the first release. v1.0 today, v2.0 when the contract changes. Old and new run side by side until every consumer migrates over.
Underestimating Multi-Currency and Bilingual Setups
Canadian SMBs regularly run CAD and USD side by side, with French-language customer records, French address formats, and Québec-specific sales tax rules. Integrations built for a single-currency English-only setup break the first time a French address hits a validation rule or a USD invoice posts against a CAD bank feed. Design for both from day one.
For teams thinking about analytics, our piece on ERP with Power BI integration shows what changes when live Business Central data feeds Power BI dashboards, giving you customizable views, real-time financial visibility, and better decisions than standard ERP reports alone.
-
Yes. The REST API is included in your Business Central subscription. You pay for the development effort, plus any middleware, ISV app, or Power Platform license you layer on top. However, while it is financially free, it is operationally limited.
Why Choose Gestisoft for Your Business Central API Integration?
Gestisoft is a Canadian Microsoft Solutions Partner founded in 1997, a Microsoft partner since 2004, with offices in Montréal, Toronto, Ottawa, and Québec. Bilingual English and French delivery is standard. B Corp certified... Great Place to Work certified… Nearly three decades of business software experience across the ERP and CRM space.
For a Business Central API integration project, that background matters in three practical ways.
- First, Canadian SMB fluency: multi-currency, bilingual data, EFT, Québec sales tax, and Canadian banking conventions are the default, not a learning curve.
- Second, Microsoft Solutions Partner status: our consultants work inside the same certification framework Microsoft uses.
- Third, we cover the full lifecycle from scoping to go-live to post-launch support, so the integration does not become someone else's problem.
The value shows up most when a project runs into internal friction: changing scope, shifting priorities, or a system messier than expected. That is where partner responsiveness separates a working integration from a stalled one.
Here’s what one of our clients said after working with us:
Gestisoft was very responsive and proactive in adapting to the internal challenges we faced and ensuring that we met our objectives. We were very impressed with the work of everyone involved in the project.
Once the scoping is clear, the next step is a short conversation to map your specific systems, timeline, and constraints.
Move From Planning to Building
We have delivered Business Central projects across finance, distribution, manufacturing, and services in Canada. Let us map yours.
Book a free consultation
Liked what you just read? Sharing is caring.
August 12, 2026 by Muhammad Ali Iqbal by Muhammad Ali Iqbal SEO Content Strategist & Copywriter
Driven by a passion for search engine optimization, strategic content, and conversion-focused writing. A copywriter and content strategist who lives for content that ranks, engages, and delivers real business results.


