Classifiers Migration
What You Get
- Dedicated
/classifiersendpoints — No moretype: "CLASSIFY"filters - New
GET /classifiers/{id}endpoint — Retrieve a single classifier (not available in old API) - Typed SDK responses —
classifierobjects are typed, no casting needed - Simpler config — No more
typefield required
The old /processors endpoint is still supported in this API version for backward compatibility. You can migrate incrementally.
Quick Start: Common Patterns
Creating a Classifier
TypeScript
Python
Java
Before (2025-04-21)
After (2026-02-09)
Retrieving a Classifier (New!)
TypeScript
Python
Java
Listing Classifiers
TypeScript
Python
Java
Before
After
Publishing a Version
TypeScript
Python
Java
Before
After
Endpoint Changes Summary
Request Changes
cloneClassifierId and config are mutually exclusive. You can either clone an existing classifier or provide a config, but not both. The API will return a validation error if both are provided.
Response Changes
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.
SDK Method Reference
Need Help?
If you encounter any issues while migrating, please contact our support team at support@extend.app.

