# MTI API Integration
source: https://developer.mastercard.com/mastercard-threat-intelligence/tutorial/api-sandbox-guide/index.md

### Overview {#overview}

This tutorial shows you how to build a small Java application that consumes the Mastercard Threat Intelligence (MTI) API. You start in the Sandbox environment, call each of the three main features, and print the responses.

The goal is a working reference you can build in minutes. The code follows the KISS principle, so it stays short and easy to read.

*** ** * ** ***

### About the Mastercard Threat Intelligence (MTI) API {#about-the-mastercard-threat-intelligence-mti-api}

Mastercard Threat Intelligence provides payment-focused cyber threat intelligence. It helps issuers and acquirers detect, monitor, and respond to emerging fraud and ecosystem threats.

The API gives you programmatic access to this intelligence through REST endpoints. You send a request, and the API returns structured JavaScript Object Notation (JSON) results.

*** ** * ** ***

### What You Build {#what-you-build}

By the end of this tutorial, you have a Maven project that:

* Authenticates with Mastercard using OAuth 2.0.
* Generates a type-safe API client from the OpenAPI specification.
* Calls each of the three features and prints the results.

*** ** * ** ***

### The Three MTI Features {#the-three-mti-features}

The API groups its endpoints into three features. Each feature supports independent use cases, so you can adopt one or all three.

|                Feature                |                                   Purpose                                   |               Primary Users                |
|---------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------|
| Merchant Threat Intelligence          | Assess the risk of a merchant web domain using fraud and cyber indicators.  | Acquirers, merchant risk teams             |
| Payment Ecosystem Threat Intelligence | Find high-risk vulnerabilities that affect payment and e-commerce software. | Issuers, acquirers, cybersecurity teams    |
| Card Testing                          | Investigate card testing activity, merchant behaviors, and transactions.    | Issuers, acquirers, fraud operations teams |

You call each feature in a dedicated step later in this tutorial.

*** ** * ** ***

### Glossary {#glossary}

This tutorial uses the following terms:

* **BIN**: Bank Identification Number.
* **CID**: Company ID.
* **CVE**: Common Vulnerabilities and Exposures, a unique identifier for a known vulnerability.
* **DPoP**: Demonstrating Proof of Possession, a security mechanism that binds an access token to a key.
* **ICA**: Interbank Card Association number.
* **OAuth 2.0**: The authorization framework used to obtain an access token.

*** ** * ** ***