WaveHouse Cloud API
API by WaveHouse Cloud · rest
WaveHouse Cloud is a managed, multi-tenant analytics platform. This is its API — the authoritative, code-generated (Huma / OpenAPI 3.1) contract that the web console, SDKs, and LLM/agent clients build against. Two API layers 1. Management (/v1/me, /v1/orgs/{org_id}/…, /v1/projects/{project_id}/…): create and administer orgs and projects, manage team members, programmatic API keys and billing. A project is addressed by its project_id alone; its org is the one that owns it. 2. Engine data proxy (/v1/projects/{project_id}/engine/*): a session/key-authorized passthrough to the WaveHouse engine serving the project, for schema discovery, structured and raw SQL query, and saved-query execution. Everything after engine/ is the engine's OWN path (engine/v1/query, engine/v1/pipes/{name}), so the prefix is usable as the base URL of a WaveHouse engine client. Saved queries and access policy are edited on the project's settings routes (/pipes, /access,…
Endpoint: https://api.wavehouse.cloud/
Verification: observed. Source: crawl.
Capabilities (191)
- Liveness check
- OIDC callback: verify the ID token find-or-create the user issue a session
- Begin customer sign-in (redirects to the hosted sign-in with PKCE + state +…
- Sign out (revoke the server-side session and clear the cookie)
- The signed-in customer (identity + their org memberships with approval status)
- Delete your own user account (email-confirmed). BLOCKED (409) while you own an…
- List the agents connected to the signed-in user's account over MCP
- Revoke a connected agent: every token it holds stops working
- Allow a revoked agent again
- Update the signed-in user's display name (first/last) at the identity…
- Read the transfer offer a link names (signed-in owner of the receiving org only)
- Accept a transfer offer — the project moves to your org (signed-in owner of…
- Decline a transfer offer (signed-in owner of the receiving org)
- Mint an identity-widget token for the signed-in user (renders the User…
- Subscribe to the blog newsletter (sends a confirmation email; double opt-in)
- Confirm a newsletter subscription (posted by the confirm page's button)
- Create a new org — you become its owner; the tenant is provisioned…
- Get one of the customer's own orgs (403 if not a member — cross-org isolation)
- Rename the org (owner/admin)
- Schedule the org's deletion (owner only; name-confirmed). The org is suspended…
- Open your org's admin portal to self-configure SSO/SCIM (org owner/admin;…
- List the members' agents that can reach the org over MCP (owner or admin)
- Block a member's agent in this org (owner or admin)
- Lift the block on a member's agent in this org (owner or admin)
- List the org's API keys (owner/admin; prefix and last four characters — never…