Create GCS Sync
Create a Google Cloud Storage Sync for a collection and start the initial backfill. GCS authenticates with a service-account JSON (stored in Secrets Manager, never returned), so there is no region, endpoint_url, or access-key pair. Returns the sync; indexing runs asynchronously.
Path parameters
Headers
Request
Google service-account key JSON (type=‘service_account’) with read access to the bucket (roles/storage.objectViewer). Stored securely in Secrets Manager, never returned.
Parsing tier. ‘advanced’ = full document understanding; ‘basic’ = faster/cheaper.
Object-name prefix to scope the sync (e.g. ‘docs/2024/’). Empty syncs the whole bucket.
Glob patterns; only matching object names are synced.
Glob patterns; matching object names are excluded.
How to propagate objects deleted from GCS: ‘mirror’ removes them from the collection (soft-delete), ‘ignore’ leaves the collection untouched. ‘archive’ is accepted but currently behaves like ‘mirror’ (documents are soft-deleted; a separate archived flag is planned).
Scheduled reconcile cadence in minutes (minimum 5; below 5 clamps to 5; null = manual).
Response
The sync’s cloud storage type. Returned by the list endpoint (GET /v2/syncs) only; other sync endpoints omit this field.
How the sync authenticates to the bucket: ‘iam_role’ (AWS cross-account assume-role), ‘access_key’ (S3-compatible key pair), or ‘service_account’ (GCS service-account JSON).
S3-compatible endpoint URL (access-key syncs on non-AWS providers); null for AWS S3. Returned by the list endpoint (GET /v2/syncs) only; other sync endpoints omit this field.
True once an event-webhook secret has been minted.
SNS subscribe URL; only surfaced by the subscribe-webhook endpoint.
Effective (already-clamped) cadence; null = manual.