/edit/async merged into /edit_runs, plus a new sync /edit endpoint for testingcreateAndPoll() helper — Easy polling with client.editRuns.createAndPoll()outputfile object instead of just fileIdPOST /edit/async has been replaced by POST /edit_runs and is no longer available. The sync POST /edit endpoint has been updated with a new request/response format.
This guide covers all breaking changes to the edit endpoints.
The SDK group and method names have been updated for consistency:
The EditRun schema has been restructured with file references changed from string IDs to objects, and output structure reorganized. Status-dependent fields are now required but nullable for a predictable response structure.
The config object now uses a named EditConfig schema with updated advanced options.
The file input format has been updated to use a oneOf schema with renamed properties.
The 2026-02-09 API provides two ways to run edits:
POST /edit) — Returns the completed result directly. Intended for testing and onboarding only.POST /edit_runs) — Returns immediately, poll GET /edit_runs/{id} or use webhooks. Recommended for production. See Async Processing for details on polling helpers.The response no longer uses a polymorphic oneOf between EditRunStatus and EditRun. It now always returns the full EditRun object.
The output structure has been reorganized to separate the edited file from the filled values.
The new API documents additional failure reasons that may be returned:
If you encounter any issues while migrating, please contact our support team at support@extend.app.