API

Two APIs

Two different things are called an API here, and they are not the same surface.

The local API belongs to the desktop companion, tcc. The daemon runs on your own machine and serves an HTTP interface on the loopback address. Anything you can do in the companion — verify three words, stamp a file, list connections, manage an organisation — has a route. It has a committed OpenAPI document, which is what these pages are written from, and the daemon serves that same document to callers.

The platform API is the server side: the hosted service the apps talk to. It is not published.

What This Section Covers

These pages cover the local API only. They describe where the daemon listens, how a caller authenticates, what the responses look like, and every one of the 79 documented paths.

They do not teach the companion itself. Installing it, signing it in and running it as a daemon are covered in the companion and CLI pages.

Why the Platform API Is Absent

The platform API has no published document, no published version and no published stability promise. Writing pages for it would mean describing a surface we have not committed to keeping. When it is published, it will get its own pages here.

Until then, an integration that needs Trusted Codes talks to a local companion, which holds the account’s own session and keys and speaks to the platform on your behalf.