Trigger Sync Configuration
Manually trigger a sync execution.
Creates a sync job and immediately dispatches it for async execution via Celery. The sync job processes files from the storage provider and creates objects in the bucket.
Execution Flow:
- Acquires distributed lock (prevents concurrent runs)
- Iterates files from storage provider with configured filters
- Creates objects idempotently (skips duplicates)
- Failed objects go to Dead Letter Queue (3 retries)
- Creates batches for collection processing (100 objects/batch)
- Emits metrics and releases lock
Use Cases:
- Test sync configuration after creation
- Force sync outside of scheduled intervals
- Re-sync after updating connection credentials
- Trigger incremental sync (only modified files)
Returns: sync_job_id to track progress via GET /syncs/
Authorizations
Mixpeek API key, sent as Authorization: Bearer mxp_sk_.... Create one in Studio under Settings → API Keys, or with an admin key via POST /v1/organizations/users/{user_email}/api-keys. A missing header returns 403; an invalid or revoked key returns 401.
Namespace id (ns_...), not the namespace name. This scopes the request rather than authenticating it, and it is required on every operation marked x-mixpeek-namespace-scoped.
Query Parameters
Response
Successful Response

