---
title: "FFprobe and store a file"
method: POST
path: "/v1/files/store-file"
tags: ["API", "File Management"]
---

# FFprobe and store a file

`POST /v1/files/store-file`

Submit a file to be analyzed with FFprobe and stored in Rendi's storage. You can use this endpoint both to get metadata about a file and to store it. If you delete the file, you will still have access to its metadata. Get the file's storage url and metadata using the GET /files/{file_id} endpoint. If you require other data extracted from FFprobe - message us at support@rendi.dev.

## Request body

- FileStoreRequest
  - `file_url` string, required — URL to the publicly accessible file. You can use public file urls, google drive, dropbox, rendi stored files, s3 stored files, etc. as long as they are publicly accessible.
  - `is_private` boolean — If true, the stored file is placed in private storage and can only be downloaded via a presigned URL (request one by passing `presigned_ttl_seconds` on the poll endpoint). Not available on trial plans.

## Response `200`

Successfully submitted file for FFprobe and storage

- RendiStoredFileId
  - `file_id` string, required — Unique identifier for the stored file

## Other responses

- `401` — Invalid API key
- `403` — Account quota exceeded or plan does not support this command
- `422` — Validation Error
- `429` — Rate limit exceeded

---

[API](https://skmtc.dev/rendi/apis/ffmpeg-command-api.md) · [All operations](https://skmtc.dev/rendi/apis/ffmpeg-command-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/rendi/ffmpeg-command-api/revisions/d3136dbf90f0/schema)