Skip to main content

Choosing the Right Integration Approach

Ardoq has multiple ways for ingesting data depending on the tools and services you want to connect to.

G
Written by Gleb Nikonov
Updated today

Overview

Ardoq has support for a number of out-of-the-box integrations, as well as three variants of custom integrations with differing levels of complexity.

For common integrations, we recommend using the out-of-the-box integrations developed by Ardoq for the most stable and comprehensive integration experience. We maintain integrations for the most common IT tools, including Microsoft Azure, Microsoft Entra ID, ServiceNow, among with several others.

For custom integrations, we offer three methods of integration with differing levels of complexity:

  1. Import Builder: A tool within Ardoq that allows you to configure a connection to a third-party RESTful API β€” similar to query-building tools like Postman or Insomnia. The Import Builder is useful because all configuration is done within Ardoq and does not require hosting or custom development. For more details, read our help article.

  2. Import API: The Import API is a mixed-use solution that combines Ardoq configuration mapping with a JSON payload containing the data you want to import into Ardoq. This solution is useful when you have a data source that provides a JSON output and your system is capable of making a POST request to Ardoq. In many cases, this is a lower effort integration than the fully-custom API integration. For more details, read our help article.

  3. REST API: Ardoq's API for complete programmatic control over creating, updating, and deleting component and reference data in Ardoq. This is the recommended approach for complex and custom-use integrations that cannot be covered by Ardoq's out-of-the-box integrations or the simpler integration tools like the Import Builder. See our developer portal for more details.

Custom Integrations

Refer to the chart below to get a feeling for how much effort will be required to integrate your data. While the Import Builder is entirely hosted within Ardoq, a fully-custom integration requires you to run your own servers to send data to Ardoq.

Import Builder

Import API

REST API

Hosting required

No

Yes

Yes

Coding required

No

Minimal

Yes

Built-in data mapping

Yes

Yes

No

Upsert support

Yes

Yes

Yes

Deletion support

Limited

Limited

Full

Scheduling

Built-in

Self-managed

Self-managed

Supported data sources

REST APIs*

Any JSON

Any

Customization

Low

Moderate

Full

Complexity

Low

Moderate

High

Best for

Connecting to standard APIs with no code

Importing data from JSON sources

Advanced integrations with custom business logic

*The Import Builder is flexible and can support many different pagination and authentication schemes, but it may not work with some APIs due to small implementation differences.

Did this answer your question?