Update a sync configuration.
REQUIRED: Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.
"Bearer YOUR_API_KEY"
"Bearer YOUR_STRIPE_API_KEY"
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'
"ns_abc123def456"
"production"
"my-namespace"
Request to update an existing sync configuration.
Allows partial updates to sync settings without recreating the configuration. All fields are optional - only provided fields will be updated.
Use Cases: - Pause/resume syncs by toggling is_active - Adjust polling intervals based on activity patterns - Update batch sizes for performance tuning - Add metadata tags for organization
Requirements: - All fields are OPTIONAL - At least one field should be provided for the update - Changes take effect on the next sync cycle
Optional human-readable description of the sync configuration. NOT REQUIRED. Used for documentation and UI display. Maximum 500 characters.
"Daily video ingestion from production bucket"
Optional custom metadata to replace existing metadata. NOT REQUIRED. Completely replaces existing metadata (not merged). Use for tagging, categorization, or custom attributes. Maximum 50 keys, values must be JSON-serializable.
{
"environment": "production",
"project": "video-pipeline"
}Optional status to set for the sync configuration. NOT REQUIRED. Valid values: 'pending', 'processing', 'completed', 'failed', 'paused'. Typically managed automatically but can be manually overridden. Use pause/resume endpoints instead for active control.
PENDING, IN_PROGRESS, PROCESSING, COMPLETED, COMPLETED_WITH_ERRORS, FAILED, CANCELED, UNKNOWN, SKIPPED, DRAFT, ACTIVE, ARCHIVED, SUSPENDED "pending"
Optional flag to enable or disable the sync configuration. NOT REQUIRED. When False, sync will not process new files. Prefer using the /pause and /resume endpoints for clarity. Changes take effect immediately.
true
Optional new polling interval in seconds. NOT REQUIRED. Must be between 30 and 900 seconds if provided. Only applies to 'continuous' and 'scheduled' sync modes. Lower values increase responsiveness but API usage.
30 <= x <= 90060
Optional new batch size for file processing. NOT REQUIRED. Must be between 1 and 100 if provided. Larger batches improve throughput but use more memory. Changes apply to subsequent batches only.
1 <= x <= 10010
Optional schema mapping to replace existing mapping. NOT REQUIRED. Completely replaces existing schema_mapping (not merged). Defines how source data maps to bucket schema fields and blobs. See SyncCreateRequest.schema_mapping for detailed documentation.
If True, sync objects to the bucket without creating or submitting batches for collection processing. Objects are created in the bucket but no tier processing is triggered. NOT REQUIRED. When omitted, existing value is preserved.
false
Successful Response
Bucket-scoped configuration for automated storage synchronization.
Defines how files are synced from external storage providers to a Mixpeek bucket. Includes configuration, status, metrics, and robustness control fields.
Supported Providers: google_drive, s3, snowflake, sharepoint, tigris
Built-in Robustness:
Metrics Fields:
Target bucket identifier (e.g. 'bkt_marketing_assets').
Storage connection identifier (e.g. 'conn_abc123').
Organization internal identifier (multi-tenancy scope).
Namespace identifier owning the bucket.
Source path in the external storage provider. Format varies by provider: s3/tigris='bucket/prefix', google_drive='folder_id', sharepoint='/sites/Name/Documents', snowflake='DB.SCHEMA.TABLE'.
User identifier that created the sync configuration.
Unique identifier for the sync configuration.
Optional filter rules limiting which files are synced.
Schema mapping defining how source data maps to bucket schema fields. Maps external storage attributes (tags, metadata, columns, filenames) to bucket schema fields and blob properties. When provided, enables structured extraction of metadata from the sync source. See SchemaMapping for detailed configuration options.
Sync mode controlling lifecycle (initial_only or continuous).
initial_only, continuous Polling interval in seconds (continuous mode).
30 <= x <= 900Number of files processed per sync batch.
1 <= x <= 100Whether objects should be created immediately after confirmation.
Skip files whose hashes already exist in the bucket.
If True, sync objects to the bucket without creating/submitting batches for processing.
Current lifecycle status for the sync configuration. PENDING: Not yet started. ACTIVE: Currently running/polling. SUSPENDED: Temporarily paused. COMPLETED: Initial sync completed (for initial_only mode). FAILED: Sync encountered errors.
PENDING, IN_PROGRESS, PROCESSING, COMPLETED, COMPLETED_WITH_ERRORS, FAILED, CANCELED, UNKNOWN, SKIPPED, DRAFT, ACTIVE, ARCHIVED, SUSPENDED Convenience flag used for filtering active syncs.
Cumulative count of files found in source across all runs.
x >= 0Cumulative count of successfully synced files.
x >= 0Cumulative count of failed files (sent to DLQ after 3 retries).
x >= 0Cumulative bytes transferred across all runs.
x >= 0When sync configuration was created.
Last modification timestamp.
When last successful sync completed. Used for incremental syncs.
Scheduled time for next sync (continuous/scheduled modes).
Most recent error message if sync attempts failed.
1000x >= 0Arbitrary metadata supplied by the user.
Worker ID that currently holds the lock for this sync
Timestamp when lock was acquired
Timestamp when lock expires (for stale lock recovery)
Whether sync is currently paused (user-controlled)
Reason for pause
Timestamp when paused
User who paused the sync
Hard cap on objects per sync run (prevents runaway syncs)
x >= 1Maximum objects per batch chunk
1 <= x <= 1000Number of objects per batch chunk (for concurrent processing)
1 <= x <= 1000UUID for current/last sync run
Increments on each sync execution
x >= 0List of batch IDs created by this sync
List of task IDs for batches
Total number of batches created
x >= 0Whether resuming partial runs is enabled
Last page/cursor processed (for paginated APIs like Google Drive)
Last primary key processed (for database syncs with stable ordering)
Count of objects processed in current/last run
x >= 0How often to checkpoint (in objects). Default: every 1000 objects
100 <= x <= 10000