Create S3 Sync
Create a Sync for a collection and start the initial backfill. AWS S3 authenticates with cross-account assume-role (recommended) or an access key. Works across S3-compatible cloud storage: AWS S3, Cloudflare R2, Supabase Storage, and Backblaze B2 (each has its own create endpoint). Returns the sync; indexing runs asynchronously.
Path parameters
Headers
Request
Auth for reading the bucket: assume-role (AWS S3) or access-key (S3 or S3-compatible). Non-S3 stores require access-key auth.
Parsing tier. ‘advanced’ = full document understanding; ‘basic’ = faster/cheaper.
Key prefix to scope the sync (e.g. ‘docs/2024/’). Empty syncs the whole bucket.
Region of the bucket (AWS region for S3, or the provider’s region, e.g. ‘auto’ for R2, ‘us-west-004’ for Backblaze B2).
Cloud storage type. ‘s3’ = AWS S3 (assume-role or access-key). ‘r2’/‘supabase’/‘backblaze’ are S3-compatible and require access-key auth with an endpoint_url.
Glob patterns; only matching keys are synced. Empty includes everything under the prefix.
Glob patterns; matching keys are excluded.
How to propagate deletes: mirror removes from the collection, archive retains but marks, ignore leaves untouched.
Scheduled reconcile cadence. MINIMUM 5 minutes (the scheduler ticks every 5 min); values below 5 are silently raised to 5; >=5 honored exactly. null/omitted = manual (events + on-demand only). For sub-5-min propagation use the event webhook.
Response
‘iam_role’ for assume-role syncs, ‘access_key’ for access-key syncs.
S3-compatible endpoint URL (access-key syncs on non-AWS providers); null for AWS S3.
True once an event-webhook secret has been minted.
Event-webhook subscribe URL (only surfaced by the webhooks endpoint).
Effective (already-clamped) cadence; null = manual.