Allow access to trashed spaces and its contents via API

XMLWordPrintable

    • 2
    • 5

      Problem

      The Confluence Rest APIs don't have a 'trashed' status for space and/or content, limiting access to trashed spaces and their content.

      For API V1 - get content:

      {
  "statusCode": 404,
  "data": {
    "authorized": true,
    "valid": true,
    "errors": [],
    "successful": true
  },
  "message": "com.atlassian.confluence.api.service.exceptions.NotFoundException: Content with id : xxxxxxx cannot be fetched for a space that has been deleted"
}

      For API V2 - get pages:

      {
    "errors": [
        {
            "status": 404,
            "code": "NOT_FOUND",
            "title": "Not Found",
            "detail": null
        }
    ]
}

      For API V2 - get spaces:

      {
    "statusCode": 404,
    "data": {
        "authorized": true,
        "valid": true,
        "errors": [],
        "successful": true
    },
    "message": "com.atlassian.confluence.api.service.exceptions.NotFoundException: No space found with key : xxxxxx"
}

      Suggested Solution

      To enable access to trashed space and its content via Confluence Rest APIs

      Why This Is Important

      The admins need to access the trashed contents programmatically for auditing purposes without restoring the spaces/contents.

      Workaround

      N/A

            Assignee:
            Unassigned
            Reporter:
            John Li
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: