Authorizations
Bearer token authentication using your API key. Format: 'Bearer your_api_key'. To get an API key, create an account at mixpeek.com/start and generate a key in your account settings.
Headers
Bearer token authentication using your API key. Format: 'Bearer your_api_key'. To get an API key, create an account at mixpeek.com/start and generate a key in your account settings. Example: 'Bearer sk_1234567890abcdef'
Optional namespace for data isolation. This can be a namespace name or namespace ID. Example: 'netflix_prod' or 'ns_1234567890'. To create a namespace, use the /namespaces endpoint.
Path Parameters
The ID or name of the collection to retrieve
Response
Successful Response
Response model for collection endpoints.
Collection name
Primary source configuration for this collection
Unique collection identifier
Collection description
Collection schema
Input schema for the collection Schema definition for bucket objects.
IMPORTANT: The bucket schema defines what fields your bucket objects will have. This schema is REQUIRED if you want to:
- Create collections that use input_mappings to process your bucket data
- Validate object structure before ingestion
- Enable type-safe data pipelines
The schema defines the custom fields that will be used in:
- Blob properties (e.g., "content", "thumbnail", "transcript")
- Object metadata structure
- Blob data structures
Example workflow:
- Create bucket WITH schema defining your data structure
- Upload objects that conform to that schema
- Create collections that map schema fields to feature extractors
Without a bucket_schema, collections cannot use input_mappings.
Output schema after feature extraction Schema definition for bucket objects.
IMPORTANT: The bucket schema defines what fields your bucket objects will have. This schema is REQUIRED if you want to:
- Create collections that use input_mappings to process your bucket data
- Validate object structure before ingestion
- Enable type-safe data pipelines
The schema defines the custom fields that will be used in:
- Blob properties (e.g., "content", "thumbnail", "transcript")
- Object metadata structure
- Blob data structures
Example workflow:
- Create bucket WITH schema defining your data structure
- Upload objects that conform to that schema
- Create collections that map schema fields to feature extractors
Without a bucket_schema, collections cannot use input_mappings.
Feature extractors applied to this collection
Lineage chain showing the processing history
Vector indexes for this collection
Payload indexes for this collection
Whether the collection is enabled
Additional metadata for the collection
List of taxonomies applied to this collection
Number of documents in the collection