classifyRun.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 classifier settings, you must now pass it as classifier.overrideConfig inside the classifier object. The top-level config property is reserved for inline classification (without a classifier).
Additionally, config.parser has been renamed to parseConfig everywhere — use config.parseConfig for inline config or classifier.overrideConfig.parseConfig when overriding a classifier.
If you previously passed config alongside processorId to override the classifier’s settings, this now moves inside the classifier 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.