Retry processing for a file that failed or is stuck.
JWT token from Stytch B2B authentication (magic link, SSO, or M2M)
File ID
"file_abc123"
File reprocessing started successfully
File response schema - COMPOSITE SCHEMA. Combines data from multiple sources for API simplicity: - FileEntity: id, filename, created_at (logical file) - FileContent: sha256, size_bytes, content_type, status, processed_at (physical content) - Computed: isDuplicate, storageCharged (deduplication logic) - Relationships: associations (file-resource links) Used for GET /v1/files/{id} and POST /v1/files responses. Deduplication info: - isDuplicate: Whether this file reuses existing content - storageCharged: Actual storage bytes charged (0 for duplicates) - sha256: Content hash for deduplication tracking
Unique file identifier
"file_abc123"
Original filename
"document.pdf"
MIME type of the file
"application/pdf"
File size in bytes
x >= 01048576
SHA256 hash of file content (for deduplication)
"abc123def456..."
Processing status
uploading, uploaded, processing, ready, error, failed "ready"
Whether this file reuses existing content (no storage charge)
false
Actual storage bytes charged (0 for duplicates)
x >= 01048576
File upload timestamp
"2025-01-17T10:00:00Z"
Detailed processing status
When file processing completed
"2025-01-17T10:02:30Z"
Resources this file is associated with (included when expanded with ?expand[]=associations)
Request origin: api, m2m, connector
"api"
"m2m"
"connector"
Specific source: dashboard, google_drive, notion, etc.
"dashboard"
Metadata from external connector (Google Drive, Notion, etc.). Only present for connector-synced files.