Allow updating a Page’s Status (Publish/Unpublish) through the Aha! API

Aha! Pages (Notes) provide a Status field in the UI, but this field is not available through the API. Because of this, teams cannot automate publishing workflows for documentation, release notes, or knowledge base pages. Any status change—such as moving a page from In progress to Published—must be performed manually in the UI, even when the rest of the content workflow is automated.

This limitation creates significant friction for documentation teams:

• Publishing workflows cannot be automated.

• Pages created or updated through integrations (CI/CD, GitHub pipelines, CMS sync, etc.) must still be manually published.

• Large documentation sets require repetitive manual updates.

• Status inconsistencies occur when multiple people are updating content.

• Teams cannot fully automate knowledge base deployment in Aha!, even though content updates can be automated via the API.

Enabling API control of page status would allow documentation updates to be fully automated, improving accuracy, speed, and consistency.

Expose the Status field for Aha! Pages (Notes) in the Aha! REST API, allowing applications to:

• Retrieve a page’s current Status

• Update a page’s Status programmatically

• Set a page to In progress, Ready, Published, or custom workflow statuses

• Automate publish/unpublish operations for Knowledge Base pages

This would allow documentation teams to fully integrate Aha! with automated build pipelines, content sync tooling, and CMS processes. It would also bring functional parity with other Aha! objects (features, ideas, epics), which already allow workflow control through the API.