List uploads in a bucket with filtering, sorting, search, and pagination.
Filtering: Use LogicalOperator with shorthand syntax
{"status": "PENDING", "metadata.campaign": "summer_2024"}{"AND": [{"field": "file_size_bytes", "operator": "gte", "value": 1000000}]}Sorting: Specify field and direction
{"field": "created_at", "direction": "desc"}Search: Full-text search across filename and metadata
"search": "video"Pagination: Use limit and offset
"limit": 50, "offset": 100REQUIRED: Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.
REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like 'my-namespace'
The unique identifier of the bucket
Request model for listing uploads with filtering, sorting, and search.
Provides flexible querying capabilities using the same filter/sort framework as documents, objects, and other list endpoints.
Supports: - Complex filters using LogicalOperator (AND, OR, NOT) - Shorthand filter syntax: {"metadata.campaign": "summer_2024"} - Full-text search across filename and metadata - Multi-field sorting - Pagination with limit/offset
Examples: - List all pending uploads in a bucket - Find uploads by metadata campaign - Search for uploads by filename pattern - Sort by file size or creation date
Complex filters using logical operators (AND, OR, NOT). Supports shorthand syntax: pass field-value pairs for equality matching. Examples: - Filter by status: {'status': 'PENDING'} - Filter by metadata: {'metadata.campaign': 'summer_2024'} - Complex: {'AND': [{'field': 'status', 'operator': 'eq', 'value': 'PENDING'}, {'field': 'file_size_bytes', 'operator': 'gte', 'value': 1000000}]} See LogicalOperator documentation for full syntax.
{ "status": "PENDING" }Sort options for ordering results. Can sort by any field including metadata fields using dot notation. Default: created_at descending (newest first). Examples: - Sort by creation date: {'field': 'created_at', 'direction': 'desc'} - Sort by file size: {'field': 'file_size_bytes', 'direction': 'asc'} - Sort by metadata: {'field': 'metadata.priority', 'direction': 'desc'}
{
"direction": "desc",
"field": "created_at"
}Full-text search across filename and metadata fields. Case-insensitive partial matching. Searches in: filename, metadata values (converted to strings). Examples: - 'video' - finds 'product_video.mp4', 'tutorial_video.mov' - 'summer' - finds uploads with metadata.campaign='summer_2024'
"video"
Whether to regenerate presigned URLs for S3 access in the response. OPTIONAL, defaults to false. If true: - Generates new GET presigned URLs for completed uploads - Useful for downloading files from S3 - Adds ~50ms per upload to response time. If false: - No presigned URLs in response - Faster response time. Note: Original PUT presigned URLs are never returned (security).
Maximum number of uploads to return. OPTIONAL, defaults to 20.
1 <= x <= 100Number of uploads to skip for pagination. OPTIONAL, defaults to 0.
x >= 0Successful Response
Response model for listing uploads.