# LakehouseBox API

**Canonical:** https://apis.io/apis/lakehousebox-com/lakehousebox-com-api/  
**Provider:** LakehouseBox — https://apis.io/providers/lakehousebox-com/  
**Base URL:** https://api.lakehousebox.com  
**Documentation:** https://lakehousebox.com/docs/api

LakehouseBox API is one of 2 APIs that [LakehouseBox](https://apis.io/providers/lakehousebox-com/) publishes on the [APIs.io](https://apis.io/) network, described by a machine-readable OpenAPI specification. This API exposes 6 JSON Schema definitions. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

LakehouseBox API as documented publicly: 75 operations. Contract generated from the documentation by API Evangelist (2026-11-14); not the provider's own document.

## Operations (60 of 75)

| Method | Path | Summary |
|---|---|---|
| GET | `/.well-known/jwks.json` | The RS256 public key(s) that verify every token this API signs. |
| GET | `/.well-known/oauth-authorization-server` | RFC 8414 metadata an MCP host reads to authorise against the remote MCP server. |
| GET | `/.well-known/oauth-protected-resource` | RFC 9728 metadata of the REST API itself. |
| GET | `/healthz` | GET /healthz → 200 |
| GET | `/jwks.json` | GET /jwks.json → 200 |
| GET | `/oauth/authorize` | The authorization endpoint. The MCP host opens the person's browser here. |
| POST | `/oauth/register` | RFC 7591 dynamic registration, the DEPRECATED fallback for hosts that cannot publish a Client ID Metadata Document. |
| POST | `/oauth/revoke` | RFC 7009: a client that logs out revokes its refresh token (or an access token). |
| POST | `/oauth/token` | The token endpoint (form-encoded or JSON). |
| DELETE | `/v1/agent/identity` | The agent ends what `lhbox new` started, before the expiry: the unclaimed organisation, its catalog with every table and file, its tokens and keys, deleted n... |
| POST | `/v1/agent/identity` | An agent with no account and no person (a deployment setting turns it on): an UNCLAIMED organisation, its catalog `lakehouse` and a key with write on it, ans... |
| POST | `/v1/agent/identity/claim` | A person keeps what an agent made without an account: a device code bound to the unclaimed organisation. |
| GET | `/v1/agent/status` | Whether the caller's organisation is still unclaimed (made by an agent without an account) and the time it has left before it is deleted with its data. |
| GET | `/v1/auth/accounts` | The accounts this browser holds a live session cookie for (the account page's account picker; its scripts cannot read the HttpOnly cookies). |
| POST | `/v1/auth/cli/authorize` | `lhbox login` in the browser (RFC 8252: a loopback redirect with PKCE). |
| POST | `/v1/auth/cli/token` | The CLI trades the code its listener received, with the PKCE verifier only it holds, for the person's own key. |
| POST | `/v1/auth/device` | RFC 8628 device authorisation for the CLI, asking for a CONNECTION (docs/agent-setup.md): a device code to poll with and an 8‑character user code for the hum... |
| POST | `/v1/auth/device/approve` | A person signed in on the account page decides a code login: yes or no. |
| GET | `/v1/auth/device/pending` | The consent screen's content for a pending code (people only; nothing is decided by reading it) |
| GET | `/v1/auth/device/status` | Where a CLI login stands, for the page that approved it. |
| POST | `/v1/auth/device/token` | The agent polls POST /v1/auth/device/token with device_code and receives a NEW key at the level the person chose. |
| POST | `/v1/auth/login/passkey/start` | The options for navigator.credentials.get(): with no body, for a sign-in with a passkey alone (the browser offers the passkeys it holds for the site); with t... |
| POST | `/v1/auth/logout` | Revokes the session, by its refresh token, by the account page's cookie (and clears it), or by the access token in Authorization (sid claim). |
| GET | `/v1/auth/mfa` | The caller's two-factor state. |
| POST | `/v1/auth/mfa/backup-codes` | New backup codes for old: needs a current code (or a backup code); the earlier codes stop working. |
| POST | `/v1/auth/mfa/enrol/confirm` | The current code of the pending secret turns two-factor on and finishes the login: the session POST /v1/auth/login answers (marked two-factor), with the back... |
| POST | `/v1/auth/mfa/totp/confirm` | The current code of the pending secret turns two-factor on. |
| POST | `/v1/auth/mfa/totp/disable` | Two-factor off: needs the password and a current code (or a backup code); the secret and the backup codes are deleted. |
| POST | `/v1/auth/mfa/totp/start` | Begin two-factor enrolment (a person's browser session, with the current password): a new secret, pending until a code confirms it. |
| GET | `/v1/auth/passkeys` | The caller's passkeys (a person's browser session). |
| POST | `/v1/auth/passkeys/confirm/start` | The options for navigator.credentials.get() naming the caller's passkeys, to confirm one act with a passkey instead of the authenticator's code. |
| POST | `/v1/auth/passkeys/register/finish` | The new passkey checked and stored; a notice is mailed to the account's address. |
| POST | `/v1/auth/passkeys/register/start` | The options for navigator.credentials.create(), bound to this session for 5 minutes. Needs the current password; when two-factor is on, a code must come too. |
| DELETE | `/v1/auth/passkeys/{passkeyId}` | Remove one of the caller's passkeys: it no longer signs in, every session it opened is revoked (not the one making the call), and a notice is mailed. |
| POST | `/v1/auth/password/change` | A logged-in human changes their password; every OTHER session is revoked; optionally revokes API keys and MCP connections. |
| POST | `/v1/auth/password/reset` | The reset link: a new password, every session revoked, every passkey removed, every API key of the person revoked, every MCP connection the person approved d... |
| POST | `/v1/auth/password/reset/start` | A 30‑minute reset link to /app/reset?token=… by mail. |
| POST | `/v1/auth/reauth` | A person's browser session confirms it is still the person: the current password, and a code when two-factor is on (a backup code is spent). |
| POST | `/v1/auth/refresh` | A new access token and a rotated refresh token; the session's expiry slides 30 days. |
| GET | `/v1/auth/sessions` | The caller's live sessions: where and when they logged in; `current` marks the one making the call. |
| DELETE | `/v1/auth/sessions/{sessionId}` | Revokes one of the caller's sessions. |
| POST | `/v1/auth/signup` | The signup form: a pending account and a pending organisation (handle reserved), and a set-password mail with a link to /app/welcome?token=… valid 3 days. |
| GET | `/v1/connection` | The Iceberg catalog at https://catalog.lakehousebox.com and the object store at https://s3.lakehousebox.com are separate surfaces with their own credential, ... |
| GET | `/v1/handles/{handle}` | Is this organisation handle free? For the signup form as you type (per-address rate limit). |
| DELETE | `/v1/me` | Delete the caller's account. |
| POST | `/v1/oauth/authorize/decision` | The signed-in human allows or denies. |
| GET | `/v1/oauth/authorize/pending` | The consent page's content for a pending authorization. |
| GET | `/v1/oauth/authorize/set-up` | What the consent page shows a person who is not signed in. |
| POST | `/v1/oauth/authorize/set-up` | "Let <client> set it up": for a person with no account. |
| GET | `/v1/orgs/{orgId}/policy` | Get the organisation's policy (used for warehouse creation defaults). |
| GET | `/v1/projects` | Projects you own or reach through an organisation you belong to. |
| DELETE | `/v1/projects/{projectId}` | Delete an empty project. |
| GET | `/v1/projects/{projectId}` | One project you reach, as the list shows it. |
| PATCH | `/v1/projects/{projectId}` | Rename a project. |
| POST | `/v1/recover/start` | Retired on 2026-10-01: a code by email no longer mints a key with a person's full access (nor does signup since then). |
| POST | `/v1/recover/verify` | Retired on 2026-10-01 with /v1/recover/start: always 410, no key minted. |
| GET | `/v1/setup` | A self-hosted install's first-run setup: whether it is open and how the first administrator will sign in. |
| POST | `/v1/setup` | The install administrator and the first organisation of a self-hosted install, once, with the setup token. |
| POST | `/v1/signup` | The one-call, UNVERIFIED signup for local development stacks. |
| POST | `/v1/signup/start` | POST /v1/signup/start → 202 |

…and 15 more operations. They are listed in full on the page.

## Machine-readable artifacts (7)

- **OpenAPI** — https://artifacts.apis.io/lakehousebox-com/openapi/_ae-authored/lakehousebox-com-openapi-generated.yml
- **JSONSchema** — https://artifacts.apis.io/lakehousebox-com/json-schema/lakehousebox-com-get-well-known-oauth-authorization-server-response-schema.json
- **JSONSchema** — https://artifacts.apis.io/lakehousebox-com/json-schema/lakehousebox-com-get-v1-oauth-authorize-pending-response-schema.json
- **JSONSchema** — https://artifacts.apis.io/lakehousebox-com/json-schema/lakehousebox-com-post-v1-warehouses-response-schema.json
- **JSONSchema** — https://artifacts.apis.io/lakehousebox-com/json-schema/lakehousebox-com-post-v1-agent-identity-response-schema.json
- **JSONSchema** — https://artifacts.apis.io/lakehousebox-com/json-schema/lakehousebox-com-post-oauth-register-response-schema.json
- **JSONSchema** — https://artifacts.apis.io/lakehousebox-com/json-schema/lakehousebox-com-post-v1-signup-response-schema.json

## Other LakehouseBox APIs (1)

- [LakehouseBox API](https://apis.io/apis/lakehousebox-com/lakehousebox-api/)

## Use this from code or an agent

- **REST, no key:** `GET https://apis.io/api/v1/providers/lakehousebox-com` returns the provider's full profile as JSON.
- **MCP:** `https://apis.io/mcp` (Streamable HTTP) — search the catalog, read any provider, compare providers, check agent readiness.
- **Free API key** for catalog-wide search, ratings and comparisons: sign in with GitHub, Google or LinkedIn at https://apis.io/developer/account/ (plans: https://apis.io/developer/plans/).

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/lakehousebox-com/lakehousebox-com-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/lakehousebox-com/.
