Get Published Digital Assets Native File



Renders the native file. In the content-type header received in the response has the media type information.

Request Headers (Optional):
Header NameHeader Value
channelToken{valid channel token value}


Path Parameters
Query Parameters
  • Channel token of the publish target. A channel token must be provided as either a query parameter or a request header.
  • By default, for files of type image, audio and video are rendered inline. For all other file types are downloaded. User can specify the query parameter download=true/false in a request to override this default.
Back to Top


Supported Media Types

200 Response

Successful operation.

304 Response

Not changed. The request honors requests with e-tag.

400 Response

Bad Request. The server is unable to process the request on the client side due to malformed syntax, invalid data or message framing.

403 Response

Forbidden. Client is not authorized to perform this request.

404 Response

The requested resource was not found.

500 Response

Internal server error. An unexpected error condition encountered in the system.
Back to Top


The following example shows how to get published Digital Asset Native file.

curl -i -X GET -H "Accept:application/json" 'http://<hostname>/content/published/api/v1.1/assets/{id}/native'

Obtains published DigitalAsset Native file with id: CONT826832D8B7BC4BDBA372586ECFCB47DD, with channelToken: b361a487716547d8a7527021a2d6628c


Response Body

DigitalAsset Native file will be displayed.
Back to Top