All routes
Every route of the Qaldy API in one list, 252 in all, grouped by what they are for.
| Group | Routes | What it covers |
|---|---|---|
| agent tools | 7 | |
| AI models | 8 | The workspace’s own model provider keys, the default model, each app’s monthly budget and the usage report. |
| Analytics | 2 | Runs, failures, time saved, connector health and backend traffic for the apps you can open. |
| Approvals | 1 | Decide an approval an app is waiting on. |
| Apps | 4 | Read an app, run it, pause it, move it on the island. |
| Audit and egress | 21 | The audit log and its hash-chain check, and what each app is allowed to reach. |
| Automations | 14 | Roads between apps: schedules, webhooks, forms and heartbeats, pausing them and running them now. |
| Backend (console) | 19 | Backend projects, tables, columns, rows, keys and logs, as the console and personal tokens use them. |
| Backend data API | 10 | The REST API your own apps and sites call with a project key (qk_pub_… or qk_sec_…), not a session. |
| billing | 14 | |
| Build | 3 | Describe an app, read the plan and its permissions, approve it, and the templates to start from. |
| builder | 2 | |
| Capacity and plan changes | 6 | The resource pool, previewing and applying a change, the monthly budget and autoscale settings. |
| capguard | 3 | |
| Connectors | 6 | The catalog, the workspace’s connections, HTTP API connectors, testing and disconnecting. Keys go in once and are never returned. |
| Device login (command line) | 5 | The routes behind qaldy login: a terminal asks for a code, a person approves it in the console. |
| domains | 6 | |
| guests | 6 | |
| Hours saved | 2 | How the hours-saved figure is calculated, and the overrides an admin can set. |
| imports | 6 | |
| Logs, alerts and digest | 12 | An app’s logs and metrics, alert rules and their history, the weekly digest and the public status page. |
| marketplace | 15 | |
| People and roles | 11 | Members, roles, access end dates, invites, joining by company domain and handing a workspace over. |
| Personal access tokens | 5 | Who a token acts as, and retiring the token you are using. A token can never make another token. |
| Plan and spending cap | 2 | The workspace’s plan, its allowances and the hard spending cap. Billing is mock in the pilot. |
| probe | 2 | |
| Regions and scaling | 4 | Where apps run, what is live and what is planned, and each app’s scaling policy (Preview). |
| Runs | 14 | The run list, one run, the plain-words explanation of a failure and the gate’s trace of what a run was allowed to do. |
| Session and sign-out | 2 | Who you are signed in as, the sign-in methods this server offers, and signing out. |
| Sharing | 3 | Who can open an app, and how: people, teams, the workspace and (where policy allows) a link. |
| Sign-in for MCP clients | 4 | The console’s side of OAuth for remote MCP clients: the consent request and the apps you have connected. The public OAuth endpoints are described under MCP. |
| Sites | 6 | Static sites and single-page apps at their own address: versions, going live, rolling back, and the files in a version. |
| telegram | 9 | |
| Versions and edits | 6 | An app’s version history, comparing two versions as permission facts, rolling back, and changing an app by a sentence. |
| Workspace settings | 2 | The workspace’s settings and the connector secrets form. |
| Workspace snapshot | 2 | Everything the City draws for a workspace: apps, automations, gates, runs and people, and the version of that snapshot. |
| Workspaces and invites | 8 | Create a workspace, switch between yours, and accept an invite. |
The same document, as OpenAPI 3: openapi.json.