Skip to content

Latest commit

 

History

History
152 lines (118 loc) · 4.35 KB

import-ti-indicators.md

File metadata and controls

152 lines (118 loc) · 4.35 KB
Raw
title description ms.service ms.author author ms.localizationpriority manager audience ms.collection ms.topic ms.custom ms.subservice search.appverid ms.date
Import Indicators API
Learn how to use the Import batch of Indicator API in Microsoft Defender for Endpoint.
defender-endpoint
siosulli
siosulli
medium
deniseb
ITPro
m365-security
tier3
must-keep
reference
api
reference
met150
02/02/2021

Import Indicators API

[!INCLUDE Microsoft Defender XDR rebranding]

Applies to:

Want to experience Microsoft Defender for Endpoint? Sign up for a free trial.

[!includeMicrosoft Defender for Endpoint API URIs for US Government]

[!includeImprove request performance]

API description

Submits or Updates batch of Indicator entities.

CIDR notation for IPs isn't supported.

Limitations

  1. Rate limitations for this API are 30 calls per minute.
  2. There's a limit of 15,000 active Indicators per tenant.
  3. Maximum batch size for one API call is 500.

Permissions

One of the following permissions is required to call this API. To learn more, including how to choose permissions, see Get started.

Permission type Permission Permission display name
Application Ti.ReadWrite Read and write Indicators
Application Ti.ReadWrite.All Read and write All Indicators
Delegated (work or school account) Ti.ReadWrite Read and write Indicators

HTTP request

POST https://api.securitycenter.microsoft.com/api/indicators/import

Request headers

Name Type Description
Authorization String Bearer {token}. Required.
Content-Type string application/json. Required.

Request body

In the request body, supply a JSON object with the following parameters:

Parameter Type Description
Indicators List<Indicator> List of Indicators. Required

Response

  • If successful, this method returns 200 - OK response code with a list of import results per indicator, see the following example.
  • If not successful: this method return 400 - Bad Request. Bad request usually indicates incorrect body.

Example

Request example

Here's an example of the request.

POST https://api.securitycenter.microsoft.com/api/indicators/import
{
    "Indicators":
    [
        {
            "indicatorValue": "220e7d15b011d7fac48f2bd61114db1022197f7f",
            "indicatorType": "FileSha1",
            "title": "demo",
            "application": "demo-test",
            "expirationTime": "2021-12-12T00:00:00Z",
            "action": "Alert",
            "severity": "Informational",
            "description": "demo2",
            "recommendedActions": "nothing",
            "rbacGroupNames": ["group1", "group2"]
        },
        {
            "indicatorValue": "2233223322332233223322332233223322332233223322332233223322332222",
            "indicatorType": "FileSha256",
            "title": "demo2",
            "application": "demo-test2",
            "expirationTime": "2021-12-12T00:00:00Z",
            "action": "Alert",
            "severity": "Medium",
            "description": "demo2",
            "recommendedActions": "nothing",
            "rbacGroupNames": []
        }
    ]
}

Response example

Here's an example of the response.

{
    "value": [
        {
            "id": "2841",
            "indicator": "220e7d15b011d7fac48f2bd61114db1022197f7f",
            "isFailed": false,
            "failureReason": null
        },
        {
            "id": "2842",
            "indicator": "2233223322332233223322332233223322332233223322332233223322332222",
            "isFailed": false,
            "failureReason": null
        }
    ]
}

Related article