API
Everything the web app does goes through a JSON REST API under /v1.
Authentication
Create an API key in your organisation settings and send it as a bearer token. Keys start with dd_live_. Treat them like passwords and store them in a secrets manager.
curl $DESIGNDOC_API_URL/v1/rfcs \
-H "Authorization: Bearer $DESIGNDOC_API_KEY"Resources
| Path | What it covers |
|---|---|
/v1/orgs | Organisations, members, templates, API keys, AI settings |
/v1/projects | Projects |
/v1/rfcs | Decisions, with comments, reviews, links and relations nested under each |
/v1/reviews/pending | Reviews waiting on you |
/v1/notifications | In-app notifications |
/v1/search | Search decisions |
/v1/ai | Summaries, rewrites and cross-reference review |
Errors
| Status | Meaning |
|---|---|
| 400 | The request is invalid. |
| 403 | You are not allowed to do this in the organisation. |
| 404 | Not found. |
| 409 | Conflicts with the current state. |
| 422 | The status change is not allowed from the current status. |
An OpenAPI reference is not published yet. Until then the MCP server and CLI are the supported clients.