Academy
Integrations

Custom integrations via REST API and SQL connectors

Not every system has a native connector on the platform — and not every report is available in the connectors that do exist. For these cases, the platform offers two custom integration paths, capable of retrieving data from any system that provides an API or database access: the REST API stage and the Database stage, both in the data preparation flow of Turbo AI processes.

When to use each path

  • REST API — when the system exposes a REST API. This is the typical path for cloud systems, market services (quotes, reference data), and corporate APIs exposed by the IT team (including via iPaaS or your company’s API gateway). The platform supports the main authentication methods (username and password, token, HTTP signature, and AWS) and automatically handles paginated APIs.

  • SQL Connectors (Database stage) — when there is read access to a database: SQL Server, Oracle, PostgreSQL, MySQL, SAP HANA, Databricks, and Google BigQuery, among others. Access can be direct to the source system database or to an intermediate base (staging or BI), depending on your company’s IT policy. You write the SQL query and precisely control which columns and filters are included in the flow.

The two paths also complement the native connectors: if your ERP has a connector but the report you need is not available there, the system API or database access fills the gap.

Data volume: the deciding factor

Attention: integration via API is not recommended for volumes above 500 thousand records per run — it can cause slowness and failures. For large volumes (full positions, historical bases, ledger), prefer the SQL connector or file exchange.

A common combination: API for low-volume, high-frequency data (quotes, status, records) and SQL connector or files for recurring heavy loads.

Connectivity with internal systems

Systems that run on the company’s internal network — without internet access — can be integrated via site-to-site VPN/VPC: a private, encrypted tunnel between the Dattos environment and your network. The benefit is secure integration, without exposing the system publicly. Setup may involve additional infrastructure costs; contact Dattos support to assess and request it.

Credentials

API and database credentials are stored in Credential Registration (Settings > Credentials), with sensitive fields encrypted, connection testing, and privacy profiles that control who can use them. A registered credential can be reused in multiple stages and processes.

  • REST API stage

  • Database stage

  • ERP stage

  • Introduction to integrations

Was this helpful?