Write File (Raw / Binary)
Filesystem API
Write File (Raw / Binary)
Stream raw bytes into a sandbox file. Binary-safe, up to 500 MiB per request.
PUT
Write File (Raw / Binary)
Streams the request body directly into a file on the sandbox disk without
buffering in memory. Use this endpoint for any binary payload — images,
archives, compiled artifacts, base64-decoded blobs — or for uploads larger
than the 10 MiB JSON gateway cap.
For UTF-8 text, the JSON
POST /files
endpoint is usually the simpler choice.
Path Parameters
The sandbox identifier. Format:
sbx-<8 chars>.Query Parameters
Absolute path to write inside the sandbox. Parent directories are created
automatically.Example:
/home/user/image.pngUnix user to own the written file. Defaults to the envd default user.
Request Headers
Must be
application/octet-stream.Request Body
Raw bytes. Up to 500 MiB per request. The body is streamed to disk with a flat memory footprint on the orchestrator.Response
Example
When to use this vs. other endpoints
| Payload | Use |
|---|---|
| UTF-8 text, < 10 MiB | POST /files (JSON) |
| Binary (any size up to 500 MiB) | PUT /files/raw (this endpoint) |
| Very large payloads (hundreds of MB, GB-class) | sbx.upload_url(path) / sbx.download_url(path) helpers |
Error Responses
| Status | Cause |
|---|---|
400 | Missing path query parameter |
401 | Missing or invalid API key |
404 | Sandbox not found |
409 | Sandbox is paused — resume it before accessing files |
410 | Sandbox has been killed |
413 | Request body exceeds 500 MiB |
502 | envd daemon unreachable |
503 | Sandbox has no VM |