Update Bulk Sync
Updates an existing bulk sync’s top-level configuration.
Updating a bulk sync is a full replacement of the sync’s top-level configuration. Every field in the request body is written to the sync; any field you omit is cleared or reset to its default value.
To make a partial change — for example, toggling active or swapping a
schedule — fetch the current sync with
GET /api/bulk/syncs/{id},
modify the fields you want to change, and send the complete object back in
the update request.
Updates to active, schedules, and policies take effect immediately.
Changes to source or destination configuration take effect on the sync’s
next execution.
Because omitted fields are reset to their defaults, the discovery and naming options behave the same as on create when left out:
automatically_add_new_objectsresets to not enabling newly discovered source objects automatically.automatically_add_new_fieldsresets to enabling newly discovered fields on already selected objects.normalize_namesresets to enabled.
Send the existing values explicitly if you want to preserve a non-default or non-empty setting.
📘 Updating schemas
When
schemasis present, it replaces the sync’s schema selection: schemas not in the list are disabled. Whenschemasis omitted or empty, the sync’s schemas are left unchanged. Use the Update Bulk Sync Schemas endpoint to change a subset of schemas, or Update Bulk Sync Schema to replace a single schema’s configuration.
Authentication
Basic organization-scoped API key
Path parameters
Headers
Request
Destination-specific bulk sync configuration (e.g. output schema name, file format). The accepted keys depend on the destination connection type.
Human-readable name for the bulk sync.
Organization the sync belongs to. Only used by partner callers; normal callers are always scoped to their own organization.
Schemas to sync. Schemas not in the list are disabled; if omitted or empty, the sync’s schemas are left unchanged.
Source-specific bulk sync configuration (e.g. replication slot name, sync lookback). The accepted keys depend on the source connection type.
