Skip to main content
Dexi’s public REST surface is deliberately small — two endpoint families: Everything else under api.dexi.net belongs to the Dexi app’s own session-authenticated API; personal API tokens deliberately don’t work there. If you want programmatic read access to a workspace — search, browse, full note text — that’s the MCP server, not REST. For bulk data, the app’s export (Settings → Export) produces ZIP/CSV/markdown.

​
Conventions

  • Requests and responses are JSON (Content-Type: application/json); the RSS route returns application/rss+xml.
  • Timestamps are ISO 8601 with timezone offsets. IDs are UUIDs.
  • Authentication uses a bearer header: Authorization: Bearer dxi_….
  • Validation failures return 422 with FastAPI’s standard detail array. Missing/invalid credentials return 401. Resources you can’t see return 404 — never 403.