Assets

The workspace's file library — images, PDFs and documents the portal shows, public or restricted to a tenant. download returns the content; presign create issues an upload URL straight to storage for files above the 2 MB request-body limit.

Command	HTTP	Description
`assets list`	`GET /v1/assets`	List assets
`assets create`	`POST /v1/assets`	Create asset
`assets get`	`GET /v1/assets/{id}`	Get asset
`assets update`	`PATCH /v1/assets/{id}`	Update asset
`assets delete`	`DELETE /v1/assets/{id}`	Delete asset
`assets download`	`GET /v1/assets/{id}/download`	Download asset
`assets presign create`	`POST /v1/assets/presign`	Get an upload URL

Examples

--params carries query, path and header parameters (id, page, filters, X-Workspace-Id); --json carries the request body; --fields limits which fields come back — worth using on every list/get to save context. See Global flags for the full reference.

# List assets
kobana dashboards assets list \
  --params '{"tenant_id": "TENANT_ID"}' \
  --fields "id,name,kind,visibility,size_bytes"

# Create asset
kobana dashboards assets create \
  --json '{"name": "contrato.pdf", "content_base64": "JVBERi0xLjQK...", "content_type": "application/pdf", "visibility": "restricted", "tenant_id": "TENANT_ID"}'

# Download asset
kobana dashboards assets download \
  --params '{"id": "ASSET_ID"}' \
  --output contrato.pdf

# Get an upload URL
kobana dashboards assets presign create \
  --json '{"filename": "video.mp4", "content_type": "video/mp4", "size": 52428800}'

Next steps

Asset types
Schema introspection — every parameter this resource accepts.

Examples​

Next steps​

Examples

Next steps