Resolve a conflict by keeping the page text

POST

/cms/print/v2/stories/{id}/sync

const url = 'https://api.example.com/cms/print/v2/stories/1/sync';
const options = {
  method: 'POST',
  headers: {
    'API-Key': '<API-Key>',
    'Token-User': '<Token-User>',
    'Content-Type': 'application/json'
  },
  body: '{"action":"keep_page"}'
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request POST \
  --url https://api.example.com/cms/print/v2/stories/1/sync \
  --header 'API-Key: <API-Key>' \
  --header 'Content-Type: application/json' \
  --header 'Token-User: <Token-User>' \
  --data '{ "action": "keep_page" }'

action: keep_page writes the story’s fields to the article even though the CMS changed them too. To take the CMS text instead, the extension refills the story and saves it with pulledVersionId.

Authorizations

ApiKeyAuth
CmsUserAuth

Parameters

Path Parameters

required

integer

Request Body^required

application/json

object

action

required

string

Allowed values: keep_page

Responses

200

The story