Update Sync
Updates a model sync’s configuration.
Updating a model sync is a full replacement of the sync’s configuration.
Every field in the request body is written to the sync; any field you omit is
cleared or reset to its default value. An empty or omitted policies list
leaves the sync’s current policies unchanged.
To make a partial change — for example, toggling active or adjusting a
single field mapping — fetch the current sync with
GET /api/syncs/{id},
modify the fields you want to change, and send the complete object back in
the update request.
Updates to active, schedule, and policies take effect immediately.
Changes to source fields, target configuration, filters, or field mappings
take effect on the sync’s next execution.
Authentication
Basic organization-scoped API key
Path parameters
Headers
Request
Identity mappings for the sync and the strategy combining them, replacing any the sync has. When this is omitted, ‘identity’ is used instead; updating a sync with more than one mapping requires this property.
Ignored for user and organization-scoped API keys, which always act in their own organization
Permissions policy IDs applied to the sync. On update, a non-empty list replaces the sync’s policies and an empty or omitted list leaves them unchanged.
Whether to skip the initial backfill of records; if true only records seen after the sync is enabled will be synced.
Deprecated. Use ‘model_filters.logic’. Combines the model filters in ‘filters’ only.
Deprecated. Use ‘model_filters.conditions’ and ‘target_filters.conditions’, which say which kind each condition is rather than inferring it. Ignored when either of those is present, except that a request carrying both shapes is rejected if they describe different filters.
