---
title: "Retrieve physical file object metadata"
method: GET
path: "/files/{id}/metadata"
tags: ["files"]
---

# Retrieve physical file object metadata

`GET /files/{id}/metadata`

Get information of the file object (not the resource it describes) as JSON.
For example, size of file, date created, content type, filename.

## Path parameters

- `id` string, required

## Response `200`

Successfully returns a list of files

- File — holds all information about a file
  - `id` string
  - `filename` string
  - `filepath` string — only specified if user is serveradmin, and storage is DiskByteStorageService
  - `service-endpoint` string — only specified if user is serveradmin, and storage is S3ByteStorageService
  - `bucket-name` string — only specified if user is serveradmin, and storage is S3ByteStorageService
  - `object-key` string — only specified if user is serveradmin, and storage is S3ByteStorageService
  - `filedescription` string
  - `content-type` string
  - `date-created` string
  - `size` string, int64
  - `authorId` string — id of user who uploaded the file
  - `thumbnail` string — optinal id of the thumbnail image of this file
  - `status` string — status of the file, this can be one of the following: - CREATED file is created, but blob is not in final place yes - PROCESSING blob is in final place, final processing is done such as sending messagess to RabbitMQ - PROCESSED file is fully procesed by clowder

## Other responses

- `401` — Access to this resource is disabled
- `404` — The requested resource was not found

---

[API](https://skmtc.net/clowder-framework/apis/clowder.md) · [All operations](https://skmtc.net/clowder-framework/apis/clowder/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/clowder-framework/clowder/versions/bcd187478e0d/schema)