Files are processed according to the specified template
Use the metadata parameter to include custom data (like user IDs, reference numbers) that will be preserved across all extraction API responses and webhooks
Metadata is useful for tying back extractions to your systems, correlation, and application integration purposes
Configure webhooks for asynchronous notifications when extractions complete
The file to upload and process. Supported formats include PDF (.pdf), Excel
(.xlsx, .xls), CSV (.csv), TSV (.tsv), and image files (.jpg, .png, .webp, .tiff).
Only one file can be uploaded per request.
The ID of the template to use for mapping the document data during extraction.
You can also pass "auto" and TableFlow will automatically select the best template
based on the document content and template file type settings.
Optional name for the extraction. This is useful for identifying extractions
in the TableFlow UI and can be used to label extractions in your workflow.
Optional extraction guidance to provide additional context to the AI during extraction.
Use this to give hints about the document structure, specific values to look for,
or any other information that might help improve extraction accuracy.
Optional JSON string containing custom metadata to associate with this extraction.
This can include any information you need to reference, such as user IDs, order numbers,
or other contextual data. The metadata will be included in all extraction responses
(API endpoints and webhooks), making it useful for correlating extractions with your application.Example: {"user_id": "123", "reference": "INV-2023-04-15", "source": "mobile-app"}