# Update a Document

# Alias

`DocumentContentUpdate`

# Description

Updates a document on which a signature operation was performed (e.g., a signature process is executed on the document).

# Request

`PUT /trustedx-resources/esignsp/v2/documents/{doc_and_sigdefs_id}/content`

## Parameters

Name | Type | Usage | Description
`doc_and_sigdefs_id` | path | Required | Identifier of the document and signature definitions resource that contains the document to be updated.

## Authorization

The request must contain a bearer access token generated by an authorization server of the platform. This token must have a scope that includes the `urn:safelayer:eidas:sign:process:document` value and must be used as explained in RFC 6750. Basically, the access token must be included in an `Authorization` header as follows:

`Authorization: Bearer <token>`

The access token can be obtained via an authorization code grant or client credentials grant OAuth 2.0 flow.

## Content-Type Header

- `Content-Type: text/xml`

- `Content-Type: application/xml`

- `Content-Type: application/pdf`

- `Content-Type: application/octet-stream`

## Body

Content with which the document is to be updated.

# Response

Status-Line

Value | Description
`HTTP/1.1 200 OK` | The document is provided in the body of the response (`Content-Type: application/pdf`).
Others | See HTTP Response Status for all the possible cases

## Body

If the document is successfully updated, the response has no body. Otherwise, it will have a body containing a JSON object describing the error.