Integrations & API
Connect Business Central to the systems you already run, with interfaces that are documented, secured and observable rather than a script on somebody's laptop.
Contact Us
What usually needs connecting
In practice it is the same handful of flows: orders arriving from a webshop, stock and pricing going back out, payment files to and from the bank, shipments to a logistics provider, invoices into an e-invoicing network, and customer data shared with a CRM. Each of these is a two-way conversation with failure modes, not a one-off export. What happens when the webshop sends an order for an item that was discontinued this morning? When the bank file arrives twice? A integration that only works on the happy path is a support ticket waiting to happen, so we design for the unhappy ones first.
How we build interfaces
Business Central exposes OData v4 and REST APIs natively, and we use them rather than writing into the database. Authentication is OAuth 2.0 against Entra ID, never a shared password in a config file. Where the external system prefers to push, we expose webhooks; where it prefers to be polled, we schedule and throttle appropriately. Every interface gets logging, retry with backoff, and a way to see what happened. When somebody asks why an order from Tuesday never arrived, the answer should take two minutes to find, not two days.
Documented and handed over
You get interface documentation: endpoints, payload shapes, authentication, error codes and retry behaviour. That document is what lets your webshop developer, your logistics provider or your next partner work with the integration without reverse-engineering it. Because we also build web and mobile applications in-house, we can take responsibility for both ends of the conversation. That removes the most common failure mode in integration projects, which is two vendors each certain the problem is on the other side.
What you get
Standard OData and REST APIs
Built on Business Central's own published APIs, never direct database writes that bypass its validation.
OAuth 2.0 and Entra ID
Proper token-based authentication with scoped permissions, not a shared password living in a config file.
Designed for failure
Retry with backoff, idempotent handling of duplicates, and defined behaviour when the other side is down.
You can see what happened
Logging and traceability, so a question about one order on one day takes minutes to answer, not days.
Interface documentation
Endpoints, payloads, authentication and error codes written down, so any developer can work with it.
We can own both ends
We build the web and mobile side too, which removes the two-vendors-blaming-each-other failure mode.
Technologies
Frequently asked questions
What can Business Central integrate with?
Anything with an API or a file interface. Commonly webshops such as Shopify, WooCommerce and custom platforms, Serbian and international banks, logistics providers, CRM systems, e-invoicing networks including SEF, and bespoke in-house applications.
Real time or scheduled?
Whichever the process genuinely needs. Stock levels shown on a webshop usually want near real time; a nightly payment reconciliation does not. Real time costs more to build and operate, so we ask what the business actually requires rather than defaulting to it.
We already have an integration that keeps breaking. Can you take it over?
Usually yes. We start by documenting what it currently does, which is often the first time anyone has. From there we can stabilise it in place or rebuild it properly, and we will tell you honestly which is cheaper.
Tell us which systems should be talking to each other
Contact UsGet Free Estimation
Have a question or want to discuss a project? We'd love to hear from you. Get in touch and we'll respond as soon as possible.
Contact Information
Fill out the form and our team will get back to you within 24 hours.
Location
Serbia