Onehouse
Onehouse is a fully managed universal data lakehouse platform, built by the original creators of Apache Hudi. It provides near real-time data ingestion (CDC and streaming), incremental ETL/ELT pipelines, automated table optimization (compaction, clustering, cleaning), and open table-format interoperability across Apache Hudi, Apache Iceberg, and Delta Lake via Apache XTable. Onehouse Cloud, the Quanton execution engine, OneFlow ingestion, Open Engines, and LakeView are exposed programmatically through a control-plane SQL Command API plus Status API, an official Python SDK, an `oh` CLI, and a Terraform provider, letting data teams manage lakes, databases, tables, flows, and clusters as code while data stays in the customer's own VPC.
Onehouse publishes 1 API on the APIs.io network. Tagged areas include Company, Developer Tools, Data Lakehouse, Data Engineering, and ETL.
Onehouse’s developer surface includes documentation, API reference, engineering blog, signup flow, changelog, CLI, authentication, and 16 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Onehouse API
Control-plane REST API for Onehouse — a SQL Command API to create and manage lakehouse resources (lakes, databases, tables, flows, clusters, jobs, transformations) plus a Status...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API