Connector

Enable business reporting from your Databricks data

Turn your data warehouse into a real reporting library. Connected Data Marts, ready for your apps and scripts.

DatabricksConnected
Data MartPublishedone definition
APIDaily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get started free

Hand this to your AI

Scripts that need Databricks numbers each carry a copy of the SQL, and nobody updates them all when a definition changes.

Paste this into your AI assistant. It builds a Data Mart on your Databricks tables with OWOX Data Marts and serves its rows over HTTP, so every script reads the current definition.

The prompt

build a Data Mart on my Databricks tables and let my scripts read its rows over HTTP with an API key, aggregated into weekly buckets, so the SQL lives in one place

S01 · Step 1

Start from your Databricks data

Pick the Databricks catalog and schema that hold the data your apps will read.

  • Nothing to move or copy: your Delta tables stay in Databricks.
DatabricksYour data warehouseCatalogmainSchema
Unified Ad SpendConnected dataNothing to move or copy

S02 · Step 2

Build a reporting library in Databricks

Each Data Mart is a ready report over your Databricks tables, described by AI, and joins to other Data Marts through the data model.

  • Business users browse reports, not tables.
Data martsUnified Ad SpendAISessionsAI
Unified Ad SpendData modelplatform_roas · platform_cpa
Unified Ad Spend + Sessions
SessionsJoined by a shared key

S03 · Step 3

Serve Databricks data through an API

A client asks for a Data Mart's rows over HTTP and gets rows back, with aggregations and date buckets.

  • Your apps read the same Data Mart as every report.
Your app or scriptHTTP request
APIUnified Ad SpendRows over HTTP
JSON rowscostInUsdclicksimpressions

S04 · Step 4

Keep your API connected to the same data

Ask in Claude, export to a sheet, share with the boss.

  • One source, every tool.
Unified Ad SpendOne source
ClaudeAsk in chat
Google SheetsExport to a sheet
Your bossShare the answer

Recent updates

Why OWOX

Why OWOX for Databricks and an API

Your own apps and scripts read governed Data Marts from Databricks over HTTP.

  • You own the data. Your data lives in your own Databricks lakehouse; your apps read the Data Marts you publish.
  • Defined once in SQL. Analysts define metrics on your Delta tables once; every Data Mart and every destination reuses them.
  • Rows, not dashboards. Fetch a Data Mart's rows with aggregations and date buckets, per Data Mart or per report.
  • One Data Mart, every tool. The Data Mart your script reads is the one feeding your spreadsheets and dashboards.

Book a callGet started free

Trust

The Data Partner You Can Trust

users

166K Source: Internal OWOX data as of 2026-11-15

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

171K3

In Open Source We Trust

Customers