Dokki API
Build with Dokki's documents, tables, artifacts, search, agents, and organization controls.
The Dokki API is the programmatic interface to the same resources and permissions used by the Dokki app. It is designed for human developers, backend services, and AI agents that need predictable, tenant-aware access to collaborative knowledge.
Start here
Base URL
https://dokki.one
Public API routes live under /api/v1. For example:
GET https://dokki.one/api/v1/me
Why use the Dokki API?
Read and update shared documents without bypassing Dokki permissions.
Search workspaces with keyword, semantic, or hybrid retrieval.
Run agents and automations in a controlled Org or workspace scope.
Publish selected resources as public documentation sites.
Discover the current API surface from
GET /api/v1/capabilities.
For AI agents
Use GET /api/v1/capabilities before choosing a tool. Treat the response as the live contract: it reports available scopes and endpoint paths. Always preserve request_id values from errors when asking for support.
Common questions
What is the safest first request?
Call GET /api/v1/me to verify the token, tenant, and effective scopes.
How do I update a document safely?
Read the resource and current content first, then send a targeted content update. Keep the returned request and snapshot identifiers in your job log.
How is access decided?
Authorization is the intersection of token scope, Org/workspace tenant boundary, and resource permission. See Permissions and Organization Access.