REST API changes for content properties?

Since a couple of weeks (?) we sometimes do not get version information when getting content properties.
The documentation at https://developer.atlassian.com/cloud/confluence/rest/api-group-content-properties/#api-api-content-id-property-key-get states: " By default, the version object is expanded."

Does this mean there is a guarantee that the version object should be present?

If not, is it best practice to always use expand=version in the API call?

1 Like

Hi @marc,

My understanding is that the version information should be returned when the expand query parameter is not specified or it includes version. So, ?expand=content should omit the version information. If the version information is being omitted under other circumstances, then it seems like a bug.

Regards,
Dugald

Hi @dmorrow , thanks for the information. We’ve added ?expand=version to our API calls, and still receive content properties from Confluence Cloud without version information.

The problem is that without version information, we (or actually our customers) can’t update content properties.

I’ve opened a DEVHELP ticket.

1 Like

Hi @marc,

Thanks for creating this. I’ve reproduced this and raised https://jira.atlassian.com/browse/CONFCLOUD-70429 for the Confluence team to look into.

Regards,
Dugald

1 Like

@dmorrow Thank you for raising the issue with the high priority.

Could you try expand=version.number maybe?

Thanks, but that was not a solution (tested already). The issue seems to be related to Confluence backend caching.