> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devias.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The docs are served at https://docs.devias.io. Every path in these docs is relative to that root: /llms.txt is https://docs.devias.io/llms.txt.
> Devias is an open-source platform that works as an operating system for a business: a core (records, views, workflows, agents, permissions) with installable modules.
> Pages are typed by folder. concepts/ explains what things are, guides/ gives procedures, reference/ is exhaustive (SDK, CLI, HTTP API), operate/ covers hosting. Use /start/glossary for exact terms.
> Every id in a module (module, object, field, view, action, workflow, step, connection, variable, event, policy) is a uuid. Generate them with `devias id <count>`. Never invent dotted or readable ids.
> Run `devias plan` and read its output before `devias apply`. Apply only what the plan says.
> The OpenAPI document, including the routes of the modules in the reference setup, is at /reference/api/openapi.json.
> Devias is young and changes quickly. If a page and the source repository (github.com/devias-io/devias) disagree, the repository is right.

# HTTP API

> How the Devias HTTP API behaves. JSON requests and responses, routes under /api/workspaces/<workspaceId>/, one permission check for every caller, every write announced as an event, and the OpenAPI document at /reference/api/openapi.json that describes all routes including module routes.

Everything the studio does goes through the Devias HTTP API, and anything the studio can do can be done through it. The [TypeScript SDK](https://docs.devias.io/reference/sdk/client.md) wraps it. This section describes the API for any other language and for what the SDK does underneath.

## Properties of the API

* **JSON in, JSON out.** Requests and responses are JSON.
* **Workspace scoped.** Almost every route lives under `/api/workspaces/<workspaceId>/`, so one server holds many workspaces.
* **One permission check.** An API call, the studio, a workflow and an agent all pass the same check. See [Access and permissions](https://docs.devias.io/concepts/access.md).
* **Changes are announced.** Every write is also an event that can be followed. See [Change feed](https://docs.devias.io/reference/api/change-feed.md).

## The OpenAPI document

Every route, with its request and response schemas, is described in one OpenAPI 3.1 document: [`/reference/api/openapi.json`](https://docs.devias.io/reference/api/openapi.json) on this site. It includes the routes added by the modules of the reference setup. The core API alone is `apps/server/openapi.json` in the repository, and the SDK's types are generated from that file, so the two never disagree.

There are no per-route pages in this documentation. The OpenAPI document is the complete and exact list of routes.

## Related

* [Authentication](https://docs.devias.io/reference/api/authentication.md): a session or an API key.
* [Errors](https://docs.devias.io/reference/api/errors.md): what a failed call returns.
* [Querying records](https://docs.devias.io/reference/api/querying.md): the query format.
* [Change feed](https://docs.devias.io/reference/api/change-feed.md): follow changes as they happen.
* [Module routes](https://docs.devias.io/reference/api/module-routes.md): actions, webhooks and a module's own routes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.