# Retrieve the Current Analysis of a TOE
source: https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-assessment/analysis/current-analysis/index.md

## Overview {#overview}

The `GET Current Analysis` endpoint retrieves the overall rating, security domain ratings, security criteria ratings, and trending data for the current analysis.

You must provide the `toe_id` in the API request to retrieve the current analysis of a vendor.

You can also provide the `include_trend` parameter as the API query parameter, if you want to retrieve trending data for rating differences between the current analysis and the previous analysis.

A graphical representation of the current analysis, criteria ratings, and trends retrieved in the endpoint response can be seen in the **Overview** tab of the vendor's page on the **RiskRecon web portal**.

![](https://static.developer.mastercard.com/content/riskrecon-api/uploads/current-analysis.png)

## Sequence Diagram {#sequence-diagram}

The following diagram shows how to retrieve the current analysis of a TOE:
Diagram retrieve-current-analysis

## Execution Steps {#execution-steps}

The following steps describe a sample integration flow to retrieve the current analysis of a TOE:

1. The user sends a `GET` request to retrieve the current analysis of a TOE and provides the `toe_id` and `include_trend` as the input parameters.
2. RiskRecon provides the the current analysis and the trending data of the requested TOE.

## Sample Request and Response {#sample-request-and-response}

For a sample request and response of this API, see [Get the Current Analysis of a TOE](https://developer.mastercard.com/riskrecon-api/documentation/testing/analysis-samples/curr-analysis-smpl/index.md).

## Use Case Examples {#use-case-examples}

The use cases in this section discuss how you can use the `GET Current Analysis` endpoint to retrieve the current analysis of a TOE:

* [Tracking the security risk posture of a vendor whose contract is expiring](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-assessment/analysis/current-analysis/index.md#tracking-the-security-risk-posture-of-a-vendor-whose-contract-is-expiring)
* [Determining the security risk posture of a vetting vendor](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-assessment/analysis/current-analysis/index.md#determining-the-security-risk-posture-while-vetting-potential-vendors)

### Tracking the security risk posture of a vendor whose contract is expiring {#tracking-the-security-risk-posture-of-a-vendor-whose-contract-is-expiring}

The contract with a vendor is expiring and the RiskRecon customer wants to do a quick ratings check before renewing the contract. The RiskRecon customer can use the `GET Current Analysis` endpoint to know the current security domain and criteria ratings, and trend to decide if they want to continue business with the vendor.

### Determining the security risk posture while vetting potential vendors {#determining-the-security-risk-posture-while-vetting-potential-vendors}

A RiskRecon customer is vetting a vendor and needs to know the vendor's security risk posture. The customer has used the `GET TOE` and the `GET Findings` endpoint to retrieve the list of all the vendor's current risks. Further, the customer uses the `GET Current Analysis` endpoint to know the current security domain and criteria ratings, and trend. This data helps the customer to evaluate if they should do business with that vendor and take on the potential risk.

## Endpoint {#endpoint}


API Reference: `GET /v1/analysis/current/{toe_id}`