Everything the console does, it does over the same API you can call yourself, from your tenant’s own host: https://<slug>.app.<domain>.

The services

Two more services expose only a short, fixed set of individual methods rather than the whole service: IdentityService (altimate.identity.v1) for inviting/removing members, service users and API keys, and minting a data-plane engine token; and FeatureFlagService (altimate.tenancy.v1), for listing your tenant’s entitlements.

Authenticating

A request also needs a scope matching what it’s trying to do; see OAuth scopes for what each one covers.

What a dip login token can call

Reads: ListQueryEngines, ListDataPlanes, ListIntegrations, ListSemanticModels, CompileMetricQuery, ListOntologies, ListConcepts, and the workspace-database reads (ListWorkspaceDatabases, GetWorkspaceDatabase, ListWorkspaceDatabaseTokens). ListDataPlanes needs no particular scope: any signed-in credential, a key or a login token, may list your workspace’s data planes. Writes: registering, updating, testing and deleting an integration (RegisterIntegration/UpdateIntegration/TestConnection/DeleteIntegration); creating, reconfiguring and deleting a query engine, and triggering or checking a metadata crawl (CreateQueryEngine/UpdateQueryEngineConfig/UpdateQueryEngineCatalogs/DeleteQueryEngine/ TriggerMetadataCrawl/GetDiscoveryStatus); and the full workspace-database write surface (CreateWorkspaceDatabase, UpdateWorkspaceDatabase, DeleteWorkspaceDatabase, inviting or removing a member, minting or revoking a token). A handful of app developer-iteration methods (EnsureDevInstallation, MintDevEngineToken, DeleteDevInstallation) are also reachable this way. Every call is still checked against your own roles and grants — the list above only says which methods a dip login token may call at all, never what it’s allowed to do once it does.

The protocol

Every RPC is a Connect request: POST to /<package>.<Service>/<Method> with a JSON body and Connect-Protocol-Version: 1.
List this tenant's query engines
Pass {"name": "engine-name"} instead of {} to look up one engine by its exact name.

Rate limits

The API itself carries no general per-request limit. Sign-in and OAuth endpoints (login, token exchange, dynamic client registration) are rate-limited per IP and per account to blunt credential-stuffing and runaway clients; if you’re scripting sign-in, back off on a 429.

What you can’t reach

Ingestion endpoints that feed query history, engine metrics, audit events and the metadata index into their stores are not reachable by any external caller, however authenticated — only Dippr’s own services write to them. Data-plane traffic that never touches this API at all — a query engine’s own protocol endpoint, an MCP tool call, a data app’s own runtime traffic, workspace database writes over DuckDB’s wire protocol — is described in Addresses and hostnames.

OAuth scopes

What each scope covers, and who can hold it.

Addresses and hostnames

Every hostname Dippr puts in front of you, and what each one serves.