imgbtGuides
Asset Organization
Organizing assets with partitions, collections, and channels.
Asset Organization
imgbt uses a three-level hierarchy to organize assets within a vault: partition, collection, and channel.
Hierarchy
vault/
├── {partition}/
│ ├── {collection}/
│ │ ├── {channel}/
│ │ │ ├── image1.jpg
│ │ │ └── image2.pngEach asset's delivery URL reflects this structure:
https://your-vault.imgbt.com/{partition}/{collection}/{channel}/{filename}Naming Rules
All path components (partition, collection, channel) follow the same rules:
- Lowercase alphanumeric characters and hyphens only
- 1–64 characters long
- Must start and end with an alphanumeric character
- Pattern:
/^[a-z0-9](?:[a-z0-9-]{0,62}[a-z0-9])?$/
Examples
By Department
marketing/blog/hero-images/post-header.jpg
marketing/social/twitter/campaign-banner.png
products/electronics/thumbnails/laptop-01.webpBy User
users/user-12345/avatars/profile.jpg
users/user-12345/uploads/vacation-photo.jpgBy Date
2026/january/photos/new-year-event.jpg
2026/march/videos/spring-launch.mp4Filtering
Use query parameters to filter assets by hierarchy level:
# All assets in marketing partition
GET /api/v1/vaults/{vaultId}/assets?partition=marketing
# All blog assets in marketing
GET /api/v1/vaults/{vaultId}/assets?partition=marketing&collection=blog
# Specific channel
GET /api/v1/vaults/{vaultId}/assets?partition=marketing&collection=blog&channel=hero-imagesUniqueness
Filenames must be unique within a channel (the combination of vault + partition + collection + channel + filename). Uploading a file with the same name to the same path returns a 409 Conflict error.