Retrieve a decision

Use Actera’s retrieve operation to explain an AI agent authorization outcome, observe human approval state, or reconcile what the trusted integration reported after authorization.

GET/v1/decisions/{decision_id}

Parameters

Parameter	Location	Required	Description
Actera-Workspace-Id	Header	Yes	Workspace UUID selected by the authenticated principal.
decision_id	Path	Yes	Stable identifier returned by evaluation.

Request

curl "$ACTERA_BASE_URL/v1/decisions/$DECISION_ID" \
  --header "Authorization: Bearer $ACTERA_ACCESS_TOKEN" \
  --header "Actera-Workspace-Id: $ACTERA_WORKSPACE_ID"

Response excerpt

{
  "id": "dec_7f26",
  "agent_id": "refund-agent",
  "action_type": "refund.create",
  "effect": "REQUIRE_APPROVAL",
  "status": "APPROVED",
  "policy_bundle_version": "12",
  "matched_policy_ids": ["pol_refund_repeat"],
  "matched_rules": ["repeat-refund-review"],
  "explanation": "Repeat refunds require review",
  "events": [
    { "event_type": "DECISION_RECEIVED", "to_state": "RECEIVED" },
    { "event_type": "DECISION_APPROVED", "from_state": "PENDING_APPROVAL", "to_state": "APPROVED", "actor_id": "reviewer-42" }
  ],
  "subsequent_activities": []
}

The actual response also includes evaluation context, applicable policies, rule evaluations, approval requirements, reservations, activity, and managed execution evidence when present.

Read events in order. APPROVED proves authorization, not completed external execution. An unknown identifier returns 404; a decision in another workspace is not disclosed. This read is safe to retry. See Inspect a decision for an evidence checklist, Decisions and approvals for lifecycle semantics, and API conventions for errors.