The trexi API is the same interface the dashboard, CLI, and MCP server use — anything you can do in the app, you can script. Every endpoint below is generated from the live API contract, so this reference never drifts from the real behavior.

​
Base URL

​
Authentication

Every request is authenticated with a personal API key sent as a Bearer token:
A key acts as you, in the organization it belongs to, with your role — so the same permissions you have in the app apply to the API.

​
Getting a key

  1. In the web app, open Settings → API keys.
  2. Create a key and give it a name. The full key (trexi_sk_…) is shown once — copy it then; only a hash is stored, so it can’t be retrieved later.
  3. Use it as the Bearer token above, or run trexi auth login <key> for the CLI.
Each member manages their own keys and can revoke any of them anytime from the same page. For security, keys can only be created from the web app — you can’t mint a new key using an existing key.
Keys are per-person, not per-organization: they carry the role of the member who created them. See Your team for what each role can do.