# Consume Merchant Threat Intelligence
source: https://developer.mastercard.com/mastercard-threat-intelligence/tutorial/api-sandbox-guide/step-7/index.md

Merchant Threat Intelligence helps you assess the risk of a merchant web domain. You submit one or more domains with a reason for the inquiry. The API returns risk indicators grouped into categories, such as malware, phishing, and payment fraud.

*** ** * ** ***

### When to Use It {#when-to-use-it}

You can use this feature to support these workflows:

* Screening a merchant domain during onboarding or underwriting.
* Investigating a suspicious domain reported by a fraud team.
* Monitoring a domain in your portfolio over time.

*** ** * ** ***

### The Endpoint {#the-endpoint}

This feature uses one endpoint:

* `domainIntelligenceSearch` sends a POST request to `/exposures/domains`.

You send a `reason` and a list of `domains`. The `reason` must be one of `MERCHANT_UNDERWRITING_CONCERNS`, `COLLUSIVE_MERCHANT`, or `SCAM_MERCHANT`.

*** ** * ** ***

### The Code {#the-code}

Add this method to your application. It searches one domain and prints the report:

```java
/** Merchant Threat Intelligence: assess the risk of a merchant domain. */
static void runMerchantThreatIntelligence(ApiClient apiClient) {
    System.out.println("== Merchant Threat Intelligence ==");
    MerchantThreatIntelligenceApi api = new MerchantThreatIntelligenceApi(apiClient);
    DomainSearch request = new DomainSearch()
            .reason(DomainSearch.ReasonEnum.SCAM_MERCHANT)
            .domains(List.of("test.com"));
    try {
        System.out.println(api.domainIntelligenceSearch(request));
    } catch (ApiException e) {
        printError(e);
    }
    System.out.println();
}
```

*** ** * ** ***

### Read the Response {#read-the-response}

The response is a `DomainReportCollection`. Each report includes the domain, the number of risks found, and a list of categories. Each category holds individual risk findings with a severity color and a timestamp.

You assemble the full application, including the `printError` helper, in a later step.

*** ** * ** ***