Create Bucket
This endpoint allows you to create a new bucket with a defined schema. A bucket is a collection of objects that conform to the schema. The schema defines the structure and validation rules for objects in the bucket.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Request model for creating a new bucket.
REQUIRED: A bucket_schema must be defined to enable data processing and validation.
The bucket_schema tells the system what fields your objects will have, enabling:
- Collections to map your data fields to feature extractors via input_mappings
- Validation of object structure at upload time
- Type-safe data pipelines from bucket → collection → retrieval
Every bucket must have a schema that defines the structure of objects it will contain.
Human-readable name for the bucket
REQUIRED. Schema definition for objects in this bucket. Must include a 'properties' object mapping field names to type definitions. Use Mixpeek types (string, text, image, video, etc.) — NOT JSON Schema types like 'keyword'. Example: {"properties": {"title": {"type": "string"}, "photo": {"type": "image"}}}
Description of the bucket
Unique key configuration for this bucket (OPTIONAL). Enables uniqueness enforcement and upsert operations on specified field(s) from the schema. Cannot be changed after bucket creation.
{
"default_policy": "upsert",
"fields": ["video_id"]
}Additional metadata for the bucket
OPTIONAL object-storage tier for this bucket's objects: standard | nearline | coldline | archive (provider-agnostic). NOTE: applied on write for sync-based ingestion (the primary media path); tiering for direct uploads (POST /objects) and presigned uploads, plus retroactive re-tiering of existing objects, are in progress (TG-2837). Omit for the provider default (standard).
standard, nearline, coldline, archive Response
Successful Response
Response model for bucket operations.
Human-readable name for the bucket
Number of objects in the bucket
Total size of all objects in the bucket in bytes
Unique identifier for the bucket
Description of the bucket
Schema definition for objects in this bucket
Unique key configuration for this bucket (if configured)
{
"default_policy": "upsert",
"fields": ["video_id"]
}Additional metadata for the bucket
Object-storage tier for this bucket's objects: standard | nearline | coldline | archive. Provider-agnostic (GCS STANDARD/NEARLINE/COLDLINE/ARCHIVE; S3/MinIO STANDARD/STANDARD_IA/GLACIER). NOTE: applied on write for sync-based ingestion (the primary media path); tiering for direct/presigned uploads and retroactive re-tiering of existing objects are in progress (TG-2837). None = provider default.
standard, nearline, coldline, archive When the bucket was created
Last modification time of bucket metadata
When the last object was uploaded to this bucket
When bucket stats were last successfully recalculated
Bucket lifecycle status (ACTIVE, ARCHIVED, SUSPENDED, IN_PROGRESS for deleting)
PENDING, QUEUED, IN_PROGRESS, PROCESSING, COMPLETED, COMPLETED_WITH_ERRORS, FAILED, CANCELED, INTERRUPTED, UNKNOWN, SKIPPED, DRAFT, ACTIVE, ARCHIVED, SUSPENDED Whether the bucket is locked (read-only)
Batch statistics for this bucket (calculated asynchronously, stored in DB)
Storage statistics for this bucket (calculated asynchronously, stored in DB)
Source adapter configuration for inbound webhook-driven ingestion

