Decide a case (the one inbound decision path)

Every channel resolves here, through DecisionActionResolver. Teams and Slack callbacks, the Business Central extension and the decionis.cases.* MCP tools all reach the same steps. The channel identity must belong to the workspace's tenant, resolve to a current Accounts member and hold the case's authority. When the authority requirement asks, Presence must have approved the person's passkey first (428 with step_up_url). The transition happens at the case's owner, with a revision check, and is applied once per case revision whichever inbox it came from. Organization API key with decision:write and a person (Business Central x-decionis-actor or an MCP OAuth token), or the named recipient's own Account session with the signed email link.

post/v1/cases/{caseId}/decisions

Request

  • Base URL: https://api.decionis.com
  • URL: https://api.decionis.com/v1/cases/{caseId}/decisions
  • Auth: HTTP bearer

Query parameters

view'card' | 'business-central' | 'assistant'

Request body

verb'approve' | 'reject' | 'edit' | 'escalate' required
revisioninteger required
decision_idstring uuid
choicesstring[]
notestring
linkstring

Signed email fallback link

Response

applied is false when the same decision was already applied (from this or another inbox).

appliedboolean required
cardobject required

Changes

No recorded changes to this operation across all 1 revision of this API.