Purge Assets From Trash

post

/mobile/tools/1.0/assets/purging

Purges requested assets from the trash.

Request

Supported Media Types
Header Parameters
  • For batch requests, this HTTP request header is used to force overwrite by passing the value *. If an overwrite value is not passed, then the REST call completes successfully if the ETag of the corresponding asset matches the value of ETag that's provided for the asset in the payload.
Body ()
Asset trashing, untrashing, or purging request metadata.
Root Schema : deleteRequest
Type: object
Asset trashing, untrashing, or purging request metadata.
Show Source
Nested Schema : deleteDependenciesArray
Type: array
Minimum Number of Items: 0
An array of assets to be trashed, untrashed, or purged with their direct and reverse (upstream) dependencies.
Show Source
Nested Schema : deleteDependencies
Type: object
Asset with its dependencies for trashing, untrashing, and purging operations.
Show Source
  • deleteAsset
    The asset representation for delete-dependency requests and responses. For a request body, you must include the asset ID and, optionally, the ETag. No other attributes are necessary. The response body contains the generic asset details.
  • dependencies
    Minimum Number of Items: 0
    Artifacts that this asset depends on. Also referred to as downstream dependencies.
  • reverseDependencies
    Minimum Number of Items: 0
    Artifacts that depend on this artifact. Also referred to as upstream dependencies.
Nested Schema : deleteAsset
Type: object
The asset representation for delete-dependency requests and responses. For a request body, you must include the asset ID and, optionally, the ETag. No other attributes are necessary. The response body contains the generic asset details.
Match All
Show Source
Nested Schema : dependencies
Type: array
Minimum Number of Items: 0
Artifacts that this asset depends on. Also referred to as downstream dependencies.
Show Source
  • deleteAsset
    The asset representation for delete-dependency requests and responses. For a request body, you must include the asset ID and, optionally, the ETag. No other attributes are necessary. The response body contains the generic asset details.
Nested Schema : reverseDependencies
Type: array
Minimum Number of Items: 0
Artifacts that depend on this artifact. Also referred to as upstream dependencies.
Show Source
  • deleteAsset
    The asset representation for delete-dependency requests and responses. For a request body, you must include the asset ID and, optionally, the ETag. No other attributes are necessary. The response body contains the generic asset details.
Nested Schema : assetGet
Type: object
The asset representation for GET requests.
Match All
Show Source
Nested Schema : deleteAsset-allOf[1]
Type: object
Show Source
Nested Schema : assetUpdate
Type: object
The asset representation for PUT requests.
Show Source
Nested Schema : assetIdEtag
Type: object
The asset ID and entity tag (ETag) values.
Show Source
Nested Schema : trash
Type: object
Indicator of whether the asset is in the trash.
Show Source
Nested Schema : assetGet-allOf[3]
Type: object
Show Source
Nested Schema : entityLinksArray
Type: array
Minimum Number of Items: 0
An array of links for an entity's metadata.
Show Source
Nested Schema : items
Type: object
Link to the entity's metadata.
Show Source
Nested Schema : deleteErrorArray
Type: array
Minimum Number of Items: 0
An array of asset delete-dependency errors.
Show Source
Nested Schema : deleteError
Type: object
The asset delete dependencies error metadata.
Show Source
Nested Schema : stringArray
Type: array
Minimum Number of Items: 0
An array of string values.
Show Source

Response

Supported Media Types

204 Response

Assets were purged from the trash. No content was returned in this response.

400 Response

The operation failed because there were unresolvable dependencies or one or more dependencies couldn't be purged.
Body ()
Root Schema : error
Type: object
Show Source
Nested Schema : errorDetails
Type: object
Show Source

412 Response

The operation failed based on the `If-Match` condition. Typically, this is the result of concurrent modification detection. It also can be the result of improper values specified in the request headers.
Body ()
Root Schema : error
Type: object
Show Source
Nested Schema : errorDetails
Type: object
Show Source