Object Storage

Connect your cloud storage to Mixpeek for automated ingestion

Mixpeek reads directly from your existing object storage — no migration, no ETL. Connect once and set up sync configurations to automatically ingest new files.

Supported Providers

Provider	Auth Method	S3-Compatible
AWS S3	IAM User or IAM Role	Native
Google Cloud Storage	Service Account JSON Key	No
Azure Blob Storage	Access Key or Managed Identity	No
Cloudflare R2	R2 API Token	Yes
Backblaze B2	Application Key	Yes
Wasabi	Access Key	Yes
Tigris	Access Key	Yes
Box	OAuth	No
Mux	API Token	No
Supabase	Service Key	Yes

Setup Pattern

All providers follow the same three steps:

1. Create credentials

   Create a read-only credential in your cloud provider (IAM user, service account, API token) with list and read permissions on your bucket.

2. Add a storage connection

   curl -X POST "https://api.mixpeek.com/v1/buckets/$BUCKET_ID/syncs" \
     -H "Authorization: Bearer $MIXPEEK_API_KEY" \
     -H "X-Namespace: $NAMESPACE_ID" \
     -H "Content-Type: application/json" \
     -d '{
       "provider": "s3",
       "connection": {
         "bucket_name": "my-source-bucket",
         "region": "us-east-1",
         "credentials": {
           "access_key_id": "AKIA...",
           "secret_access_key": "..."
         }
       },
       "sync_config": {
         "source_path": "/videos/",
         "sync_mode": "incremental",
         "polling_interval": 3600
       }
     }'
   
3. Trigger first sync

   curl -X POST "https://api.mixpeek.com/v1/buckets/$BUCKET_ID/syncs/$SYNC_ID/trigger" \
     -H "Authorization: Bearer $MIXPEEK_API_KEY" \
     -H "X-Namespace: $NAMESPACE_ID"
   

   After the initial sync, new files are picked up automatically at the configured polling interval.

Best Practices

• Use separate buckets or prefixes per data domain (videos, images, documents) for cleaner pipelines
• Set up incremental sync to avoid reprocessing existing files
• Use file patterns (*.mp4, *.pdf) to filter which files get ingested
• Use metadata filters to selectively sync based on provider-level metadata (e.g., Mux passthrough, custom tags). See Mux metadata filtering for an example.
• Enable reconciliation (reconcile_on_sync) when metadata changes should trigger unindexing of previously synced objects
• Grant read-only access — Mixpeek never writes to your storage

Sync API reference →