> For the complete documentation index, see [llms.txt](https://docs.tutelar.io/tutelar-api-document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tutelar.io/tutelar-api-document/adverse-media-search/search-details-pdf.md).

# Search Details PDF

The overall details that are provided in the adverse media search details page is available to download via pdf,

A full PDF report is available for download, offering a comprehensive overview of due diligence findings.

### Search Details PDF 

<mark style="color:green;">`GET`</mark> `https://secctrl.tutelar.io/api/v1/aml/adverse-media-search/:searchHistoryId /:SearchResult[]id?download=pdf`

### Header

| Name         | Value              |
| ------------ | ------------------ |
| Content-Type | `application/json` |

### Query Parameter

<table><thead><tr><th width="169.78515625">Query Parameter</th><th width="127.07421875">Type</th><th width="122.6796875">Is Mandatory</th><th>Description</th></tr></thead><tbody><tr><td>Download</td><td>String</td><td>Yes</td><td>A flag indicating the response format will be passed to the download query. The query will return stream data only if the accepted value is <mark style="color:orange;"><strong>pdf</strong></mark>. In this case, only PDF format is supported.</td></tr></tbody></table>

### Sample Response

{% tabs %}
{% tab title="200: OK " %}

```
Content-Type: application/pdf

Complete data stream of the file contents.
```

{% endtab %}

{% tab title="401: Unauthorized " %}

```json
{
   "success": false,
   "code": 1001,
   "message": "Unauthorized access",
   "data": {}
}
```

{% endtab %}

{% tab title="422: Unprocessable Entity " %}

```json
{
   "success": false,
   "code": 1001,
   "message": "Invalid Search History Id",
   "data": {}
}
{
   "success": false,
   "code": 1001,
   "message": "Invalid search Reference id",
   "data": {}
}
```

{% endtab %}

{% tab title="500: Internal Server Error " %}

```json
{
   "success": false,
   "code": 1001,
   "message": "Something went wrong",
   "data": {}
}
```

{% endtab %}
{% endtabs %}

### **Path Param values :**

| PathParameter     | Type   | Is Mandatory | Description                                                                               |
| ----------------- | ------ | ------------ | ----------------------------------------------------------------------------------------- |
| searchHistoryId   | String | Yes          | Search history Id will be generated for every Individual search made in the client panel. |
| SearchResult\[]id | String | Yes          | unique id, to get a adverse media  details.                                               |

### **Success Response:**

Response as in stream by ContentType application/pdf.

### **Failure response:**

```json
{
   "success": false,
   "code": 1001,
   "message": "Invalid Search History Id",
   "data": {}
}
{
   "success": false,
   "code": 1001,
   "message": "Invalid search Reference id",
   "data": {}
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tutelar.io/tutelar-api-document/adverse-media-search/search-details-pdf.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.