Object storage (buckets)

Each workspace gets S3-compatible buckets, isolated from other workspaces. You never handle raw S3 keys: the API issues short-lived presigned URLs, and file bytes go directly to storage.

In the dashboard

1. Storage → New bucket. Name: 3–63 lowercase letters, numbers, dots and hyphens, starting and ending with a letter or number, no .., not shaped like an IP. Unique per workspace.
2. Open a bucket to Upload files, download or delete. Uploading an existing name asks before replacing.

Deleting a bucket permanently deletes every file in it.

Storage API

Full reference with Node.js, Python and cURL examples: /docs.

1. Team → API tokens → Create token (owners and admins) with only the permissions needed: Read storage (storage:read), Write files (storage:write), Manage buckets (storage:buckets).
2. Call https://api.marvx.io/v1 with Authorization: Bearer mvw_…. No org_id needed.
3. Upload = request an upload URL for the exact size, then PUT the bytes to it with the returned headers.

curl -s -X POST "https://api.marvx.io/v1/storage/buckets/$BUCKET_ID/upload-url" \
  -H "Authorization: Bearer $MARVX_TOKEN" -H "Content-Type: application/json" \
  -d '{"key": "reports/q3.pdf", "content_length": 73400, "content_type": "application/pdf"}'

• Presigned URLs expire after 15 minutes; request fresh ones.
• The PUT must send exactly content_length bytes with the same Content-Type. Max 5 GB per upload.
• Keys: relative paths up to 1024 bytes, no leading /, no ./.. segments.
• Responses are {"data": …}; errors {"error": {"code", "message"}}.
• Browser uploads to presigned URLs depend on the storage CORS settings; if they fail with CORS errors, upload from your backend or contact support.

Quotas

Free 1 GB, Starter 10 GB, Pro 50 GB, Enterprise 500 GB. Paid plans can add +10 GB storage ($2/month each) in Billing → Add-ons. An upload that would exceed the quota is refused with 402 quota_exceeded ("Storage is full"). Freed space shows up within about a minute.

Errors