Custom Content "trashed" status

Confluence Development Confluence Cloud
,
1

According to the doc, deleting page or blog via REST API means moving them to “thrashed” status if the response is 200 and they are purged if the response is 204: https://developer.atlassian.com/cloud/confluence/rest/api-group-content/#api-api-content-id-delete

However, this doesn’t seem to apply for custom content, as of current, I get 204 even if a custom content is just moved to trash (i.e. still restore-able with space content tool). Is this behaviour expected or is it a REST API bug? If it’s the former, how do I tell whether a custom content has been “thrashed” or “purged” (permanently removed)?

2 Likes
2

Hi @yongchong.long,

When I test trashing a page I get back 204 when the docs say I should get back 200. I’ve created an issue for this bug here [CONFCLOUD-70605] Delete content REST API status codes return 204 for trashed (200 expected per docs) - Create and track feature requests for Atlassian products.

1 Like