Edit a story

To edit a story, call the storyEdit mutation. It creates a new version of the story. You need the GraphQL ID of the story (see Get a story).

This example replaces the main asset with another file. Upload the file first, as in Post a story with a file, and use its token the same way.

The mutation:

mutation storyEditExample($input: StoryEditInput!) {
  storyEdit(input: $input) {
    story {
      slug
      version {
        title
        mainAsset {
          __typename
          ... on FileAsset {
            downloadUrl
            embed
            mimetype
            filesize
          }
        }
      }
    }
    errors {
      __typename
      ... on MutationError {
        path
      }
    }
  }
}

The variables:

{
  "input": {
    "id": "STORY_ID",
    "addedAssets": [
      {
        "type": "FILE",
        "file": ".eJw...xMWA",
        "uuid": "GENERATED_UUID"
      }
    ],
    "mainAsset": "GENERATED_UUID",
    "title": "My story with a new file as main asset",
    "publish": true
  }
}

Most fields you leave out keep the value of the previous version. lang is the exception: a version sent without it has no language attached.

With publish: true, version in the response is the new version. With publish: false, version still returns the last published version, and the draft is in story.editVersion.

• title, body, attributes and lang set the content of the new version. body takes a format and a markup, as in Post a story.
• addedAssets and removedAssets change the attachments; mainAsset, coverAsset, removeMainAsset and removeCoverAsset change the main asset and the cover.
• addedTags, removedTags, addedHashtags and removedHashtags change the tags. To change only the tags, use the simpler mutation in Change the tags of a story.
• publish is false by default, which saves the new version as a draft. comment describes the change in the version history.