Platform · Module · Data API

One checked query, as a secure API.

With the ENABLE data API, you publish a saved SQL query as a REST endpoint on your own data warehouse. Other systems fetch the result with their own API key, via a fixed URL and an OpenAPI specification. Each publication gets a version number, so you always see what is running and can roll back.

Book a demo All modules

enable.dataanalytics.nl/acme

EnglishClient adminSV

Publish as API

Saved query · revenue-by-region · version 3

Endpoint

Endpoint slugrevenue-by-region

URLGET/api/v1/queries/revenue-by-region

X-API-Keyak_••••••••••••3f9a

Rate limit60 requests / min

AccessRead-only

View OpenAPI specification

Test call 200 OK · 184 ms

{
  "query": "revenue-by-region",
  "version": 3,
  "rows": [
    { "region": "South", "revenue_2026": 1421300 },
    { "region": "North", "revenue_2026": 1284900 },
    …
  ]
}

A data API makes figures from your data warehouse available to other systems, without those systems needing access to your database. In ENABLE you do this by publishing a query you have already written and checked in the SQL Explorer. That query becomes a REST endpoint that another system can call with an API key.

The big advantage: everyone fetches the same, verified figures. The definition of "revenue" or "open orders" lives in one place, in one query with a version number, and not in five different scripts or exports.

Endpoints are read-only. They run in a read-only transaction on your data warehouse, with a row limit per endpoint and a rate limit per caller. Only client admins can publish queries.

Features

What Data API does

Publish from the SQL Explorer

Save a query, choose a short name for the URL and publish. The endpoint uses exactly the SQL you tested, not a copy that drifts apart later.

API key per endpoint

Each endpoint gets its own key. ENABLE shows it once and only stores a hash. If a key leaks, you replace it with one click.

Typed parameters

Make a query flexible with up to twenty parameters, such as a date or customer code. For each parameter you choose text, number, date or yes/no, required or with a default value.

Versions and rollback

Each publication gets a new version number. The version history shows who published when, and you restore an earlier version as a new publication.

OpenAPI specification

ENABLE generates an OpenAPI 3 specification of all your published endpoints, with parameters, row limit and security. Developers can get started with it straight away.

Row limit and cache

Set a maximum number of rows per endpoint (5,000 by default, up to 50,000). The response tells you whether the result was truncated. Optionally, cache responses for up to an hour.

Switch off and logging

Switch an endpoint off when it is no longer needed. Publications are recorded in your organisation's activity log, with version and row limit.

A data API on your data warehouse: how it works

You can set up an API on your data warehouse in two ways: give other systems a database account, or put a controlled layer in between. The first is quick, but then every system can read every table and everyone writes their own SQL. The second is what the ENABLE data API does.

For each endpoint you decide which query runs, which parameters are allowed and the maximum number of rows returned. Parameters are passed to the database as bound values, never pasted into the SQL as text. That prevents SQL injection via the URL.

What a request looks like

A system sends a GET request to the endpoint's address, with the API key in the X-API-Key header (or as a Bearer token) and any parameters in the URL. The response is JSON.

Part	Content
Address	/api/v1/queries/[slug], with parameters such as ?from=2026-01-01
Key	X-API-Key header, or Authorization: Bearer
Response: data	The rows of the result
Response: meta	Row count, version number, truncated yes/no, timestamp
Error codes	401 without a valid key, 400 for an invalid parameter, 429 for too many requests

Exposing data via an API: typical uses

The data API is meant for situations where another system or a script needs the same figures as your dashboards. A few examples:

Other systems: a website, CRM or planning tool that fetches stock levels, prices or KPIs every day.
Custom apps: apps in the portal read data through approved endpoints, pinned to a version of the query.
Automation: scripts and integration tools that fetch an overview at set times and process it further.
AI assistants and agents: give an agent access to one scoped query instead of your whole database.
Custom dashboards: the data sources of the dashboard builder (pilot) are also published queries.

Securing and managing your endpoints

Only client admins publish endpoints. The API key is stored only as a hash, so even platform admins cannot read it back; if it is lost, it is replaced. An endpoint you switch off stops responding immediately, and if an organisation is suspended, all its endpoints stop.

The rate limit of 60 requests per minute applies per endpoint and per IP address. A system that asks too often receives a 429 response with a wait time. Every execution runs read-only on your data warehouse, over the same secure connection as the SQL Explorer.

In ENABLE

How to publish a data API in ENABLE

01
Write and save the query
Write and test the query in the SQL Explorer, yourself or with help from the AI, and save it under a recognisable name.
02
Publish the endpoint
Choose the name in the URL, define the parameters and their types, and set the row limit and any caching.
03
Store the key safely
Copy the API key straight into the system that will use it. ENABLE shows it only once.
04
Call and manage
Share the OpenAPI specification with the developer. Publish new versions, roll back to an old version or switch the endpoint off.

Book a demo How the platform works

FAQ

Frequently asked questions

What is a data API?

A data API is a fixed web address through which a system requests data without having access to the database itself. In ENABLE, each endpoint is a published, read-only SQL query on your own data warehouse, secured with an API key.

How do I secure an API on my data warehouse?

In ENABLE, each endpoint has its own API key that is stored only as a hash, a fixed query, typed parameters and a rate limit of 60 requests per minute per IP address. You also set the row limit yourself and restrict the query to the data the consuming system is allowed to see.

Can I also write data with the data API?

No. The ENABLE data API is read-only: endpoints run a SELECT query in a read-only transaction. To load data into your data warehouse, you use a separate integration.

What limits apply to the data API?

Each endpoint accepts 60 requests per minute per IP address. By default an endpoint returns at most 5,000 rows; you can raise that per endpoint to 50,000. The response tells you whether the result was truncated.

Is there documentation for developers?

Yes. ENABLE generates an OpenAPI 3 specification of all your organisation's published endpoints, with parameters, types, row limits and the authentication method. You can import it into most API tools.

Share securely, live fast, no headache

In an online demo we show you the portal: dashboards per role, row-level security, plain-language questions and how we set it up and manage it for you.

Book a demo info@enableyourdata.nl