WorkflowRun back instead of an arraystepRuns now includes all step types (extraction, classification, splitting, etc.) with typed results, replacing the old outputs arraycreateAndPoll / create_and_poll handles polling with exponential backoffThe old /workflow_runs request and response shapes from 2025-04-21 are not carried forward—you’ll need to update your integration to use the new format.
The SDK provides createAndPoll / create_and_poll methods that handle polling automatically, returning when the run reaches a terminal state (PROCESSED, FAILED, CANCELLED, NEEDS_REVIEW, or REJECTED):
The old API accepted an array of files in a single request. The new API processes one file at a time. To process multiple files, make separate requests or use the batch endpoint:
Breaking change: The files array has been replaced with a single file object. If you previously processed multiple files in one request, you’ll need to either make separate requests or use the Batch Run Workflow endpoint.
Response shape changes: Single object responses are now returned directly (no wrapper key), and list responses use { "object": "list", "data": [...] } format. See Simplified Response Shapes for details.
The biggest change is how processor results are returned. Previously, results lived in the outputs array as ProcessorRun objects. Now, results are in stepRuns as typed StepRun objects:
The POST /workflow_runs/{workflowRunId}/outputs/{outputId} endpoint for submitting corrected outputs has been removed. This was deprecated in the 2025-04-21 API.
If you encounter any issues while migrating, please contact our support team at support@extend.app.