Save a story
PUT
/cms/print/v2/stories/{id}/content
const url = 'https://api.example.com/cms/print/v2/stories/1/content';const options = { method: 'PUT', headers: { 'API-Key': '<API-Key>', 'Token-User': '<Token-User>', 'Content-Type': 'application/json' }, body: '{"baseRevision":1,"icml":"example","release":true,"pulledVersionId":1}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PUT \ --url https://api.example.com/cms/print/v2/stories/1/content \ --header 'API-Key: <API-Key>' \ --header 'Content-Type: application/json' \ --header 'Token-User: <Token-User>' \ --data '{ "baseRevision": 1, "icml": "example", "release": true, "pulledVersionId": 1 }'Stores the uploaded ICML as the next revision. The story must be checked out by this client and baseRevision must be the revision it was edited from; otherwise 409 NOT_LOCKED or REVISION_CONFLICT with the current story. release: true also checks it in.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”id
required
integer
Request Bodyrequired
Section titled “Request Bodyrequired”Media typeapplication/json
object
baseRevision
required
integer
icml
required
Upload id of the ICML file
string
release
boolean
pulledVersionId
The text was just refreshed from this article version: record it, don’t write back
integer
Example generated
{ "baseRevision": 1, "icml": "example", "release": true, "pulledVersionId": 1}Responses
Section titled “Responses”Saved. For a story linked to an article, its tagged fields were written back unless the CMS changed them too (articleSync: conflict).
NOT_LOCKED or REVISION_CONFLICT