Decisions

Where you answer kanman's questions, and how your tools list, read and answer them through the REST API.

Decisions are the questions kanman asks a person: what you intend, a choice only you can make, or access it does not have. Each one comes with the options kanman sees, and you can also answer in your own words. See Questions from kanman for the concept. You answer them in the app, in Slack or through the REST API.

Answer a decision

Where How
App Decisions (/<workspace>/decisions), tabs Pending, Stories and Resolved, or the decision page /<workspace>/decisions/<decision-key>. Choose an option or answer in your own words.
Slack The buttons under the decision message in the team’s channel, or a reply to kanman in the thread. See Answer decisions from Slack.
Intake A reply in the team’s intake that names the decision, for example “dec-4h2k: use the sandbox account”.
REST API POST /v1/decisions/<decision-key>/resolve with a token that has the write permission. See below.

The first answer wins. Whoever answers second is told that the decision is already resolved. Every answer writes a decision_resolved audit entry with the person and the channel, shown on the decision as “resolved via” the app, Slack, the MCP server or the API.

REST API

List decisions

GET /v1/decisions returns the workspace’s decisions, newest first, paginated. Filter with status (pending, resolved, expired, cancelled, superseded), team (team slug) and run (run key).

curl "https://api.kanman.ai/functions/v1/api-gateway/v1/decisions?status=pending" --header "Authorization: Bearer $KANMAN_API_KEY"
Field Description
key, title, body The decision; body holds kanman’s reasoning as Markdown.
status, recommendation The state and the id of the option kanman recommends.
options id, label, action and recommended per option.
team, story, runKey Where the decision belongs.
resolution, resolvedVia, resolvedAt The answer (optionId, note) and its channel, once resolved.
expiresAt, createdAt Timestamps.

GET /v1/decisions/{decision-key} returns one decision in the same shape.

Answer a decision through the API

POST /v1/decisions/{decision-key}/resolve needs a token with the write permission. The answer is recorded with the token’s owner as the person who answered and api as the channel, and has the same effect as answering in the app.

curl -X POST https://api.kanman.ai/functions/v1/api-gateway/v1/decisions/dec-4h2k/resolve \
  --header "Authorization: Bearer $KANMAN_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"optionId": "opt-1", "note": "Use the sandbox account"}'
Body field Description
optionId Required. The id of one of the decision’s options.
note Optional, up to 50,000 characters (a longer note is refused, not shortened). Passed on like a note in the app.

The answer is the updated decision plus effects, the steps kanman took. 400 means the option does not exist, 404 that the decision is not in the token’s workspace, 409 that it was already answered (the first answer wins).

Last updated: January 1, 0001

Open kanman