---
title: "Resolve a content synchronization conflict"
method: POST
path: "/v1/spaces/{spaceId}/content/sync/resolve"
tags: ["Spaces"]
---

# Resolve a content synchronization conflict

`POST /v1/spaces/{spaceId}/content/sync/resolve`

## Request

- Base URL: `https://api.spacefast.com`
- URL: `https://api.spacefast.com/v1/spaces/{spaceId}/content/sync/resolve`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `__Host-better-auth.session_token`
  - OAuth 2 (authorization code, authorization URL `https://api.spacefast.com/v1/auth/oauth2/authorize`, token URL `https://api.spacefast.com/v1/auth/oauth2/token`; client credentials, token URL `https://api.spacefast.com/v1/auth/oauth2/token`, scopes: `spaces:write`)

Saves the chosen document only while source and WordPress still match the supplied revisions, then queues the normal source commit and build. Changed revisions return a conflict without overwriting either side.

## Path parameters

- `spaceId` string, required

## Request body

- object
  - `bindingId` string, required
  - `operationId` string, required
  - `expectedBaseRevision` string, required
  - `expectedWordpressDigest` string, required
  - `expectedSourceRevision` string, required
  - `text` string, required

## Response `200`

Response for status 200

- object
  - `$schema` string, uri: Canonical JSON Schema URL for this response body. The server also sends it in the `Link: rel="describedby"` response header.
  - `data` object, required
    - `postId` integer, required
    - `bindingId` string, required
    - `operationId` string, required
    - `status` 'queued', required

## Other responses

- `default`: Problem details (RFC 9457). Any 4xx/5xx response is one `application/problem+json` document.

---

[API](https://skmtc.dev/spacefast/apis/spacefast-api.md) · [All operations](https://skmtc.dev/spacefast/apis/spacefast-api/llms.txt) · [OpenAPI document](https://skmtc.dev/spacefast/apis/spacefast-api/revisions/bd165bc7c983?raw)