Configure file storage

Endpoint

PUT /v1/disks/{disk}/config?chunk_bytes=N
GET /v1/disks/{disk}/config
PATCH /v1/disks/{disk}/config

Query parameter	Required	Range
chunk_bytes	Yes for PUT	4,096 to 4,194,304 bytes, inclusive.

Request

curl --fail-with-body -X PUT \
  "https://api.wabe.sh/v1/disks/demo/config?chunk_bytes=65536" \
  -H "Authorization: Bearer YOUR_PROJECT_API_KEY"

Response

204 No Content, with an empty body.

Future file writes capture this size. Existing versions retain their recorded size and remain readable. KV value limits and HTTP body semantics are unchanged. New disks default to 65,536 bytes unless the server operator configures another initial size.

GET returns the current configuration as JSON. PATCH sets all three fields from a JSON body and returns 204:

{"chunk_bytes":65536,"autosave_interval_ms":10000,"history_retention_ms":2592000000}

Defaults are autosave 0 and history retention null (unlimited). Zero retention keeps only required/pinned states at GC. The 30-day duration above is an example. Changing the autosave interval seals existing drafts first. See history behavior.

Errors

400 for a missing, invalid or out-of-range size or an invalid disk name; 401 for authentication; 500 for storage failure. Configuration updates follow the selected durability policy.