> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cocoondata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# <content-service>/api/v1/objects/{objectId}/view

## URL structure&#x20;

```text theme={null}
https://content-service.xy-company.com/api/v1/objects/{objectId}/view
```

where `{objectId}` is the ID of a Secure Object.

## Supported methods and overview&#x20;

* `GET` - used to download a [Secure Object](/3.1/api/creating-secure-objects-and-collections.md#secure-object)'s encrypted *read-only view* data from storage via the Covata Platform's Content Service.
* `PUT` - used to regenerate a Secure Object's *read-only view* (based on the Secure Object's actual data) which is also stored and managed by the Content Service.

> [!NOTE]
>
> The `PUT` method take no parameters.

## Detailed description&#x20;

This API endpoint serves a number of purposes, all of which are managed by the Covata Platform's Content Service:

* Downloads a Secure Object's encrypted *read-only view* data from storage. \

  **Note:** The key required to decrypt this *read-only view* can be obtained by calling the [\<access-service>/api/v1/objects/\{objectId}/keys/view](/3.1/api/access-service-api-v1-objects-objectid-keys-view.md) API endpoint.
* Regenerates a Secure Object's *read-only view* (based on the Secure Object's actual data) in storage.

## Supported roles and conditions&#x20;

This API endpoint supports the following Covata user [roles](/3.1/admin/administering-users.md#a-users-roles) (as described in the [Covata Platform Administrator's Guide](/3.1/admin.md)), conditions and [permissions](/3.1/api/access-service-api-v1-permissions-sets.md) (where applicable):

* [Originator](/3.1/admin/administering-users.md#originator-role) - a Covata user with this role can call the `GET` and `PUT` methods on a Secure Object they own.
* **Originator**, [Collaborator](/3.1/admin/administering-users.md#collaborator-role) and [Ad hoc](/3.1/admin/administering-users.md#adhoc-role) - a Covata user with any of these roles can call the `GET` method for a Secure Object they are a collaborator on (with the **View** *permission*).

The Covata Platform's resources available to one of these Covata users (above) is determined by the access token passed in the [header](/3.1/api/content-service-api-v1-objects-objectid-view.md#content-service-api-v1-objects-objectid-view-required-headers) of requests to this endpoint.

## Required headers&#x20;

The appropriate access token as the `Bearer` token:

* `Authorization: Bearer a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6`

## Optional parameters&#x20;

The following optional parameter can be sent in the URL of the GET request:

* **encoding** - Specify the value `base64` to download the encrypted view as [Base64](https://tools.ietf.org/html/rfc4648)-encoded data. Otherwise, omit this parameter to download the encrypted view as raw/binary data. In both cases, the `Content-Type` in the response is `application/octet-stream`.

  **Example:**

  ```text theme={null}
  https://content-service.xy-company.com/api/v1/objects/987654321098765432/view?encoding=base64
  ```

## Returns&#x20;

If the request succeeded, then an HTTP response status `200 OK` is returned.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.