← All documentation

Files · Customer documentation

Create a file space, upload assets, and serve them by URL.

What you prepare

Files to upload. No separate storage signup; check access settings before sharing.

Steps in the workspace

  1. 01Create a file space.
  2. 02Choose and upload a file.
  3. 03Use the returned URL after reviewing access settings.

Example request / integration

Upload logo.png and use the returned URL as your website image source.

# Create a space in the workspace; copy its real SPACE_ID.
curl --fail-with-body -X PUT \
  "$BASE_URL/api/picosvc/files/spaces/$SPACE_ID/object?path=logo.png" \
  -H "Authorization: Bearer $SESSION_TOKEN" \
  -H 'Content-Type: image/png' --data-binary @logo.png
# The JSON response contains publicUrl. Do not upload secrets.

Examples use placeholders: replace $BASE_URL, $SESSION_TOKEN and issued URLs with real values. Never publish session tokens or API keys in a webpage or repository.

Management API entry point

POST /api/picosvc/files/spaces

Space name, file, and target path.

File URL and storage usage.

What it does not do

Files are capped at 10 MiB each; no large-file transfer or advanced image transforms.

Feature comparison and sources

Access controls and image handling：Small-file uploads and URL delivery.

Supabase Storage：Documents public/private buckets, granular access policies, and image transformations.

Feature comparison and sources · Supabase Storage ↗
Overview, workspace, and dashboard

The product overview is public. The workspace handles creation, editing and history. The all-service dashboard shows usage and links for all 16 tools.

Workspace →Product overview →All-service dashboard →