Files and versioning

Supported file types

Start with PDFs for invoice workflows. Use other formats when the source system already produces them. exdata checks file content signatures and scanner status before the requested extraction or thumbnail work is queued.

• PDFInvoices, credit notes, account statements, letters, contracts, and exported reports.
• PNGScanned document pages and image-only uploads.
• JPGPhotographed documents and image captures from mobile workflows.
• HTMLSaved web documents, rendered invoice templates, and HTML exports.
• TXTPlain-text documents and extracted text from upstream systems.
• CSVTabular exports where the document data is already structured in rows.
• JSONStructured source payloads that should be normalized into the same extraction response shape.
• DOCXOffice documents such as contracts, letters, statements, and reports.
• EMLEmail files with sender, recipient, subject, headers, and body content.
• MSGOutlook message files for email-based document workflows.
• MP4MPEG-4 video uploads and common camera exports.
• M4VMPEG-4 video files commonly exported by Apple software.
• MOVQuickTime video files from cameras and editing workflows.
• WebMWeb-native video files and browser recordings.
• OGVOgg video files from open media workflows.
• OGGOgg container video files.
• XMLSupported CII, Factur-X/ZUGFeRD 2, XRechnung, and UBL e-invoices, plus generic XML exports. XML files are limited to 5 MiB before parsing. Recognized legacy, oversized, or invalid e-invoice profiles fail closed instead of returning empty invoice data.
• EDIElectronic data interchange payloads used in operations and procurement workflows.
• IDocSAP IDoc exports and integration payloads.

For video uploads, exdata extracts a representative frame. The document thumbnail endpoint returns that frame as a JPEG. With processing_mode=thumbnail, that frame is the only generated result: no OCR, AI, structured extraction, or persisted preview is created. The container must include a decodable video stream, and decoded frames must not exceed 33,177,600 pixels (8K UHD); audio-only files fail during processing, and oversized video files fail during processing.

API versioning

Use /api/v1 for document API integrations. Breaking API changes will be introduced under a new versioned base path.

OpenAPI contract

The OpenAPI YAML is available publicly for client generation and schema review. Client collections and receiver examples are listed under Tools and downloads.

https://www.exdata.app/docs/api/openapi.yaml

Data handling links

Review these documents before sending production customer files through the API.

• Privacy policy for how personal data is handled.
• DPA for controller/processor terms.
• TOMs for technical and organizational measures.
• Security overview for access controls, audit context, and operational safeguards.
• Data residency for regional processing information.
• Subprocessors for third-party processing dependencies.
• Terms for product and account usage terms.