---
title: "Put a file at a specific path (object-storage style)"
method: PUT
path: "/v1/files/{file_id}"
tags: ["Files"]
---

# Put a file at a specific path (object-storage style)

`PUT /v1/files/{file_id}`

S3/blob-style put-object: store the raw request body at the given key. The key is relative to the session's uploads mount (`/mnt/user-data/uploads/` inside the sandbox) and may be nested, e.g. `data/2024/report.pdf`; an explicit `uploads/` prefix is accepted and normalized away. Parent directories are created automatically and existing keys are overwritten. The response is the same `FileMetadata` as `POST /v1/files`, so the returned `id` can be used with the other file endpoints.

## Path parameters

- `file_id` string, required

## Query parameters

- `scope_id` string, required — Session / container identifier.
- `namespace` string — Namespace for the file. Defaults to 'session'.

## Request body

- string, binary — Raw file bytes stored at the key (S3/blob-style put-object). The media type is taken from the request Content-Type header.

## Response `200`

Successful Response

- FileMetadata — Metadata for a file stored in a session (upload or sandbox output).
  - `id` string, required — Relative path of the file within the session, e.g. 'uploads/data.csv' or 'outputs/result.png'. Use this value as `file_id` in subsequent requests.
  - `created_at` string, date-time, required — ISO-8601 timestamp when the file was created or last modified.
  - `filename` string, required — Filename derived from the path.
  - `mime_type` string, required — MIME type detected from the file content.
  - `size_bytes` integer, required — File size in bytes.
  - `type` 'file' — Object type discriminator, always 'file'.
  - `downloadable` boolean, required — True for sandbox output files; False for uploaded input files.
  - `etag` string, nullable — Content checksum (MD5 hex or S3 ETag). Present after stat; None if unavailable.
  - `namespace` string — Namespace this file belongs to (e.g. 'session', 'skills', or a custom namespace).
  - `scope` FileScope, required — Scope that a file belongs to (always a session).
    - `id` string, required — Session / container identifier that owns this file.
    - `type` string — Namespace the file belongs to (e.g. 'session', 'skills', or a custom namespace).

## Other responses

- `400` — Invalid path key (absolute, `..`, or directory key).
- `401` — Unauthorized
- `404` — Namespace not found.
- `422` — Validation Error
- `503` — Files API not configured (session namespace not set).

## Changes

- **2026-08-27** `4e828cf153c4` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/zylon-ai/apis/private-gpt-api/changes/v1/files/:file_id/put.md)

---

[API](https://skmtc.dev/zylon-ai/apis/private-gpt-api.md) · [All operations](https://skmtc.dev/zylon-ai/apis/private-gpt-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/zylon-ai/private-gpt-api/revisions/4e828cf153c4/schema)