FileSummary object — Lightweight file info used in list responses?markdown=true query params{ id } instead of { success, fileId, message }client.file.* → client.files.*These changes are straightforward. Most /files endpoint functionality works the same way.
This guide covers all breaking changes to the /files endpoints.
The SDK group and method names have been updated for consistency:
The File schema has been simplified. The contents field has been removed entirely—use the Parse endpoints for content extraction. Additionally, parentFileId is now required but nullable for a predictable response structure.
The new FileSummary schema is a lighter object used in list responses and upload responses. It excludes the presignedUrl and contents fields. Like File, parentFileId is now required but nullable.
The metadata object structure has changed:
The pageCount property has been removed from the File object. To get page count information, use the Parse endpoints which include pageCount in the output metadata.
No breaking changes to query parameters.
Response shape changes: List responses now use { "object": "list", "data": [...] } format, and single object responses are returned directly (no wrapper key). See Simplified Response Shapes for details.
The response now returns FileSummary objects instead of File objects:
Key differences:
success fieldobject: "list" and data arraypresignedUrl not included (use GET /files/{id} to get download URL)contents field not includedpageCount removed from metadataRemoved query parameters:
To get parsed content from files (raw text, markdown, HTML), use the Parse endpoints instead.
Key differences:
success fieldcontents field removed (use Parse endpoints for content extraction)pageCount removed from metadataparentFileId is now always present (null for non-derivative files)The response has been significantly simplified:
Key differences:
success fieldfileId renamed to idmessage field removedNo changes to the request body. The endpoint still accepts multipart/form-data with a file field.
The upload endpoint now returns a File object with consistent nullable fields:
Key differences:
success fieldcontents field removedpresignedUrl is null (only available on GET /files/{id})null valuesThe POST /files endpoint has been completely removed. It was deprecated in API version 2025-04-21.
If you were using this endpoint, migrate to POST /files/upload:
Alternatively, you can use inline file URLs directly in processing endpoints without uploading first:
If you encounter any issues while migrating, please contact our support team at support@extend.app.