Skip to main content

Workflow Callback API

Summary​

Terminal Workflow decision callback and validation/idempotency behavior.

Audience​

API consumers, engineers, architects, QA, support, security reviewers, implementation partners, and product owners.

Overview​

The Workflow callback is always mapped, although operationally relevant only when Workflow delegation is enabled.

Endpoint family​

FamilyRouteMethodsContract or purpose
Terminal decision/performance/workflow/callbackPOSTWorkflowCallbackDto; AppraisalDto
  • The DTO can correlate by appraisal, subject, or Workflow identity and carries a terminal decision with optional reviewer context; sensitive values are omitted.
  • Validation rejects a missing body, unsupported decision, unexpected subject type, or unresolved appraisal.
  • An already-decided appraisal is acknowledged without reapplying events.
  • Optional remote-state verification returns Conflict only for a definitive mismatch; unavailable state is best-effort.
  • No endpoint authorization or callback-specific authentication metadata is present; idempotency is state-based, not ledger-based.

Classification​

Transitional Workflow boundary.

Authentication and authorization​

Bearer authentication and tenant context are registered. No Performance endpoint in this family declares an authorization requirement unless explicitly stated above.

Requires confirmation​

Callback authentication, replay window, delivery retries, verification strictness, and recovery ownership require confirmation.

Diagram​

See Also​

Keywords​

  • Performance API
  • Workflow Callbacks
  • Draft API documentation

Source References​

  • microservices/src/performance-service/Api/PerformanceEndpoints.cs
  • microservices/src/performance-service/Application/WorkflowIntegration.cs
  • microservices/src/performance-service/Application/Commands/AppraisalCommands.cs

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-16
  • Review cycle: Quarterly