Table Recognition → Document Conversion
The standalone Table Recognition endpoint (/api/v1/table_rec) is deprecated. Use the Document Conversion endpoint with JSON output instead.
Before (deprecated)
After (current)
Why migrate?
- Single endpoint — no need for separate table-specific calls
- Better accuracy — tables are extracted in context with the full document
- More features — access processing modes, structured extraction, and more
- Active development — the marker endpoint receives all new improvements
OCR → Document Conversion
The standalone OCR endpoint (/api/v1/ocr) is deprecated. Use the Document Conversion endpoint instead, which includes OCR as part of its processing pipeline.
Before (deprecated)
After (current)
Why migrate?
- Better results — the conversion pipeline includes OCR plus layout analysis, table recognition, and image handling
- More output formats — get markdown, HTML, JSON, or chunks instead of raw text
- Quality scoring —
parse_quality_scoretells you how well the document was processed