splitRun.output is typed, no more castingconfigThe old /processor_runs endpoint is still supported in this API version for backward compatibility. You can migrate incrementally.
Breaking change: If you previously passed config alongside a processorId to override splitter settings, you must now pass it as splitter.overrideConfig inside the splitter object. The top-level config property is reserved for inline splitting (without a splitter).
Additionally, config.parser has been renamed to parseConfig everywhere — use config.parseConfig for inline config or splitter.overrideConfig.parseConfig when overriding a splitter.
If you previously passed config alongside processorId to override the splitter’s settings, this now moves inside the splitter object as overrideConfig:
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.
If you encounter any issues while migrating, please contact our support team at support@extend.app.