Category updates create new blockchain transactions for traceability. You can modify name, description, status, and image.
Endpoint
Request
HTTP Method
PUT
URL
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
COMPANY_ID | string (UUID) | ✅ | Company identifier |
CATEGORY_ID | string (UUID) | ✅ | Category identifier |
Headers
Request Body (multipart/form-data)
| Field | Type | Required | Description |
|---|---|---|---|
name | string | ✅ | Updated category name |
action | string | ✅ | Update action type |
description | string | ❌ | Updated description (max 2048 chars) |
file | file | ❌ | New category image file |
Update Actions
| Action | Description |
|---|---|
CHANGE | Change category name/description |
ACTIVATE | Activate a deactivated category |
DEACTIVATE | Deactivate category (no new objects) |
REMOVE | Remove category and all data |
Response
Success Response (200)
Error Responses
400 Bad Request
404 Not Found
409 Conflict
Update Examples
Change Category Information
Update Category Image
Deactivate Category
Action Types Explained
CHANGE
CHANGE
Purpose: Modify category name, description, or image
Impact:
- Updates category metadata
- Preserves all subcategories and objects
- Creates audit trail on blockchain Usage: Regular updates and improvements
ACTIVATE
ACTIVATE
Purpose: Reactivate a previously deactivated category
Impact:
- Changes status from
delistedtoactive - Allows new object creation again
- Restores full functionality Usage: Restore categories after temporary deactivation
DEACTIVATE
DEACTIVATE
Purpose: Temporarily disable a category
Impact:
- Changes status to
delisted - Prevents new object creation
- Existing objects remain accessible Usage: Temporary suspension or deprecation
REMOVE
REMOVE
Purpose: Permanently delete category and all data
Impact:
- Deletes category, subcategories, and all objects
- Removes all associated files
- Creates deletion record on blockchain Usage: Complete cleanup (irreversible)
Best Practices
Safe Updates
Safe Updates
- Always provide the current name when updating
- Test changes in staging environment first
- Backup important data before REMOVE actions
- Use DEACTIVATE instead of REMOVE when possible
Image Management
Image Management
- Optimize images before upload (under 1MB recommended)
- Use consistent aspect ratios
- Keep backup of original images
- Consider impact on existing UI layouts
Change Management
Change Management
- Document reasons for category changes
- Notify users of significant changes
- Plan updates during low-usage periods
- Monitor system after major changes