> For the complete documentation index, see [llms.txt](https://docs.uaepass.ae/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uaepass.ae/feature-guides/signature-integration-guide/digital-signature-multiple-document/signing-guide/untitled/4.-obtaining-the-signed-document.md).

# 5. Obtaining Document

Following the [previous step](/feature-guides/signature-integration-guide/digital-signature-single-document/signing-guide/untitled/3.-executing-the-document-signature-process.md), the signature portal sends the following message to UAEPASS to obtain the signed PDF document.

## Obtain Signed PDF Document

<mark style="color:blue;">`GET`</mark> <https://stg-id.uaepass.ae/trustedx-resources/esignsp/v2/documents/{document_id}/content>

#### Headers

| Name          | Type   | Description     |
| ------------- | ------ | --------------- |
| Authorization | string | Bearer \<token> |

{% tabs %}
{% tab title="200 Note that for the sake of readability, {pdfSigned} replaces the binary content of the signed PDF." %}

```
Content-Type: application/pdf 

{pdfSigned}
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
Note that the portal demonstrates its authorization for obtaining the signed document by including the access token (403e...e7b3) in the Authorization header.&#x20;

Also note that the URL of the document requested is created by adding /content to the URL specified in the response received when the signature process for the document was created (the document\[0].url property of the JSON object contained in the response)
{% endhint %}