Update Content Sync Settings
PUT/api/integration-instances/:integrationInstance/content-sync-settings
Update the instance-level content-sync configuration. Partial updates are merged onto the current settings. Enabling sync for the first time starts a background baseline job over every mapped listing on the instance, so pre-existing differences are not flagged as drift on day one; poll the jobs API to watch it complete.
reconcile_frequency: six_hours, daily, or weekly. Ownership values: catalog (channel edits are flagged only), channel (channel edits can be pulled into the catalog), two_way (both sides may edit; simultaneous edits become conflicts). Unknown group or field keys are rejected with a 422. Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.