Currently, the Confluence v2 REST API has significant gaps when it comes to non-page content types (whiteboards, databases, folders, and smart links). While all of the following actions are possible through the native Confluence UI, there are no public REST API equivalents available for app developers to use.

It would be very helpful to have:

• A PUT endpoint to update whiteboards, databases, folders, or smart links.
• A GET endpoint to retrieve or manage labels on whiteboards, databases, folders, or smart links.
• A GET endpoint for inline comments for whiteboards, databases, folders, or smart links
• A GET endpoint to list root-level pages in a space. Developers are currently forced to use CQL as a workaround, which is less reliable and less performant than a dedicated endpoint.

Devs building content management, versioning, or reporting tools on top of Confluence gets blocked from extending their feature sets to cover the full range of content types that Confluence now supports. As Confluence expands beyond pages, parity between the UI and the REST API is critical for the app ecosystem.