# Download a partner document

`GET /lokta-lms/api/v1/sourcing-partners/{partnerId}/documents/{documentId}/content`

Downloads the file of a partner document.

Streams the file from the ledger's document store as an attachment, with the original file name and content type.

The document id is resolved **scoped to the partner in the query**, never found first and rejected second. This endpoint hands back file content; a lookup that could locate a document belonging to another partner and then reject it could end up serving one partner's PAN under another partner's path.

The bytes live in the core store; this API holds only the reference, so what you get here is exactly what the core would serve for `core_document_id`.

## Parameters
- `partnerId` (path, string, required)
- `documentId` (path, string, required)

## Responses
- `default`: default response

## Example request (cURL)
```bash
curl -X GET \
  'https://default.lokta.tech/lokta-lms/api/v1/sourcing-partners/{partnerId}/documents/{documentId}/content' \
  -u '{username}:{password}' \
  -H 'Tenant-Identifier: default'
```

Interactive: https://developer.lokta.ai/reference#operation/content