There is NO WAY we would even consider migrating from Scroll Versions to Scroll Documents if there is no feature-compatible REST API available.

Currently, we have implemented fully automated publishing pipelines that start at the authoring space, publish each version/variant to a dedicated space and then walk this space to publish about 50 PDF documents per space.

and other folks at K15t, any idea if this is still alive in the roadmap? Applications that use the REST API for Scroll Translations face a fairly significant hurdles to update to be ready for Scroll Documents as it is, but that burden becomes even greater if one has to develop Java programming expertise in order to have a chance of automating operations with Scroll Documents. And even then, the Java API still only supports Confluence Data Center (not Confluence Cloud), limiting the utility of this API.

Hi @David,

thank you for getting back to me. You are reading my mind:

It would be great to have a REST API function to trigger a page create action as we do it manually in the “Organized page tree” action.

By now, we first manually an empty page in “Ogranize page tree“ which then is updated be the content from Git file. To have an API function for this would be a milestone for us and speed up the creation process.

Cheers,

Heike

Hi ,

thanks for letting us know. Automation via REST API is definitely on our roadmap. Regarding the Create page action you mentioned, is it particularly important for the action to be triggered within the Organize page tree dialog as opposed to a “normal” Confluence create action?

Cheers,

David

Great! Thank you for considering a public API. We do need this as we push updated and new content from Git into a Confluence space. If the public API also considers “Create new page” in Organize page tree, it would be of great help. By now we create pages manually in Scroll Documents and then push the content.