curl --request POST \
  --url https://api-prod.extend.app/files/upload \
  --header 'Authorization: Bearer <token>' \
  --form 'file=@/path/to/document.pdf'
  

{
  "object": "file",
  "id": "file_1234",
  "name": "example_file",
  "type": "PDF",
  "presignedUrl": "https://s3.example.com/file_1234.pdf",
  "parentFileId": "file_5678", // Optional, only set if this file is a derivative of another file
  "createdAt": "2024-01-01T00:00:00Z",
  "updatedAt": "2024-01-01T00:00:00Z"
}

This endpoint accepts file contents and registers them as a File in Extend, which can be used for running workflows, creating evaluation sets, parsing, etc.

If an uploaded file is detected as a Word or PowerPoint document, it will be automatically converted to a PDF.

Supported file types can be found here.

This endpoint requires multipart form encoding. Most HTTP clients will handle this encoding automatically (see the examples).

​
Headers

​
Content-Type
string

A multi-part/form-data header containing the boundary, such as multi-part/form-data; boundary="...".

​
Body

A multipart/form-data body containing a single file field and its binary data. For more information, see the MDN documenation.

The Content-Type field header is currently ignored and Extend will infer the type automatically based on the field’s Content-Disposition and the file’s contents.

​
Response

​
success
boolean

A true or false value for whether the file was processed successfully or not.

​
file
File

A File object representing the newly created file. See the File object for more details. Note: Since the file is not parsed, it will not contain contents nor metadata.

curl --request POST \
  --url https://api-prod.extend.app/files/upload \
  --header 'Authorization: Bearer <token>' \
  --form 'file=@/path/to/document.pdf'
  

{
  "object": "file",
  "id": "file_1234",
  "name": "example_file",
  "type": "PDF",
  "presignedUrl": "https://s3.example.com/file_1234.pdf",
  "parentFileId": "file_5678", // Optional, only set if this file is a derivative of another file
  "createdAt": "2024-01-01T00:00:00Z",
  "updatedAt": "2024-01-01T00:00:00Z"
}