*This article was updated for accuracy and relevance on 4/22/2025.

The latest SmartConnect on Premise update adds access to custom Business Central APIs using the current Dynamics 365 Business Central OData connector.  This will allow SmartConnect to query data as a source and send data as the destination to any custom API endpoints without needing any additional connections.

On the Dynamics 365 Business Central OData Setup window there is a new option at the bottom that will show all Api Routes available in your Business Central environment.  Check the box next to the custom API to make it available as a data source and destination. The v2.0 will be enabled by default as this is the API that SmartConnect has been using to connect to the standard Business Central API in previous releases.

BCOdataAPIConnector 5

Data Source

The new API Route field on the Dynamics 365 Business Central Odata Api Query will now allow you to choose a custom API and give access to the entities within the API.  Any linked entities can be added by clicking the plus button on the main entity.

BCOdataAPISource

Destination

Send Data to Custom APIs

In 21.1.0.1633 or newer, there are two destination types that support Odata API integrations.  

Dynamics 365 Business Central OData Deep Insert
The integration process window now includes an API Route dropdown in the destination settings, where you can choose a custom API and add related services. SmartConnect will create nodes for the main and linked entities, which you can map just like any other destination. 
When you run the integration, records are sent using a deep insert—meaning the parent and any child entities are delivered in a single create API call. That’s fast, clean, and ideal for maintaining data integrity.  

Dynamics 365 Business Central OData API
In versions before 21.0.1.1633, this was the only option, but has now been renamed to Dynamics 365 Business Central OData Deep Insert as mentioned above.  This destination type supports creating and updating records and allows document rollback if a child record fails. It uses a parent field to allow linking parent to child records without the need of a lookup.  It also allows the use of Actions which allow further record processing options.

BCOdataAPIDestination

If you have questions or need help with this feature, contact us at sales@eonesolutions.com