# Download files of a case Download the files that are part of a case. The response format is determined by the Accept header: - multipart/mixed — returns all files as a multipart response, where each part contains the binary content of a file with its own Content-Type and Content-Disposition headers. This allows the client to iterate over the parts and attach each file individually to a workflow without any unzipping. - application/zip — returns all files packaged as a ZIP archive. Each file is stored under its original filename as provided during upload. Use this if your HTTP client does not support multipart response parsing. The files returned can be filtered by their mainFile flag or by their type using the query parameters below. If no filters are provided, all files of the case are returned. Endpoint: GET /cases/{id}/files Version: 2.68.0 Security: OAuth2 ## Path parameters: - `id` (string, required) Id of the case whose files should be downloaded. ## Query parameters: - `mainFile` (boolean) If set to true, only the main file of the case is returned. If set to false, only non-main files are returned. If omitted, all files are returned regardless of their main file flag. - `type` (array) Used to retrieve only files of specific types. Multiple types can be provided. If omitted, files of all types are returned. ## Response 400 fields (application/json): - `detail` (string, required) A human readable explanation of the error. - `status` (integer, required) The HTTP status code. - `title` (string, required) A short summary of the error ## Response 404 fields (application/json): - `detail` (string, required) A human readable explanation of the error. - `status` (integer, required) The HTTP status code. - `title` (string, required) A short summary of the error ## Response 406 fields (application/json): - `detail` (string, required) A human readable explanation of the error. - `status` (integer, required) The HTTP status code. - `title` (string, required) A short summary of the error ## Response 429 fields