Resolve Content Conflict
POST/api/content-sync/conflicts/:contentChange/resolve
Resolve one two-way conflict.
- mine: keep the catalog value; the channel change is dismissed.
- theirs: apply the channel value to the catalog.
- both: apply the channel value now; the catalog value is preserved on the resolved record for outbound re-push. Returns 409 when the record is not an open conflict (already resolved, superseded because the channel moved on, or resolved concurrently) and 422 when applying the channel value to the catalog fails. Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Content-Type
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.
Unprocessable Entity
Response Headers
Content-Type
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.