Report Search
POST
https://api.deepinfo.com/v1/platform/reports/searchSearches reports. Different filter format: filters.type is required, other filters use operators like {"name": {"contains": "…"}}.
Authentication
Send your API key in the apikey request header.
Query Parameters
| Parameter | Required | Description |
|---|---|---|
page_ | Optional | Min 25, max 100. Default 100.Example 25 |
page | Optional | Min 1, max 800. Default 1.Example 1 |
Request Body
| Parameter | Type | Required | Description |
|---|---|---|---|
filters | object | Required | See Filtering below |
sort | object | Optional | One {field, order} object |
application/json
{
"filters": {
"type": "easm_executive_summary"
}
}
Filtering
This search takes filters as an object with one key per field, not as a must list. Each field takes the operators of its filter type as keys, and fields combine with AND. sort is one {field, order} object, not a list. Example body:
JSON
{
"filters": {
"name": {
"equals": "<value>"
}
},
"sort": {
"field": "name",
"order": "desc"
}
}
Operators by field:
| Field | Operators |
|---|---|
name | equals, not_equals, contains |
type | a plain value: easm_, easm_, easm_asset_detail, easm_, easm_, easm_, easm_issue_detail, cti_ |
type_ | equals, not_equals |
description | contains |
creation_ | gt, gte, lt, lte |
creation_ | a plain value: instant, scheduled |
rule_ | a plain string value |
Searchable Fields
| Field | Description |
|---|---|
name | The report's name, such as executive-summary-2025-06-01-08:00. |
type | Required. The report type to search, such as easm_executive_summary, easm_asset_detail or cti_email_breach_summary. One search covers one type. |
type_ | The options the report was made with (for example, which asset an asset detail report covers), an object compared as a whole. |
description | The report's description. |
creation_ | When the report was created (ISO 8601 date-time). |
creation_ | How the report was made: instant (on demand) or scheduled (by a scheduled report rule). |
rule_ | The ID of the scheduled report rule that made the report; null in the response for instant reports. |
Sortable Fields
| Field | Description |
|---|---|
name | The report's name, such as executive-summary-2025-06-01-08:00. |
description | The report's description. |
creation_ | When the report was created (ISO 8601 date-time). |
creation_ | How the report was made: instant (on demand) or scheduled (by a scheduled report rule). |
Response Fields
| Field | Type | Description |
|---|---|---|
page | integer | |
page_ | integer | |
result_ | integer | |
results | array of object | |
results[]. | string | |
results[]. | string | |
results[]. | string | |
results[]. | string | date-time |
results[]. | string | One of instant, scheduled |
results[]. | string |
Paginated. See Getting Started → Pagination.
Response Schema
Inferred from examples Built from the saved 2xx example response: the fields it contains, with the types seen there. It is not a contract.
| Field | Type | Example |
|---|---|---|
page | number | 1 |
page_size | number | 25 |
result_count | number | 21 |
results | array< | |
results[]. | string | "000000000000000eab510001" |
results[]. | string | "Executive summary" |
results[]. | string | null | "A PDF report of your attack surface." |
results[]. | string | "2025-06-01T08:00:00Z" |
results[]. | string | "instant" |
results[]. | null |
Examples
Selecting one loads it into the request and response panels.