ApivomApivom
Get Demo

Dynamics 365 Business Central API Connector

Microsoft Dynamics 365 Business Central standard APIs — customers, vendors, items, sales quotes/orders/invoices/credit memos with lines, purchase invoices, journals and payments, general ledger entries and the financial statements — registered in Apivom Atlas as 324 routes on your tenant's environment.

What you can do

  • Master data: customers (16 routes), vendors, items and item categories, employees, bank accounts, currencies, payment terms and methods, dimensions
  • Sales documents end to end: quotes, orders, invoices and credit memos with their lines, PDF document and picture endpoints
  • Purchasing and payments: purchase invoices with lines, customer and vendor payment journals, journals and journal lines
  • Finance: general ledger entries, aged receivables/payables, trial balance, balance sheet, income and cash-flow statements, retained earnings
  • 324 routes (152 read-only) generated 1:1 from Microsoft's official Business Central OpenAPI contract; per-request tenant/environment base URL

Use cases

  • Sales documents next to the account — Read a customer's open quotes, orders and unpaid invoices from Business Central and show them on the account record, so sales sees the ERP position without opening it.
  • CRM-won deal becomes an ERP order — Create the sales quote or order in Business Central from the CRM opportunity with its lines, instead of re-keying items, quantities and prices in two systems.
  • Receivables and credit signals — Pull aged accounts receivable and customer financial details on a schedule to flag overdue accounts before the next visit or renewal.

Business Central is Microsoft's cloud ERP for small and mid-sized companies, and its standard API exposes the whole ledger-side of a company: customers, vendors, items and employees as master data; sales quotes, orders, invoices and credit memos with their lines; purchase invoices; journals, journal lines and customer or vendor payments; and read-only financial reports — general ledger entries, aged receivables and payables, trial balance, balance sheet, income statement, cash-flow and retained-earnings statements. Apivom Atlas catalogues 324 of these routes, 152 of them read-only, generated one-to-one from the only OpenAPI contract Microsoft publishes for the standard APIs. Every call is scoped to a company inside a named environment of your tenant: the caller sends an Entra token from an app registration and the tenant/environment base URL, and Atlas forwards and logs. No Apivom product workflow uses Business Central today — Apivom's live ERP connectors are the Penta distributor APIs — so the connector is available to tenants that run Business Central and want quotes, orders or invoices mirrored next to their CRM records, scoped per customer.

Authentication

An Entra app registration in your Microsoft 365 tenant (tenant id, client id + secret) with Business Central API permissions, plus the environment name. The caller runs client-credentials and sends the Bearer token; tenant/environment base URL set per request. Secret encrypted in your Iris tenant.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Which Business Central environments and API version are covered?

The standard APIs (v2.0 path) of any production or sandbox environment of your tenant — the environment name is part of the per-request base URL. Custom API pages you publish from AL extensions and the automation APIs are not in this catalogue.

Is Business Central on-premises supported?

No. The connector targets api.businesscentral.dynamics.com, Microsoft's cloud endpoint; an on-premises deployment exposes the same APIs on its own host and would need a separate connector.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.