Extractors Migration
What You Get
- Dedicated
/extractorsendpoints — No moretype: "EXTRACT"filters, cleaner API surface - New
GET /extractors/{id}endpoint — Retrieve a single extractor with its draft version (not available in old API) - Typed SDK responses —
extractorobjects are typed, no casting needed - Simpler config — No more
typefield required in config
The old /processors endpoint is still supported in this API version for backward compatibility. You can migrate incrementally.
Quick Start: Common Patterns
Creating an Extractor
TypeScript
Python
Java
Retrieving an Extractor (New!)
TypeScript
Python
Java
Listing Extractors
TypeScript
Python
Java
Publishing a Version
TypeScript
Python
Java
Endpoint Changes Summary
Request Changes
Creating an Extractor
cloneExtractorId and config are mutually exclusive. You can either clone an existing extractor or provide a config, but not both. The API will return a validation error if both are provided.
Example: Create Request
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.
Key Differences
Example: Response
Versions Endpoint Changes
List Versions
The list endpoint now returns summaries without config. Use the get version endpoint for full details.
SDK Method Reference
Detailed Schema Changes
Extractor Schema
ExtractorSummary Schema (List Response)
ExtractorVersion Schema
ExtractConfig Schema
Need Help?
If you encounter any issues while migrating, please contact our support team at support@extend.app.

