Asset types
The categories you organize the file library with (contract, bank slip, invoice...). An asset points at its type through type_id.
| Command | HTTP | Description |
|---|---|---|
asset-types list | GET /v1/asset_types | List asset types |
asset-types create | POST /v1/asset_types | Create asset type |
asset-types get | GET /v1/asset_types/{id} | Get asset type |
asset-types update | PATCH /v1/asset_types/{id} | Rename asset type |
asset-types delete | DELETE /v1/asset_types/{id} | Delete asset type |
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 asset types
kobana dashboards asset-types list
# Create asset type
kobana dashboards asset-types create --json '{"name": "Contratos"}'
# Rename asset type
kobana dashboards asset-types update \
--params '{"id": "ASSET_TYPE_ID"}' \
--json '{"name": "Contratos assinados"}'
Next steps
- Assets
- Schema introspection — every parameter this resource accepts.