# Changelog

Customer-visible changes to SEON's APIs, SDKs and webhooks, most recent first.
Entries are drafted from each service release and reviewed before publishing.

## 2026-08-27 — Workflow API

- **Re-send a run's data on demand.** A new `orchestration/workflow_execution_sync`
  webhook event is sent when someone re-sends a finished workflow run from the
  Workflow Runs page in the Admin Panel. Subscribe to it to recover missed
  deliveries. See [Workflow webhooks](api-reference/workflow-api.md#workflow-webhooks).
- **Return users to your application from hosted flows.** Workflow links accept
  optional `completedUrl` and `incompleteUrl` redirect targets. See
  [Redirecting users back to your application](api-reference/workflow-api.md#redirecting-users-back-to-your-application).

## 2026-08-13 — Workflow API

- **Read workflow results on demand.** `GET /v1/workflow-execution/{id}` returns
  the current state of an execution and, once finished, the result of every
  check it ran. Add `mediaOnly=true` to fetch only captured images and video.
  See [Retrieving workflow execution results](api-reference/workflow-api.md#retrieving-workflow-execution-results).
- **Record your own decision.** `PATCH /v1/workflow-execution/{id}` stores your
  final `APPROVED` or `DECLINED` decision on a finished execution and notifies
  your webhook endpoint. See [Recording a decision](api-reference/workflow-api.md#recording-a-decision).
- **Richer workflow webhooks.** The `data` object of
  `workflow_execution_finished` and `workflow_execution_updated` now includes
  `createdAt`, `dataPurgedAt` and a `checks` array with the outcome, extracted
  data and captured media of each check, and is identical to the object
  returned by the results endpoint. Existing fields are unchanged.
- **Level of Identity Proofing details.** `loip.unmetConditions` is now included
  only when the result is `NONE`, listing what prevented a higher level.